by At Codeminer, we value and encourage contributions to open-source projects and this year was no different as we kept contributing to several open-source projects. We believe this is a way to give back to the community, helping to improve projects we often use and even projects we don’t use, but contributing to them would benefit other people.
Another point we advocate for is the fact that by working on open-source developers can get experience in a real project that is used by real people. Interacting with open-source projects helps our developers improve their skills and keeps them motivated, knowing that others use the code they develop.
Other initiatives include the weekly internal open-source workshop we conduct to assist developers interested in entering this world but unsure how to start and the #GivingBack program, where we allocate developers to contribute to open-source projects full-time.
Today, we will present you with some data regarding our efforts to contribute to the open-source community in 2023.
The projects
The project we contributed the most to this past year was Mastodon, a decentralized social network that took a lot of traction this year. The top 3 are completed by the Casa and the Punchclock projects. Among the top 10 projects, we find some well-known ones, such as Shoulda Matchers and Pundit, which are widely used in the Ruby community and by our clients at Codeminer42. Below is a chart depicting the top 10 projects we contributed the most.
We contributed to more than 20 projects, spanning various programming languages such as Ruby, JavaScript, TypeScript, and Elixir.
The numbers
Regarding the whole of contributions of the year:
Last year (2022), October was the month with more contributions (people get excited by Hacktoberfest and its swags 😂), but this year, we had June as the month with more contributions.
This is majorly due to the end of the first phase of our trainee program, where they were assigned to open-source issues to gain experience in real projects instead of just studying projects as they had done before. Each of them received mentorship from the company’s most experienced developers at the start of the program, and the result is shown in the growth of contributions in the second phase, as you can see in May and June.
This also resulted in a blog post from one of our "miners": "The Path of Open Source: What I learned", showing the experience of entering the world of open-source contributions.
The statuses of the PRs (as of the present date):
Some of the closed PRs were due to a misunderstanding of the issue at first or because the project maintainer decided to use a different approach to the proposal in the contribution.
PRs opened based on the average lifetime (from PR opening to being merged) of previous contributions, which should take approximately one month between reviews and issue discussions. Of course, this time varies from project to project and time available from the maintainers, but getting a general idea is interesting.
Conclusion
This post was just a piece of what Codeminer did for open-source projects this year. We thank all the CodeMiner developers and all the maintainers who worked and reviewed our contributions. We want to continue contributing more and more to the community and always with better quality than before.
We want to work with you. Check out our "What We Do" section!
