Skip to main content

The Hectoberfest

Hactoberfest

A Hactoberfest takes place in October where coders are encourages to churn out a set amount of Pull Requests in the month. And a Pull Request is essentially a contribution made to the community. It is an interesting opportunity set to help motivate coders to take an active part in the open source communities in general. I certainly enjoyed the chance. This blog is dedicated to the Hactoberfest and acts as my index to my contributions and associated blogs.

That Index I was talking about...

The Good

I have made five pull requests, contributing to open source programs for the first time. In many ways, this is my dream come true; just 3 years ago, I never even thought this to be something within my power to do. I was always a consumer. Now, I have [contributor] tag next to my name in some of the program that I actually use or play.

The Bad

This exercise reminded me of a TEDTalk by Daniel Pink where I was first introduced to the candle problem. As the deadline loomed, with the prospective of getting the t-shirt dwindling as others completed their 5 pull requests, I was more and more attracted to questions that had clearly defined goals. Other tasks that I would have found more interesting were not only less enticing but was becoming more challenging to think through. At the end, my interests were trumped by a mere t-shirt. Was that good? Well, these were tasks that had to be done by somebody, so my contributions weren't in vein. Still, I am less proud of my work than usual.
By next Hecktober, I wish to be more familiar with some interesting group sufficiently so that more interesting questions would be within my grasp of understanding to comfortably do them during the month period.

The Weird

I learned more about guns, zinc, protein powders, and horrors of eating virtual human flesh than before. I hope some of the information would be of some use in my life. I hope some of these information will never be revisited.
Labels:

Comments

Post a Comment

Popular posts from this blog

Project: Boost-free goblins

The headache: Boost Don't take me wrongly: Boost library is a powerful set of tools for bleeding-edge technology. Much of it gets absorbed into the C++ Standard Libraries. The problem lies in our project being inactive for 7 years, which means it is relying on a library that is 7 years behind. Installing such an old library is a chore, and securing a pre-built package is problematic at best. The project is even incompatible with the later versions of Boost. It may have once given the original developers a powerful technology to propel their project in the past, but now we are stuck with clock stopped at 2011. Along with libtcod being stuck also in 2012, dealing with Boost is critical to bringing the project up-to-date. Options There are several ways to address the issue. Option 1 : Upgrade We can read each related source code, research how Boost has modified the relevant function calls, and either fix the expected return type or required input type, This may lead to mor...
Post a Comment
Read more

Vehicles with a Broken Frame

Browsing through github projects in C/C++ Trying to find ways to link up the goblin_camp project with more automated testers, I started looking around the Readme.md files of other C/C++ projects in github. From neovim, I found AppVeyor, and although I have not yet set it up, it promises to supplement Travis CI with Windows test builds. I also found Coverity Scan, which might be a way for us to scan the large, preexisting code and fix goblin_camp. Then, from Cataclysm-DDA, I found Bounty Source . The icon had a dollar figures on it, so I assumed it was some sort of funnily-named fund raising site. It was, but with a twist. Show Me The Money Apparently, this site is designed to help the project by having people put down money into a pot to fix certain issues listed in Github. Some of the issues were very popular: enough people contributed to the pot of 250 dollars. I would also imagine those are tough ones. I found myself a less-popular, 4 year-old issue of 15 dollars . I am mor...
Post a Comment
Read more

Debugging with GCC: GIMPLE

GCC and GIMPLE One of the very first thing GCC asks the GSoC applicants to do, even before writing the application, is to try various different debugging techniques using GCC. I was personally familiar with the basic, compile-with-g-flag-and-use-gdb method. Turns out, there's more: GIMPLE. A Simple but Non-trivial Program Problem Description The instruction asks to compile a simple but non-trivial program with some flags that generates debugging information: -O3 -S -fdump-tree-all -fdump-ipa-all -fdump-rtl-all . Because I was keep reading on ways to debug GCC just prior to the statement, I immediately thought "GCC" and tried make -j8 CXXFLAGS="-O3 -S -fdump-tree-all -fdump-ipa-all -fdump-rtl-all" . This was a mistake: turns out, GCC can't be compiled with those flags. Thankfully, GCC developers have a very active IRC channel for me to signal SOS. Resolution jakub and segher were quick to respond to my call for help. jakub: it isn't meant that y...
1 comment
Read more