Hello everyone! This week’s blog will be focusing on the GNOME organization. “How can you contribute to GNOME”, “How can we make GNOME asynchronous?” or let’s start with the basic one “What is GNOME ?”.
What is GNOME?
GNOME is a free and open-source desktop environment for Unix-like operating systems. I find the workflow of GNOME very intuitive. It is smart and stable. Dynamic workspaces are one of the features that make using GNOME a great environment to me. We can easily view all the applications running on a workspace simply by pressing the Super key and We cannot forget that it’s easily extensible. It has a lot of extensions.
All passionate applicants can contribute to GNOME!
The community appreciates everyone who is passionate and can contribute to its project through the project repository or contribution page. All the projects use an issue tracker to keep information about bugs to fix, project features to implement, documentation to write, and many more. You can follow the tutorial and also create an issue that you feel should be modified. Applicants can look for newcomer-friendly issues to use for their first contributions by looking for the following issue tags in the project issue tracker: “4. Newcomers”.
My Experience during the Contribution Period!
When I first started contributing to this project during the contribution period of Outreachy, I was perplexed. The codebase seemed very intimidating initially, So I thought of completing the tutorials before making an actual contribution to get the basic knowledge about GNOME apps. In the process of building an abstract GNOME app, I found some errors in the tutorial, which gave me a kickstart. I created issues corresponding to those errors and started solving those. Soon there was a list of issues I was working on. These included fixing broken links, adding dependencies, modifying documentation and adding correct screenshots – corresponding to the steps mentioned.
So if you are reading this blog and thinking about applying to Outreachy in the following December or May cohort, you’ve got this! Remember to choose a project of your interest with the known tech stack and not be intimidated by the codebase, however large it may seem to be. Join the community channel to clear your doubts with the maintainers. Read the documentation to understand the project entirely. And lastly, use your skills wisely to work on issues.