Ever since I finished my Outreachy Internship, I have been contributing to several open-source projects here and there. Even so, whenever I was asked on if I am currently contributing to any open-source project I often said no. I said no not because I wanted to be dishonest, but because at that specific point I felt what I contributed was insignificant. Can you imagine?
I decided to reflect my contributions in a reverse motion and think of how far I have come in this past year.
An open-source journey
– Learn X in Y minutes : Fixing some typos sample contribution
Last year I wanted to take part in Hacktoberfest, I was trying to find ways to get started. I notice the Learn X in Y minutes had some documentation in Greek language however, there were a few typos. I decided to fix several of them. Do you know a unique language? Maybe you can help an open-source project in close captioning, documentation, or translation.
– Adding Consistency: Hugo
Sometimes contributing is not overly complicated, things such as adding consistency to a documentation can be very beneficial as it makes it easier to read.
– Drop code, add, fix, rebuild: Airmozilla
Airmozilla is a product/project that I hold dear to my heart as that is the product I worked on during my first internship and the team/mentor I worked with are just awesome. Merging code into it is always refreshing, but to be able to contribute code understanding the code base and the language used is key. I remember when I started contributing code there were many times where I had merge conflicts. That was something I dreaded because fixing them looked like conducting an intricate operation. Merge conflicts can be hard to master but worth the effort.
– Contribution leading to Discussion: DWYL (Do What You Love)
Sometimes you might contribute a fix, and get to know people that want to hear more about things that you would like to see in their project. That can turn into a very interesting discussion.
– Improving diversity: Diversity – Index
– Contributing with session
– You do big things and learn how to collaborate: Airmozilla
What I learned from my work: Aside from Django, Python, and all the technical stuff, I learned that I was capable of contributing new features to an existing project, even though the learning curve could be huge and distance sometimes can make the learning curve wider.
What I hope for the future of my open-source contributions is that I find the balance of getting started without that being as challenging every single time. I also want to see my programming skills improve more, as much as my knowledge of how several software systems work.
Working on Airmozilla through Outreachy opened several doors for me. It equipped me with skills that I used to get other opportunities.
Whatever we contribute to making an open-source project better is good enough.
The more I learn and blog about, the more I am able to use that experience to help one person at a time.
P.S – All underlined text are links.