[DOC/ENH] Hacktoberfest Issue Label

[loganthomas]

Brief Description

I would like to propose the dev team creates a new "Hacktoberfest 2020" label for outstanding issues for pyjanitor that they may want people to work on during Hacktoberfest this year. As October quickly approaches, this would be a great way to invite new contributors to the project as well as submit some issues that seasoned contributors may be able to help the dev team with during October. I for one would love to submit a few PRs to pyjanitor during ~~Octbober~~ Hacktober 🎃

Example API

• Link for Hacktoberfest 2020 site here

[ericmjl]

@loganthomas!!!!! It's been a while! Thanks for pinging in!!!! It's great to see you again, even if just virtually 😄.

I love this idea. Given what I remembered, at SciPy 2019, you helped a ton with the sprint. I love the enthusiasm for this, and I'm going to invite you onto the dev team! We've got a discord (for just the devs at the moment) as well - it could be useful for coordinating during Hacktober.

[samukweku]

So, how does Hacktoberfest work?

[loganthomas]

Hacktoberfest is a month-long celebration of open source software run by DigitalOcean:

• It's open to everyone in the GitHub global community!
• If you submit 4 quality pull requests to public GitHub repositories, you complete the challenge and earn a limited-edition T-shirt.
  • The T-shirt is given to the first X number of people that complete the challenge (but X is usually pretty high so you have a really good chance of getting one). I've done it for the past 2 years and gotten a shirt both times.
  • This year they are giving folks the option to plant a tree or receive a shirt.
• You can sign up anytime between October 1 and October 31.
• Here is a list of helpful FAQs

Specifically for pyjanitor, maintainers are encouraged to create issues for anything you’d like contributors to help with, making sure to give them a Hacktoberfest label so they’re easier to discover. You can also share issues or repositories on Twitter, using #Hacktoberfest. The Hacktoberfest team will try to retweet as many as they can for contributors to see!

I have a few recommendations in order to get this started:

1. Create a Hacktoberfest 2020 label in the issue tracker.

   • A simple Hacktoberfest label works just fine, but including a year allows us to filter by year easily and compare over consecutive years (only applicable if we plan to do this for more than one year 😄 )

2. Tag issues normally, but add the Hacktoberfest 2020 label to anything we'd like to try and complete through the challenge

   • pyjanitor has a great reputation for tagging/creating tags that are user friendly (especially the available for hacking, help wanted, good first issue, good intermediate issue, and good advanced issue labels)
   • In my experience, most people actively looking to contribute during Hacktoberfest are in the beginner/intermediate realm of open source. Thus, I'd recommend focusing the Hacktoberfest issues in that space. But, ya never know who might be looking 👀

3. Actively create some new issues that we (as a dev team) would like to try and complete during the challenge

   • Contributors have an extra incentive to submit PR's so it would benefit us to think of a few items we can display that we'd like to get done. Best case scenario, a new contributor helps us with an issue and they are one step closer too earning a shirt. Worst case, we have documented some things we'd like done and have them in the issue tracker.

4. Compile stats to track progress

   • Open to ideas here, but I'm a data scientist and see an opportunity 🤓

   • I think it would be cool if we collected a few metrics on September 30 and then again on October 31 to show the progress.

   • We could also talk about updating this weekly? Depends on the level of engagement I suppose...

   • Not sure where this would live or what the final form will be, but I am thinking about something like the below:

     Metric	Pre Hacktoberfest	Post Hacktoberfest	Compared
     Open Issues	83	70	↓ 13
     Closed Issues	266	350	↑ 84
     Hacktoberfest Issues Closed	0	15	↑ 15
     Open PRs	5	15	↑ 10
     Closed PRs	384	400	↑ 16
     Hacktobterfest PRs Closed	0	10	↑ 10
     Contributors	76	82	↑ 6

5. Take notes throughout the process to help for next year

   • It's always nice to do a post-mortem and collect notes on things that we can do better next time
   • Plus, if we get used to tagging things this way and compiling certain metrics, we can do the same thing for internally sponsored sprints (like SciPy 😄)

[ericmjl]

@loganthomas I'm going to reopen and pin this issue at the top of the issue tracker, it's good for visibility :smile:

[MinchinWeb]

Thanks for participating this year!

[ericmjl]

Our pleasure!