It is still under construction and content may change. Do not rely on the information on this page.
This is the main page for the Fedora Council 2024 Hackfest. The purpose of the 2024 Council Hackfest is to forge a path forward for the Fedora 2028 Strategy.
At a glance:
- Location: Amsterdam, The Netherlands (Red Hat Amsterdam office)
- Dates: 6-9 February 2024
- Travel itinerary:
- Participants arrive on Monday, 5 February
- Participants leave on Saturday, 10 February
Participants
| No | Name | FAS | Role | Origin location | Remote? | Day 1 (Tue, 6 Feb) | Day 2 (Wed, 7 Feb) | Day 3 (Thu, 8 Feb) | Day 4 (Fri, 9 Feb) |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Justin W. Flory | jflory7 | Community Architect | Brussels, BE | no |  |
|
|
|
| 2 | Matthew Miller | mattdm | Project Leader | Brussels, BE | no |  |
|
|
|
| 3 | Aoife Moloney | amoloney | Operations Architect | Brussels, BE | no | |
|
|
|
| 4 | Sumantro Mukherjee | sumantrom | Elected Representative | Kolkata, IN | no | |
|
|
|
| 5 | Akashdeep Dhar | t0xic0der | Elected Representative | Kolkata, IN | no | |
|
|
|
| 6 | David Cantrell | dcantrell | Engineering Representative | ?? | no | |
|
|
|
| 7 | Alberto Rodríguez Sánchez | bt0dotninja | Mindshare Representative | Mexico City, MX | no | |
|
|
|
| 8 | Jona Azizaj | jonatoni | DEI Advisor | Brussels, BE | no | |
|
|
|
| 9 | Fernando Fernandez Mancera | ffmancera | Initiative Co-Lead | Brussels, BE | no | |
|
|
|
| 10 | Smera Goel | smeragoel | Initiative Co-Lead | ?? | ?? | |
|
|
|
: present
: absent
: undecided
Purpose
The purpose of the Fedora Council 2024 Hackfest is accomplish the following:
- Example 1
- Example 2
- Example 3
Impact
- Vision: An abstract idea of where we want to go.
- Mission: A more concrete picture of how we get to the vision.
Why this vision and mission?
- Supporting evidence 1
- Supporting evidence 2
- Supporting evidence 3
Primary goals
Primary goals are our most urgent tasks that set the minimum bar for what we want to accomplish.
Example Goal 1
- Goal: One-sentence summary of what we want to accomplish.
- Success metric: The metric we use to know whether we accomplished this goal or not.
Descriptive text to provide more details about the goal and why it is important.
Example Goal 2
- Goal: One-sentence summary of what we want to accomplish.
- Success metric: The metric we use to know whether we accomplished this goal or not.
Descriptive text to provide more details about the goal and why it is important.
Example Goal 3
- Goal: One-sentence summary of what we want to accomplish.
- Success metric: The metric we use to know whether we accomplished this goal or not.
Descriptive text to provide more details about the goal and why it is important.
Secondary goals
Secondary goals are other important tasks that are valuable to discuss in person, but are not defined as "mission critical" for the success of the hackfest. How much time we get to cover secondary goals depends on how much ground we cover with the primary goals.
Example Goal 1
- Goal: One-sentence summary of what we want to accomplish.
- Success metric: The metric we use to know whether we accomplished this goal or not.
Descriptive text to provide more details about the goal and why it is important.
Example Goal 2
- Goal: One-sentence summary of what we want to accomplish.
- Success metric: The metric we use to know whether we accomplished this goal or not.
Descriptive text to provide more details about the goal and why it is important.
Q&A
- Is this realistic to accomplish?
- Answer here.
- Does everyone need to be in the same room for this to happen?
- Answer here.
- What happens if this hackfest does not happen?
- Answer here.
Logistics
Logistics and planning information for executing the hackfest.
Budget proposal
This table represents the proposed budget. Note that the amount proposed below is final, i.e. you would not be reimbursed for more than what you propose here.
Please estimate all prices in USD. Use latest market rates for approximate conversions from EUR to USD on xe.com.
| No | Name | FAS | Airfare and/or rail ($USD) | Hotel ($USD) | Taxis, meals, visas, insurance, other minor incidentals ($USD) (if applicable) | Comments |
| 1 | Matthew Miller | mattdm | $TBD | $805 | $TBD | |
| 2 | Aoife Moloney | amoloney | $TBD | $805 | $TBD | |
| 3 | Sumantro Mukherjee | sumantrom | $1350 | $805 | $TBD | |
| 4 | Akashdeep Dhar | t0xic0der | $1350 | $805 | $TBD | |
| 5 | David Cantrell | dcantrell | $TBD | $805 | $TBD | |
| 6 | Alberto Rodríguez Sánchez | bt0dotninja | $TBD | $805 | $TBD | |
| 7 | Jona Azizaj | jonatoni | $TBD | $805 | $TBD | |
| 8 | Fernando Fernandez Mancera | ffmancera | $TBD | $805 | $TBD | |
| 9 | Smera Goel | smeragoel | $TBD | $TBD | $TBD |
- Total Airfare: $2700 USD
- Total Hotels: $6440 USD
- Total Taxis, Meals, Visas, Insurance, Other Minor Incidentals: $TBD USD
- Event Total: $9140 USD
Schedule
- All times in local time (CET / UTC+1)
- TPB-B = TPB-B is the "older" Red Hat Building at the Technolgicky Park tram stop
Monday, Jan. 29
Arrival day.
- 09:10: (A Sport Hotel) Departure, 15-20m walk to TPB-B
- 09:30: Arrival at TPB-B, Argentum Meeting Room (need RH badge for entry)
- 10:00: High-level refresh: goals for hackfest, schedule
- 10:10: Ticket triage; year-long goals for CommOps in 2018
- Take time together to triage tickets; what's still backburner, what can be closed?
- 12:30: Lunch
- 14:00: fedora-commops#110: Fedora Appreciation Week
- See ticket for details
- bex joins
- 17:00: Quick retrospective, re-confirm next day schedule
- 17:30: Depart from TPB-B
Tuesday, Jan. 30
- 09:10: (A Sport Hotel) Departure, 15-20m walk to TPB-B
- 09:30: Arrival at TPB-B, Argentum Meeting Room (need RH badge for entry)
- 10:00: High-level refresh: goals for hackfest, schedule
- 10:10: GrimoireLabs implementation
- 12:30: Lunch
- 14:00: GrimoireLabs implementation
- 17:00: Quick retrospective, re-confirm next day schedule
- 17:30: Depart from TPB-B
Wednesday, Jan. 31
- 09:10: (A Sport Hotel) Departure, 15-20m walk to TPB-B
- 09:30: Arrival at TPB-B, Argentum Meeting Room (need RH badge for entry)
- 10:00: High-level refresh: goals for hackfest, schedule
- 10:10: Fedora elections discussion
- 12:30: Lunch
- 14:00: Fedora elections discussion
- 16:00: fedmsg plugins
- 17:00: Hackfest retrospective, GrimoireCon plans
- 18:00: Depart from TPB-B
Thursday, Feb. 1
Departure day.
- 12:38: (GrimoireCon) Train to Prague
External links
- Fedora Badges Hackfest planning (shared notes document)
- First announcement of Badges Hackfest planning
- Badges Hackfest 2020 schedule planning