How We Decided on Our Project

In terms of finding our project, we first took a look at the projects that the class had already made evaluations of. Though when reviewing them, we found that these large projects like VSCode would be difficult to understand and thus make useful fixes/changes, and that due to their size there would be a large gap in time between submitting a PR and getting feedback on it. So we then looked at projects that we personally found interesting, where I brought up Curl. Curl was interesting but we then found that the project was currently not accepting new PRs so we would have to wait weeks to get feedback. Then another member suggested Frosty as they were familiar with using Twitch extensions. We looked through the GitHub and found that maintainers were very active and that the project wasn’t too large, and everyone felt that they could understand it.

Group Work So Far

So far we have decided on the project of Frosty, with all of the members currently working on installing and getting it running. We had one standup where we decided on this action item and discussed issues that we might be having with getting it running.

Obstacles and How We Plan to Resolve Them

The current obstacle is getting Frosty running, so we will communicate our issues to each other on our group Discord server to resolve them. We will also work to begin mapping out the repository and understanding it. Then we can transition to looking at issues and making PRs.