Halil Umut Özdemir Repository Research

Repositories

I choose Flutter as one of the repositories that I searched because it is used by lots of developers.
It has a good README file. In README, they provide useful links about Flutter (Documentation about Installation, Documentation of the Framework, etc.). After the documentation part, they tell the advantages of their product and basic working principle of it with using visual materials.
In this repository there is a set of detailed labels. They created labels for mostly asked questions and they have explanatory labels for questions of their customers. So, the developer team can answer questions faster.
In the wiki page of this repository, they give information about the roadmap of the project, detailed information about the installation and usage of their framework. I think this wiki file is sufficient for information with the additional links of their websites. So I think it is important to include detailed information about the installation, usage, and capabilities of the product on the wiki page.

I choose Scikit-Learn, because it is a popular machine learning library.
It has a short and understandable README file so that beginners can easily understand the information of the installation of the library. Also, there are links for anyone that needs detailed information. I think a good README file gives basic information about the usage of the product and a way to find detailed information.
There is a help wanted label in this repository. I think this label can be useful in our repository, too. Anyone who needs help for a code piece can use this label.

Because Visual Studio Code is the code editor that I mostly use, I research repository of Visual Studio Code.
In the README file of this repository, there is a part named Contributing that explains how a user can contribute the project by submitting bugs and requests. It is the part that I like about the README file.
Also on the wiki page of that repository, there is detailed information about how to contribute to the Visual Studio Code Project. I think it can be useful to solve bugs and errors in the projects.

It is an open-source compıter vision library.
They have labels like effort: few days, effort: few hours, effort: few weeks which define the difficulty of the issue. It can be good to categorize issues. With these tags, members with easier work can help another member.
In the wiki page of the repository, there is detailed information about versions of the library. Also, they archive all of their meeting notes in their repository(2008 to 2020). I view some of these meeting notes. In meeting notes, they explained the agenda and action items of the meeting as short as possible. I think this feature can make old meeting notes more reusable.