🎃 Hacktoberfest v0.0.1 🎃
Lets us have a brief look at the month in hindsight. Stay tuned for more explicit dive into Hacktoberfest.
Going in, I did not know what to think. I was excited to be apart of the open source community, and at times overwhelmed. I knew from joining the Discord Server for the event, there was tons of projects out there, but what I wasn’t prepared for….
The competition of tens of thousands of people all vying for contributions to open-source projects, and I had no idea how competitive it would end up being.
Over the course of the Month +, I have spent a ton of time on GitHub, and in doing so, I did notice a couple trends during Hacktoberfest.
Contributors & Participants
You will see participants rush to a repository and ask to be “assigned” an issue. Eventually you will notice some of the same names, across various projects, with different technologies.. Like flies on 💩.
First I was impressed of the scope and volume people were able to make contributions in. I’d be lieing to you if I did not admit that I found myself quite critical of my own skills. Falling back into these same repositories weeks later though, that would change…
It became evident that it was really just abusing the “assign” system, to collect and horde issues. I found this very noticeable during the first week. This sort of abuse seems to contradict the purpose of the assign system.
The individuals who have horded these issues though, I cannot recall one being done. No questions were asked, attempts from Maintainers to reach out were left unanswered.
fresh, never ❄️frozen❄️, wild caught Spam?!?
^^ The individual created the issue, and attempted to solve it just adding an extra line. Maintainers gave him the benefit of the doubt, no further commit was pushed.
Two styles of project management style relating to issues became clear to me.
A project maintainer decides to use the assign system, because it prevents multiple people wasting time on an issue. Furthermore, there is the direct commitment from an individual, allowing them to take ownership of their work.
There is no assignment, first come, first serve. You open a PR, and solve an issue. This can have its own merits, as you can step up and take it upon yourself to complete. On the other hand, the work your doing can be for nothing if somebody beats you to it.
I can see merits to both systems if your a maintainer. People will take an issue, than disappear. Leaving the issue in limbo. With an event like Hacktoberfest, I am sure there is more patience given because of new developers contributing to projects. On the other hand, you just want to issue to get done with. So get it done. The flakiness of others can be annoying, which extends beyond this scope. Either way, maintainers and contributors who care about a project stand out. Regardless of their style and/or approach.
Stay tuned for additional volumes