Introduction

This week in our Open Source Software Development class, we had the chance to watch more final presentations and reflect on how different teams tackled their projects. Our team also presented our work on Oppia, which was a great opportunity to showcase the work we’ve done and the implementation of feedback along the way from Professor Joanna.

Introduction

This week in our Open Source Software Development class, we’ve been finishing up our contributions to Oppia and getting ready to share what we’ve worked on. It’s been a good chance to reflect on what we’ve learned and also check out how other teams tackled their projects.

Introduction

This week in our Open Source Software Development class, we continued making progress on our group contributions to Oppia, and also explored how open source fits into the world of business. It’s been interesting to not only get hands-on with a real open source codebase, but also to reflect on how companies actually use and sustain open source in practice.

Introduction

This week in our Open Source Software Development class, my group kept working on Oppia and made more progress finding new down issues to contribute to. I also spent some time reflecting on The Cathedral and the Bazaar, and I looked into how big companies manage their open source work with OSPOs. Overall, it was a solid week with a mix of coding and learning more about how the open source world works behind the scenes.

Introduction

This week in our Open Source Software Development class, my group made significant progress on our Oppia project. We also heard a presentation from our TA, who shared his own experience breaking into tech through open source, which offered a unique and inspiring perspective on the potential of OSSD.

Introduction

This week, we had a class speaker, Nick Vidal, from the Open Source Initiative (OSI) present about the Open Source AI Definition. The talk provided insight into how the open source community is defining AI development and ensuring transparency, accessibility, and ethical considerations in this rapidly evolving space.

Introduction

This semester has been all about diving into open source software development, and although we haven’t started contributing code yet, it’s been an exciting journey of exploration. My two teammates and I have spent this week getting to know the landscape of open source projects, leading to our decision to choose Oppia as our project.

Introduction

This semester has focused on understanding Open Source Software Development, learning how to get started, and practicing the process of selecting and contributing to a project. As I’ve explored different ways to get involved, I’ve realized that even small contributions can have a meaningful impact on open-source communities.

Introduction

As I dive deeper into the world of open source, I’ve started evaluating various projects through both classroom discussions and personal research. This process has given me a clearer understanding of what to expect from open source contributions, particularly as a beginner.

Projects So Far

The projects I’ve explored so far, through class discussions and my own research, have shown me that not all projects are as beginner-friendly as I had anticipated. Many of these projects, while exciting, have inactive members and haven’t seen true involvement in years.

Git Exercises

The git exercises we did in class helped reinforce the previous lessons I have had on git and Github. It is extremely important to understand these tools in order to work on a team as a software developer.

Idea

For this week’s project, our team came up with the idea of developing a browser extension designed to quickly reference common and useful git commands. We wanted to create a tool that would save time for beginner developers and help eliminate confusion when it comes to executing essential git commands. This extension will serve as a handy reference for users, streamlining the workflow of git-related tasks.

Introduction

In open source projects, a code of conduct serves as a crucial guideline for maintaining a positive and inclusive community. It sets expectations for behavior, helps prevent conflicts, and ensures that contributors can work together in a respectful and productive manner. In this post, I will explore the importance of codes of conduct in open source communities by analyzing different examples and reflecting on their role in fostering collaboration and accountability.

When I hear the term open source, I usually envision a large team of people working on a specific project to then release publicly without much desire for profit. I envision these teams being comprised of members from around the world who may or may not have known each other before the creation of the project. I believe that some advantages of open source are that it allows for more people to give input and help solve issues, thus avoiding many of the needless errors that occur when a small team creates a project.

Closed source, to me, seems like a better idea if a team is looking to profit off of a project given that I think ownership over a project is unclear in an open source project. I decided to register for a class about open source software development because I want to gain exposure to real world projects and hopefully contribute to them in some meaningful way. I also want to learn more about how to manage them and how they work so that I can create my own in the future.