Yo @nodejs/collaborators, Hacktoberfest is upon us once again.
We don't need to do much about this, but if we choose to, we can start applying the "Hacktoberfest" label to issues. We can also (my recommendation) temporarily rename the "good first issue" label to "Hacktoberfest".
This is a great idea!
Node.js Code+Learn as a Hacktoberfest meetup event would also be a good idea.
Last time the signal to noise ratio was really bad and we got a lot of bad PRs and noise compared to the amount of good contributions.
We should make sure we point people in the right direction while doing good expectation setting about what ways of contributing to Node.js are helpful.
A code and learn at a meetup organized by someone already familiar with the contribution process sounds good.
@benjamingr should we choose to play along with the initiative, it would also make sense to let collaborators know that they should use the "invalid" label liberally on useless PRs to disincentivize making useless PRs and improve our signal to noise ratio.
Revisiting this issue, as Hacktoberfest registrations are open
I started contributing to Node.js core because of Hacktoberfest 2017 (unit tests in HTTP/2), and ended up organizing/mentoring Code+Learn and becoming a collaborator.
As @ryzokuken mentioned, we can use invalid
labels liberally to reduce noise
I was just about to post about registration :D
If there are no objections I'd like to rename "Good first issue" to "Hacktoberfest" 24 hours before it starts, and turn it back at the end of October.
I was just about to post about registration :D
If there are no objections I'd like to rename "Good first issue" to "Hacktoberfest" 24 hours before it starts, and turn it back at the end of October.
I won't stop it, but I'd rather we add a separate label. I know of at least one site (mine!) that links to search results for "good first issue" and this change would likely break that link: https://www.nodetodo.org/next-steps/. There may be other similar sites. Additionally, it will (probably) make any sites that mention the "good first issue" label in Node.js incorrect for the duration of the month. Lastly, I'd want to label other issues "hacktoberfest", not just good first issues. For example, perhaps a number of the issues labeled "help wanted" would be good ones.
+1 to what @Trott said; a separate label makes more sense here.
totally fair. I'm open to whatever works best for our processes.
hacktoberfest 2019 is open.
@nodejs/collaborators i created the "Hacktoberfest" label, feel free to add it to anything you want hacktoberfest folks to notice.
Can we close?
Confirmed that Hacktoberfest label was removed
Search link: https://github.com/nodejs/node/labels?utf8=%E2%9C%93&q=hacktoberfest
Most helpful comment
This is a great idea!
Node.js Code+Learn as a Hacktoberfest meetup event would also be a good idea.