I have really enjoyed reading about how other groups came to their project idea. I noticed that some groups decided to have some general projects that were interesting to them and then chose the projects that were easy to set up and did not give a lot of issues at the start. Furthermore, I think this is a crucial point, as projects that are difficult to even set up often imply a lack of proper documentation. Working on such an open-source project could become a burden later down the line, given the short time constraint we have for the class. Having to have the open-source software cloned and set up for testing and development fast is crucial in deciding what project to start the open-source journey with as a beginner.

I have also noticed teams discovering projects by looking at open-source alternatives to the projects they were already using. The group AFFiNE for example, chose it because it was an open-source alternative to Notion. This is also a really nice way to discover new projects that give meaning to contributing. It makes it so you are not only using the free tool but also contributing to it as a way of generously paying it forward for other people to have a better product.

Our groups planning stages were also very similar to most of the posts I have read so far. We have initially short-listed a bunch of alternative or overall projects that we use on a daily basis. We have then removed the projects that we were not familiar with or took way too long to set up. This eventually led us to Oppia.