This is the second part of Contributing to OSS projects where I’m telling my modest journey in being a contributor to OSS projects, as a way to motivate myself to continue doing it but also to show others that it’s not difficult to get started.
So let’s continue…
resque/redis-namespace - Add the ability to pass a Proc as the namespace, Remove rubysl-json dependency for rbx. Fixes travis build: I was in need of this for a multi-tenant app I was working on by that time that had a redis based activity feed. Even though it was not accepted because the added complexity was considered not worth it, I appreciated the feedback from @yaauie, I learned a couple things overall :)
paraseba/eliga - Ack standup update received, Receive updates from private messages, and others: Eliga was a toy project that @paraseba wanted to do, and I had the opportunity to help him. We didn’t finish it, and now there’s even something similar from hipchat, but there was a very important outcome: I learned a lot!! If you happen to have the chance to do some work with @paraseba, go for it!
nberger/rapipago_scraper, nberger/rapipago_api and nberger/rapipago_map: Perhaps I should have just skipped this projects, but I’m going to keep them not only because I learned a lot while doing them but also because I showed them during a ruby meetup (yep, clojure in a ruby meetup) and there are some videos from that session! It’s all in spanish, sorry in advance if that’s not your thing.
guilespi/time-series-storage - Make timestamp param position consistent. Add some tests and a couple merged pull requests and others that I left out: I was in-between jobs and I asked @guilespi if I could be of help in any of his projects, so he offered me a desk in his offices, a bed (had to share it with the dog but didn’t know that until it was too late), food and a lot to learn! So I took the next ferry and “crucé el charco” to Montevideo. Apart from having a great time with @guilespi, his wife and friends, it was the first time that I worked an entire week doing clojure, and it was awesome!
clojure/test.check - Minor refactoring: use int-rose-tree in choose: A very minor refactoring, just one line. But I think it’s one of those cases where you need to do some preparation work to get a grasp on the codebase: test.check code is not “trivial”, so I was pretty happy when I got to understand the shrinking process that uses those rose trees. It can be very easy to understand today thanks to great posts like Verifying State Machine Behavior Using test.check and others that exist today, but by that time I could only find Writing simple-check by Reid Draper, which is great and I recommend it a lot, but it’s not so educational. I was also happy to have had penetrated the clojure’s JIRA barrier :)
That’s it for 2014.
I hope this isn’t being too boring. To me, it’s being awesome. It’s liberating in some sense: Even though I’m not proud of all the code I did, I’m proud for having done it and for showing it in the open. A couple years ago I would have been incapable of doing this: I was very afraid of doing a mistake while in the open.
Life is only one. And as (supposedly) Albert Einstein said:
A person who never made a mistake, never tried anything new
See you in the third part, where I’ll cover the current year.