Finding somewhere to contribute
In my last post I set some goals for myself in order to manage my expectations and contributions. One of these goals was to use my bilingual skills to contribute to a project internationally which I thought would be a great way to get my feet wet in the community. I began by searching for issues which had the words “translate” and “Italian” in them which lead me to Navcoin, a promising cryptocurrency focused on fast & efficient payments. I had a look around the codebase and homepage and I noticed their repo had an issue filed asking for help contributing to translations of the site in various languages. I quickly jumped on this as I thought it would be an interesting and different kind of contribution than usual. It also helped that I’d heard of them before briefly on reddit and was genuinely interested in how they approached the crypto space.
I decided to get started on the translation of the homepage but quickly realized that someone had already created an Italian version. This version, however, was simply run through Google Translate and was full of grammatical errors and mistranslated English sayings. So I forked the repo, cloned it to my laptop and started poking around the code to try and find where this translation was stored. A quick search in VS Code lead me to a file called ” _index.it.html” where the Italian translation was stored for the homepage. I began combing through the HTML and fixing various errors and mistranslated words and after 4 or 5 passes through the file I felt confident that I was “done”.
Creating a Pull Request
After pushing to my Github repo I began creating a pull request where I noticed a checklist needed to be completed before submitting the pull request. Unfortunately I was unable to claim or assign my initial issue on Github because I didn’t have appropriate permissions to do so. What I could (and had to) do from this checklist was have the layout tested using Netlify which I had never used before. Luckily, this was easy enough and the check passed meaning that the only thing required to have my changes published to the Navcoin.org website was a review from someone in the community with write access to their repository. Unfortunately, this is where things fell short of my expectations.
I waited a few days for someone to review, comment or even reject my pull request, but unfortunately I was disappointed here. As of writing this, no one from the community has commented anything on my pull request or even rejected it. It seems the community may be less active than I initially believed.
So what did I learn? Well, for starters, I should be ensuring that the projects I am contributing to are actively maintained to increase the likelihood of getting my PR accepted. Also, I should have likely installed Hugo and tested the changes in a more in-depth manor before creating the pull request (although I was lucky enough to pass the tests on the first try this time). All-in-all I’m looking forward to my next contributions and can’t wait to learn more from my first experience.