Group Progress and Contributions

This week we had an in-class meeting and discussed our progress on the Frosty project. Everyone continued working on different tasks and shared updates during the meeting.

I commented on an issue and continued working on the adaptive themed icons for Android. This week I was able to finish the implementation, and I am now preparing to test it before submitting a pull request. This is the first time I worked on a feature like this in an open source project, so I want to make sure everything works correctly before submitting.

Group Progress and Meeting Reflection

This week our group met on Google Meet and discussed our progress on the Frosty project. Each member worked on different parts of the project and we shared updates during the meeting.

I mainly spent time going over the codebase and looking through existing issues. I also updated my ideas for contributions and started working on them, including adding adaptive icons, editing documentation, and thinking about how to improve some user-facing error messages. This process helped me better understand how the project is structured.

Reflection on Other Groups

During the presentations this week, we noticed that many groups are still in the process of setting up their development environments. This seems to be a common challenge for students who are contributing to open source projects for the first time. Some groups mentioned that the setup process can be quite complicated. For example, the group working on Oppia said that they need to use Docker to run the development environment. For beginners, learning how to use tools like Docker can take some time, but it is also an important part of real-world open source development.

Choosing the Project

So far our group has been discussing what open source project we want to contribute to. When choosing the project, we considered several important factors. One important factor is whether the maintainers respond to pull requests and issues in a reasonable amount of time. Since we are new contributors, feedback from maintainers is very important for learning how the contribution process works.

We also wanted to find a project where the issues have different difficulty levels. This allows us to start with smaller beginner-friendly tasks and slowly move to more complex problems.

Project We Hope to Contribute To

This week our group discussed what kind of open source project we want to contribute to. We are hoping to find a project where maintainers respond to pull requests in a reasonable amount of time. Since we are new contributors, getting feedback from maintainers is important for us to understand how the contribution process works.

We also want to find a project where the issues have different difficulty levels. Some beginner-friendly issues can help us start contributing, and later we might try slightly more difficult tasks.

Student Presentations and Extensions

This week we watched presentations from different groups and saw the extensions they created. Many of the projects were very creative. One group made a video that showed how the brain forgets information by gradually speeding up the playback, and it was very funny and memorable. Other groups built extensions that were practical and useful in everyday life. It was interesting to see how different teams approached the same assignment with completely different ideas.

Watching these projects made me realize that there are many ways to design a browser extension. Some teams focused on solving small daily problems, while others focused more on creative ideas and storytelling. Seeing these different approaches was inspiring and helped me think more broadly about project design.

Git Exercises in Class

This week we practiced more Git exercises in class. We explored how Git works inside a repository and learned more about the .git folder. It was interesting to see how Git stores commits, branches, and history.

We also practiced some basic Git commands and workflows. For example, we learned how to create commits, check the status of a repository, and view the commit history. At first Git still feels a little confusing, but practicing these exercises helped me understand the workflow better.

Team Progress

This week our team started working more seriously on our first open source project. The idea of our project is a Chrome extension that allows users to highlight text on webpages and keep the highlights even after refreshing the page.

During our meetings we talked about how the extension should work and what features we should focus on first. We also created the GitHub repository and organized the files. Everyone shared their ideas and we discussed how to divide the work.

Open Source Communities and Code of Conduct

This week we talked about open source communities and the importance of having a Code of Conduct. I learned that a Code of Conduct helps create a respectful and safe environment for contributors. Because open source projects are open to people from many different countries and backgrounds, it is important to have clear rules about communication and behavior.

A good Code of Conduct usually explains what kind of behavior is acceptable and what is not. For example, contributors should respect others, avoid harassment, and communicate professionally. It also usually explains how to report problems if someone breaks the rules. I think this is very important because without clear guidelines, conflicts can easily happen in large online communities.

What I Think About Open Source

When I hear the term open source, I think about software where the source code is public and anyone can see it. People can study the code, change it, and improve it. Many developers from different places can work on the same project together.

One advantage of open source is that it is very transparent. Because the code is public, people can understand how the software works. If there is a bug, someone from the community can help fix it. Open source projects also benefit from collaboration, because many people can contribute ideas and improvements.