Last year there were discussions of what we could do to be more prepared to take advantage of the wider “Hacktoberfest” in 2025.
One of those things was to get started preparing for it sooner, and discussing it as group sooner.
I’d like discuss this at the upcoming DaWGs if you want to join us on Tuesday at 11.00 US/Eastern (other timezone are available!). Come on by and tell us what you think: https://matrix.to/#/#docs:ansible.com
I think we could get something started in this thread for planning. The main thing is to try and identify some issues to which we can add the hacktoberfest tag.
Hacktoberfest works best for simple fixes. Either Edit on GitHub or something someone can grep/replace over the repo.
There is a mad rush that first week as the people who get XX PRs merged first get a free t-shirt (at least in the past that’s how it went).
It’s also important to decide how we limit the ‘noise’ PRs. Again, for those racing for a t-shirt, we can get things that change a comma somewhere as the entire PR.
What we do have is a solid backlog of issues. If we could review them and see which ones we can pop in and add a solid description of the exact documentation fix, we could add the hacktoberfest label. It would have to be non-controversial as we wouldn’t want someone doing a good PR for us and then have it held up by bikeshedding or legitimate ‘this is not the correct fix’ reviews.