#292 Fedora Representation for Hacktoberfest 2021
Closed: Complete 2 years ago by siddharthvipul1. Opened 2 years ago by t0xic0der.

We had our Hacktoberfest representation from the community last year and albeit we started late to prep for it, it was a success. Now that we are almost starting from a month before, we probably should do it again - what do you folks think?

Things to take care of

  • Get an inventory of repositories at GitHub which can be potential candidates to Hacktoberfest contributions
  • Create and tag self-contained and well-documented issue tickets as hacktoberfest for repos on GitHub
  • Connect with the design team to help create posters/banners to promote the community's Hacktoberfest representation
  • Possibly bring in the awesome folks from the Community Outreach Revamp and have their two cents about this
  • Set up push mirror from stub GitHub repositories to actual Pagure repositories in order for the participant's PR to be counted
  • Reach out to folks with repos at the Easyfix page asking them to tag their existing easyfix issues with hacktoberfest
  • Prep slide deck / talk for an event that can go as long as 90 minutes, with multiple speakers to onboard new folks to community

This follows up the ticket created under the Fedora-Join project of the fedora-join namespace here https://pagure.io/fedora-join/Fedora-Join/issue/257

I would love to hear from you as to what you think about it and how can possibly do it better! :)

This follows up the discussion taking place here https://discussion.fedoraproject.org/t/fedoras-representation-for-hacktoberfest-2021/32744


The Mindshare Committee discussed this in their weekly meeting. The general sentiment is positive towards supporting Fedoras participation Hacktoberfest! Some questions came up in our discussion:
1. What was last years outcome? How many people participated and what did they work on?
2. Do we expect mostly new contributors or existing?
3. The plan you outlined seems great, but a lot of work. Do you have some folks on board to assist?

Some notes

  1. We were a bit underpowered the last year as we started preparing late (nearly one week close to the start of the Hacktoberfest). Hence, we directed folks to the Easyfix repositories and asked the maintainers to tag those tickets with hacktoberfest and folks could contribute to them. For the one day event that we had the last time on BlueJeans, around ~20-30% of the total participants were newcomers while the rest were speakers and the folks who were around at some earlier point, making a comeback.

  2. As much as contributing to Fedora is done best, one step at a time - there is a lot of momentum factor too involved due to which some existing contributors might start feeling out of place after sometime if they are not able to find something to do. This event would potentially expect both new contributors (and try to get them into the community) and existing ones (who could use this opportunity to restart their contributions).

  3. Unfortunately I don't. Any and every assistance in this regard would be highly appreciated. I am thinking of aggregating the first, second and sixth tasks from my outline as just one by reaching out to the folks maintaining those repos and ask them to tag their easyfix issues with hacktoberfest. I would keep the fifth task in the backseat too for now - until we come across people who can be able to help us with that.

Offtopic (or not) : Both Fragment and Easyfix rewrite repos are on GitHub and I am expecting massive contributions to the both of them down-the-line. I might put this point forth in the coming W&A meet and start planning how we can channel the voluminous contributions to effective progress.

I think We as a community need a presence in this event; It's a lot of work (maybe like in google code in). The mentors need to know the project to evaluate nontrivial commits.

I think Fedora-join can help but I'm not sure if we can handle all the work . but I'm +1

I am generally -1 to this as it often brings a lot of spam.
We haven't really any proper contribution through this event but yes, I understand @t0xic0der that it could be because of less efforts from our side.
Our projects are often mature.. easy fixes tickets are not a lot (be it because nature of our projects or just because we don't have people filtering out those).. so not sure how beneficial this can be at this point .. without a general change in our approach to highlighting issues way before October

@t0xic0der since you are pretty active with EasyFix and Fragment (say Møte), how about we just apply for those 2 repositories instead of all of Fedora-Infra org

We did best with what was made available last year but you're right, it brings a lot of spam - I myself had to deal with ~10 spammy PRs and today's just 1st October! It doesn't feel right committing in someone's (here, repo maintainers) behalf because this just adds a lot of metawork to filter through PRs. But for those who can, @bt0dotninja's mail should get them in a position to decide if they should.

There can be easy to fix issues in the repositories but I doubt if there would quick to fix issues - something that Hacktoberfest is unfortunately about and that itself removes the possibility of people contributing. Our repositories are nice and they are (mostly) well documented but I cannot say for sure if the PR maker would be meticulous enough to read through them.

I stayed up till late last night to tag the issues on Easyfix and Mote (2.0 :sunglasses:) with hacktoberfest and there have been a healthy in-flow of contributors (and some spams but hey, always look for the bright side :P). All in all, they are helpful in addressing a lot of trivial yet quick-to-fix issues and I see it as a good sign.

Quick update - We had a discussion in the Commops telegram channel with @bt0dotninja back in the last week of September and with @riecatnor (after Mindshare meetings) that in the wake of FWD, setting Outreachy projects and some more other things - we'd only be stretching ourselves thin if we added one more thing to the pile. So we decided to drop a mail and keep the effort minimal this time around.

Closing this ticket as there is no other action item on mindshare.. if I missed something, do reopen this ticket again

Metadata Update from @siddharthvipul1:
- Issue close_status updated to: Complete
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata