#419 Reviving contributor hackfests in 2023
Opened 3 months ago by jflory7. Modified 3 months ago


  1. Define a process for organizing contributor hackfests with budget
  2. Target 2-3 in-person hackfests and/or up to 6 virtual hackfests in 2023


Fedora has had a long tradition of bringing small groups of contributors together for focused, in-person sprints. They have had many names: FADs, sprints, and hackfests. These hackfests are organized by a team or sub-project, and give an opportunity for a small team to get to know each other better and accomplish a few specific goals in a small amount of time. There is wiki documentation about how to organize a FAD, but it is very out-of-date.

Also, now it has been a few years since any hackfest happened in Fedora, either in-person or virtually. The benefit and impact of continuing these is good for Fedora, and to specifically target support to teams that would greatly benefit from the high-bandwidth environment of an in-person hackfest. However, the process to organize a hackfest is not clear and there is little guidance on how to do it other than prior knowledge that you just have to ask.

The goal for this ticket would be to figure out what an updated process for this might look like, and to also agree on a target in 2023 for hackfests.


There is pre-ticket close and post-ticket close work with this ticket:

Pre-ticket close

  • As a Council, define a process for any recognized Fedora team in the Fedora Account System to submit a hackfest proposal (for either virtual or in-person).
    • Create guidelines for in-person organizers: Locations and safety of Fedora contributors. Recognition of any local laws and public health regulations. Travel sponsorship and visa support.
    • Create guidelines for virtual organizers: Is a virtual hackfest a thing? What does it look like? What makes it different from regular online meetings?
  • Agree on a 2023 target for hackfest funding, and request as much funding in the 2023 fiscal year.

Post-ticket close

  • Outreach and promotion of the updated policy
  • Council meeting Q&A about the new process?
  • Avoiding the problem of coming up with a new process but not having it get utilized

Additionally, I would promote this as a "beta", i.e. that we haven't done this in a while, many things have changed since we last did hackfests, and any team volunteering in 2023 to host one will help us in "piloting" the new process. There may be bumps, but hopefully we can have some bold champions who will help us smooth over the bumps for others who might come after.


  • In-person, small-group hackfests resume
  • Contributors have more time to connect in offline settings
  • We return the high-value of these hackfests into the Fedora Community and begin piloting what they can look again in the 2020s

I've created a topic on Fedora Discussion for this ticket.

Please keep this ticket focused. Discuss there, and record votes and decisions here. Thanks!

Discussed in 2022-11-23 meeting.

In today's meeting, we proposed an action plan for this ticket:

  1. Hold two hackfests in the first half of 2023 and one hackfest in the second half.
  2. The Fedora Council opens a bidding process in January for the two hackfests, and a bidding process in July for the third hackfest.
  3. @sumantrom and @t0xic0der volunteered to organize a process for this and work with me to roll it out next year.

I'm removing this ticket from the meeting discussion queue, but we will take this as a short-term action to close this ticket by January or February of 2023.

Metadata Update from @jflory7:
- Issue assigned to jflory7
- Issue priority set to: Waiting on External (was: Next Meeting)

3 months ago

Login to comment on this ticket.