From Fedora Project Wiki
m (→‎Participants: Fix FAS ID)
mNo edit summary
 
(34 intermediate revisions by 9 users not shown)
Line 6: Line 6:
* ''Location'': Amsterdam, The Netherlands (Red Hat Amsterdam office)
* ''Location'': Amsterdam, The Netherlands (Red Hat Amsterdam office)
* ''Dates'': 6-9 February 2024
* ''Dates'': 6-9 February 2024
* ''Travel itinerary'':
** Participants arrive on Monday, 5 February
** Participants leave on Saturday, 10 February




Line 11: Line 14:


{|class="wikitable" border="1"
{|class="wikitable" border="1"
! 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)
! No !! Name !! FAS !! Role !! Origin location funded from/to !! Remote? !! Day 1 (Tue, 6 Feb) !! Day 2 (Wed, 7 Feb) !! Day 3 (Thu, 8 Feb) !! Day 4 (Fri, 9 Feb)
|-
|-
| 1 || [[User:Jflory7|Justin W. Flory]] || jflory7 || [https://docs.fedoraproject.org/en-US/council/fca/ Community Architect] || Brussels, BE || no || {{check}} || {{check}} || {{check}} || {{check}}
| 1 || [[User:Jflory7|Justin W. Flory]] || jflory7 || [https://docs.fedoraproject.org/en-US/council/fca/ Community Architect] || Brussels, BE || no || {{check}} || {{check}} || {{check}} || {{check}}
|-
|-
| 2 || [[User:Mattdm|Matthew Miller]] || mattdm || [https://docs.fedoraproject.org/en-US/council/fpl/ Project Leader] || Brussels, BE || no || {{question}} || {{question}} || {{question}} || {{question}}
| 2 || [[User:Mattdm|Matthew Miller]] || mattdm || [https://docs.fedoraproject.org/en-US/council/fpl/ Project Leader] || Brussels, BE || no || {{check}} || {{check}} || {{check}} || {{check}}
|-
|-
| 3 || [[User:Amoloney|Aoife Moloney]] || amoloney || [https://docs.fedoraproject.org/en-US/council/foa/ Operations Architect] || Brussels, BE || no || {{question}} || {{question}} || {{question}} || {{question}}
| 3 || [[User:Amoloney|Aoife Moloney]] || amoloney || [https://docs.fedoraproject.org/en-US/council/foa/ Operations Architect] || Brussels, BE || no || {{check}} || {{check}} || {{check}} || {{check}}
|-
|-
| 4 || [[User:Sumantro Mukherjee|Sumantro Mukherjee]] || sumantrom || Elected Representative || Kolkata, IN || no || {{question}} || {{question}} || {{question}} || {{question}}
| 4 || [[User:Sumantro Mukherjee|Sumantro Mukherjee]] || sumantrom || Elected Representative || Kolkata, IN || no || {{check}} || {{check}} || {{check}} || {{check}}
|-
|-
| 5 || [[User:T0xic0der|Akashdeep Dhar]] || t0xic0der || Elected Representative || Kolkata, IN || no || {{question}} || {{question}} || {{question}} || {{question}}
| 5 || [[User:T0xic0der|Akashdeep Dhar]] || t0xic0der || Elected Representative || Kolkata, IN || no || {{check}} || {{check}} || {{check}} || {{check}}
|-
|-
| 6 || [[User:Dcantrell|David Cantrell]] || dcantrell || Engineering Representative || ?? || no || {{question}} || {{question}} || {{question}} || {{question}}
| 6 || [[User:Dcantrell|David Cantrell]] || dcantrell || Engineering Representative || Boston, MA, US || no || {{check}} || {{check}} || {{check}} || {{check}}
|-
|-
| 7 || [[User:Bt0dotninja|Alberto Rodríguez Sánchez]] || bt0dotninja || Mindshare Representative || Mexico City, MX || no || {{question}} || {{question}} || {{question}} || {{question}}
| 7 || [[User:Bt0dotninja|Alberto Rodríguez Sánchez]] || bt0dotninja || Mindshare Representative || N/A || yes || {{check}} || {{check}} || {{check}} || {{check}}
|-
|-
| 8 || [[User:Jonatoni|Jona Azizaj]] || jonatoni || [https://docs.fedoraproject.org/en-US/dei/roles/council-advisor/ DEI Advisor] || Brussels, BE || no || {{question}} || {{question}} || {{question}} || {{question}}
| 8 || [[User:Jonatoni|Jona Azizaj]] || jonatoni || [https://docs.fedoraproject.org/en-US/dei/roles/council-advisor/ DEI Advisor] || Tirana, AL || no || {{check}} || {{check}} || {{check}} || {{check}}
|-
|-
| 9 || [[User:Ffmancera|Fernando Fernandez Mancera]] || ffmancera || Initiative Co-Lead || Brussels, BE || no || {{question}} || {{question}} || {{question}} || {{question}}
| 9 || [[User:Ffmancera|Fernando Fernandez Mancera]] || ffmancera || Initiative Co-Lead || Brussels, BE || no || {{check}} || {{check}} || {{check}} || {{check}}
|-
|-
| 10 || [[User:Smeragoel|Smera Goel]] || smeragoel || Initiative Co-Lead || ?? || ?? || {{question}} || {{question}} || {{question}} || {{question}}
| 10 || [[User:Smeragoel|Smera Goel]] || smeragoel || Initiative Co-Lead || N/A || yes || {{check}} || {{check}} || {{check}} || {{check}}
|-
| 11 || [[User:Rwright|Robert Wright]] || rwright || Initiative Co-Lead || Brussels, BE || no || {{check}} || {{check}} || {{check}} || {{check}}
|}
|}


Line 37: Line 42:
{{caution}} : absent
{{caution}} : absent
{{question}} : undecided
{{question}} : undecided
= Schedule =
All times in local time (CET / UTC+1).
== Monday, 5 February 2024 ==
Travel and arrival day. Welcome!
* '''19:00''': (''optional'') Welcome dinner and catching-up conversations before starting on the next day
== Tuesday, 6 February 2024 ==
* '''09:00''': (''Holiday Inn Express'') Departure, walk to RH Amsterdam office
* '''09:15''': Arrival at RH Amsterdam office, Young Meeting Room (''need RH badge for entry'')
* '''09:30''': High-level refresh: goals for hackfest and current day schedule
* '''10:00''': Strategy Review
* '''12:30''': Lunch
* '''14:00''': Strategy In Action
* '''17:00''': Quick retrospective, re-confirm next day schedule
* '''17:30''': Depart from RH Amsterdam office
== Wednesday, 7 February 2024 ==
* '''09:00''': (''Holiday Inn Express'') Departure, walk to RH Amsterdam office
* '''09:15''': Arrival at RH Amsterdam office, Fleury Meeting Room (''need RH badge for entry'')
* '''09:30''': High-level refresh: goals for hackfest and current day schedule
* '''10:00''': Fedora annd RHEL
* '''12:30''': Lunch
* '''14:00''': Git Forge Evaluation
* '''17:00''': Quick retrospective, re-confirm next day schedule
* '''17:30''': Depart from RH Amsterdam office
== Thursday, 8 February 2024 ==
* '''09:00''': (''Holiday Inn Express'') Departure, walk to RH Amsterdam office
* '''09:15''': Arrival at RH Amsterdam office, Fleury Meeting Room (''need RH badge for entry'')
* '''09:30''': High-level refresh: goals for hackfest and current day schedule
* '''10:00''': CommOps 2.0 Reboot
* '''11:30''': Mentored Projects
* '''12:30''': Lunch
* '''14:00''': IRC & Matrix
* '''15:30''': Community Recognition
* '''17:00''': Quick retrospective, re-confirm next day schedule
* '''17:30''': Depart from RH Amsterdam office
== Friday, 9 February 2024 ==
* '''09:00''': (''Holiday Inn Express'') Departure, walk to RH Amsterdam office
* '''09:15''': Arrival at RH Amsterdam office, Fleury Meeting Room (''need RH badge for entry'')
* '''09:30''': High-level refresh: goals for hackfest and current day schedule
* '''10:00''': Governance and Administrative Topics - Video Call reboot, Elections scheduling, FPCA
* '''12:30''': Lunch
* '''14:00''': Parking Lot (leftover topics from Primary Goals, Secondary Goals as time allows)
* '''17:00''': Final retrospective and summary of hackfest
* '''17:30''': Depart from RH Amsterdam office
== Saturday, 10 February 2024 ==
Travel and departure day. Safe travels home!


= Purpose =
= Purpose =
Line 42: Line 107:
The purpose of the Fedora Council 2024 Hackfest is accomplish the following:
The purpose of the Fedora Council 2024 Hackfest is accomplish the following:


# Example 1
# Deliver an effective and upgraded Fedora Strategy that aligns with current and future needs of the project, that has clear milestones defined to measure progress and key responsibilities assigned.
# Example 2
# To be aware of, and be able to plan support for the engineering needs of the project, by understanding the requirements, effort  and resources needed to manage the project wide changes effectively.
# Example 3
# To make sure the Community Objectives planned for this year are well supported and have clearly defined milestones to aid successful execution, and examine how the project is handling community relations in general in terms of recognition, communication and boarding, in order to do better in areas that need support.
 


= Impact =
= Impact =
Line 54: Line 118:
== Why this vision and mission? ==
== Why this vision and mission? ==


# Supporting evidence 1
# The Fedora Five-Year Strategy is in its second year, and we recognise the need to refine this to make it more measurable and accessible to the fedora community to engage with and align their work to.
# Supporting evidence 2
# There are several unknown engineering factors emerging this year, from the retirement of Bugzilla from RHEL, to newer ways to run operating systems. The fedora council needs to be aware of these changes, have conversations about the direction of the project overall, and make sure there is support and guidance available to the engineering teams within the t=project so that these major changes can be managed effectively and with the greatest amount of care and collaboration.
# Supporting evidence 3
# There are a number of objectives requiring more support and definition happening in the Fedora project that directly align with the five-year strategy. The council need to make sure these objectives have a clear remit and are well supported, so that they  can become a success story to share both in the project and throughout the open source community in general as a great example of community-led development.




Line 103: Line 167:


Descriptive text to provide more details about the goal and why it is important.
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 =


Logistics and event execution details for the hackfest.


== Planning pre-requisites ==
== Budget ==
 
* <strike>Publish wiki page proposal for feedback</strike>
* <strike>Create new [https://pagure.io/FedoraLogicModelTemplate logic model] based off [https://docs.google.com/document/d/15euqW6jAacRmyMeFCgTf0Wv2ov2qw9Ul8hZexY0qjDc/edit?usp=sharing original planning notes]</strike>
* Finalize participant list
* Calculate final budget
* Submit proposal to Fedora Council
* Complete supporting research leading up to hackfest
 
 
== Proposal: 2020 ==
 
# '''Location''': Brno, Czechia
# '''Dates''': 20-22 March 2020
# '''Travel itinerary''':
#* US-based participants arrive on Thursday evening, May 9th
#* International participants arrive on Wednesday evening, May 8th
#* Participants leave on Sunday night, May 12th
 


== Budget ==
This table represents the total event budget. Note that the amount proposed below is final, i.e. '''a sponsored attendee will NOT be reimbursed for more than what is written below'''.


{{admon/tip | Not yet finalized | Budget is not yet confirmed.}}
'''Please estimate all prices in USD'''. Use latest market rates for approximate conversions from EUR to USD on [https://www.xe.com/currencyconverter/convert/?Amount=1&From=EUR&To=USD xe.com].


{|class="wikitable" border="1"
{| class="wikitable"
! Contributor !! Travel plan !! Estimated travel cost (USD)
|-
|-
| [[User:Alishapapun|Alisha Mohanty]] || Bhubaneswar <=> DEL <=> ?? <=> PRG || $800
! No !! Name !! FAS !! Airfare and/or rail ($USD) !! Hotel ($USD) !! Incidentals¹ ($USD) !! Total ($USD) !! Comments
|-
|-
| [[User:Jflory7|Justin W. Flory]] || NYC <=> ?? <=> PRG || $1000
| 1 || [[User:Mattdm|Matthew Miller]] || mattdm || N/A || $805 || style="background-color: red; color: #fff;" | $TBD || '''$805''' ||
|-
|-
| [[User:Riecatnor|Marie Nordin]] || ROC <=> NYC <=> ?? <=> PRG || $900
| 2 || [[User:Amoloney|Aoife Moloney]] || amoloney || N/A || $805 || style="background-color: red; color: #fff;" | $TBD || '''$805''' ||
|-
|-
| [[User:Tatica|Maria Gracia Leandro Lombardo]] || CUC <=> ?? (not U.S.) <=> PRG || $1200
| 3 || [[User:Sumantro Mukherjee|Sumantro Mukherjee]] || sumantrom || $1350 || $805 || $300 || '''$2455''' ||
|-
|-
| [[User:Mleonova|Maria Leonova]] || BRQ || $0
| 4 || [[User:T0xic0der|Akashdeep Dhar]] || t0xic0der || $1367 || $805 || $300 || '''$2472''' ||
|-
|-
| [[User:Mattdm|Matthew Miller]] || BOS <=> PRG || $600
| 5 || [[User:Dcantrell|David Cantrell]] || dcantrell || $761 (air) + $45 (rail) || $805 || style="background-color: red; color: #fff;" | $TBD || '''$1611''' ||
|-
|-
| [[User:Misc|Michael S.]] || CDG <=> PRG || $120
| 6 || [[User:Jonatoni|Jona Azizaj]] || jonatoni || $450 || $805 || $150 || '''$1405''' ||
|-
|-
| [[User:Nb|Nick Bebout]] || Evanston <=> ORD/MDW <=> PRG || $925
| 7 || [[User:Ffmancera|Fernando Fernandez Mancera]] || ffmancera || style="background-color: red; color: #fff;" | $TBD || $805 || style="background-color: red; color: #fff;" | $TBD || '''$805''' ||
|-
|-
| [[User:Renata|Renata Gegaj]] || PRN <=> PRG || $200
| 8 || [[User:Rwright|Robert Wright]] || rwright || N/A || $805 || style="background-color: red; color: #fff;" | $TBD || '''$805''' ||
|-
| [[User:Sayanchowdhury|Sayan Chowdhury]] || BLR <=> ?? <=> PRG || $700
|-
| [[User:Shraddhaag|Shraddha Agrawal]] || DEL <=> ?? <=> PRG || $800
|-
| [[User:Tanvi|Tanvi Shrivastava]] || BLR <=> ?? <=> PRG || $700
|-
| [[User:Laxathom|Xavier Lamien]] || Paris <=> PRG || ~$120
|-
| Round Trip Prague to Brno for 8 attendees || PRG <=> BRQ || $400
|-
|-
! Totals !! -- !! -- !! $3973 !! $6440 !! $750 !! $11163 !! --
|}
|}


# '''Travel:''' ~$8145 USD (''anticipated'')
¹ — Taxi, meals, visas, travel insurance, other minor incidentals. Confirm other expense types with Community Architect before proposing here.
# '''Accommodation''' (10 attendees): ~$2500 USD
# '''Location''': $0
#* Red Hat Czech s.r.o.
# '''Meals''': ~$1500 USD (''food for 10 for 3.5 days, inc. one social dinner'')c


'''Total budget: ~$12,145 USD
= 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.


<!-- We'll fill this part out closer to the hackfest.
= 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''': [https://pagure.io/fedora-commops/issue/110 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 =
= External links =


* [https://docs.google.com/document/d/15euqW6jAacRmyMeFCgTf0Wv2ov2qw9Ul8hZexY0qjDc/edit?usp=sharing Fedora Badges Hackfest planning] (shared notes document)
* [https://pagure.io/Fedora-Council/tickets/issue/469 Issue #469: Fedora Council Hackfest 2024 - tickets - Pagure.io]
* [https://lists.fedoraproject.org/archives/list/badges@lists.fedoraproject.org/thread/E5YNZ2CUEJEJJBSGFK2IKQP4HCN2LJQX/ First announcement of Badges Hackfest planning]
* [https://discussion.fedoraproject.org/t/fedora-council-tickets-ticket-469-fedora-council-hackfest-2024/94761 Fedora-Council/tickets ticket #469: Fedora Council Hackfest 2024 - Fedora Discussion]
* [https://docs.google.com/spreadsheets/d/1wZBPXCfOa61loLFJxlhoVYaZNYEXXPlBpXlfjQjXqlI/edit?usp=sharing Badges Hackfest 2020 schedule planning]


----
----
[[Category:Council]]
[[Category:Council]]
[[Category:FAD]]
[[Category:FAD]]

Latest revision as of 09:20, 6 February 2024

Warning.png
This page is a draft only
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 funded from/to 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 Checkmark.png Checkmark.png Checkmark.png Checkmark.png
2 Matthew Miller mattdm Project Leader Brussels, BE no Checkmark.png Checkmark.png Checkmark.png Checkmark.png
3 Aoife Moloney amoloney Operations Architect Brussels, BE no Checkmark.png Checkmark.png Checkmark.png Checkmark.png
4 Sumantro Mukherjee sumantrom Elected Representative Kolkata, IN no Checkmark.png Checkmark.png Checkmark.png Checkmark.png
5 Akashdeep Dhar t0xic0der Elected Representative Kolkata, IN no Checkmark.png Checkmark.png Checkmark.png Checkmark.png
6 David Cantrell dcantrell Engineering Representative Boston, MA, US no Checkmark.png Checkmark.png Checkmark.png Checkmark.png
7 Alberto Rodríguez Sánchez bt0dotninja Mindshare Representative N/A yes Checkmark.png Checkmark.png Checkmark.png Checkmark.png
8 Jona Azizaj jonatoni DEI Advisor Tirana, AL no Checkmark.png Checkmark.png Checkmark.png Checkmark.png
9 Fernando Fernandez Mancera ffmancera Initiative Co-Lead Brussels, BE no Checkmark.png Checkmark.png Checkmark.png Checkmark.png
10 Smera Goel smeragoel Initiative Co-Lead N/A yes Checkmark.png Checkmark.png Checkmark.png Checkmark.png
11 Robert Wright rwright Initiative Co-Lead Brussels, BE no Checkmark.png Checkmark.png Checkmark.png Checkmark.png

Checkmark.png : present Warning.png : absent Questionmark.png : undecided

Schedule

All times in local time (CET / UTC+1).

Monday, 5 February 2024

Travel and arrival day. Welcome!

  • 19:00: (optional) Welcome dinner and catching-up conversations before starting on the next day

Tuesday, 6 February 2024

  • 09:00: (Holiday Inn Express) Departure, walk to RH Amsterdam office
  • 09:15: Arrival at RH Amsterdam office, Young Meeting Room (need RH badge for entry)
  • 09:30: High-level refresh: goals for hackfest and current day schedule
  • 10:00: Strategy Review
  • 12:30: Lunch
  • 14:00: Strategy In Action
  • 17:00: Quick retrospective, re-confirm next day schedule
  • 17:30: Depart from RH Amsterdam office

Wednesday, 7 February 2024

  • 09:00: (Holiday Inn Express) Departure, walk to RH Amsterdam office
  • 09:15: Arrival at RH Amsterdam office, Fleury Meeting Room (need RH badge for entry)
  • 09:30: High-level refresh: goals for hackfest and current day schedule
  • 10:00: Fedora annd RHEL
  • 12:30: Lunch
  • 14:00: Git Forge Evaluation
  • 17:00: Quick retrospective, re-confirm next day schedule
  • 17:30: Depart from RH Amsterdam office

Thursday, 8 February 2024

  • 09:00: (Holiday Inn Express) Departure, walk to RH Amsterdam office
  • 09:15: Arrival at RH Amsterdam office, Fleury Meeting Room (need RH badge for entry)
  • 09:30: High-level refresh: goals for hackfest and current day schedule
  • 10:00: CommOps 2.0 Reboot
  • 11:30: Mentored Projects
  • 12:30: Lunch
  • 14:00: IRC & Matrix
  • 15:30: Community Recognition
  • 17:00: Quick retrospective, re-confirm next day schedule
  • 17:30: Depart from RH Amsterdam office

Friday, 9 February 2024

  • 09:00: (Holiday Inn Express) Departure, walk to RH Amsterdam office
  • 09:15: Arrival at RH Amsterdam office, Fleury Meeting Room (need RH badge for entry)
  • 09:30: High-level refresh: goals for hackfest and current day schedule
  • 10:00: Governance and Administrative Topics - Video Call reboot, Elections scheduling, FPCA
  • 12:30: Lunch
  • 14:00: Parking Lot (leftover topics from Primary Goals, Secondary Goals as time allows)
  • 17:00: Final retrospective and summary of hackfest
  • 17:30: Depart from RH Amsterdam office

Saturday, 10 February 2024

Travel and departure day. Safe travels home!

Purpose

The purpose of the Fedora Council 2024 Hackfest is accomplish the following:

  1. Deliver an effective and upgraded Fedora Strategy that aligns with current and future needs of the project, that has clear milestones defined to measure progress and key responsibilities assigned.
  2. To be aware of, and be able to plan support for the engineering needs of the project, by understanding the requirements, effort and resources needed to manage the project wide changes effectively.
  3. To make sure the Community Objectives planned for this year are well supported and have clearly defined milestones to aid successful execution, and examine how the project is handling community relations in general in terms of recognition, communication and boarding, in order to do better in areas that need support.

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?

  1. The Fedora Five-Year Strategy is in its second year, and we recognise the need to refine this to make it more measurable and accessible to the fedora community to engage with and align their work to.
  2. There are several unknown engineering factors emerging this year, from the retirement of Bugzilla from RHEL, to newer ways to run operating systems. The fedora council needs to be aware of these changes, have conversations about the direction of the project overall, and make sure there is support and guidance available to the engineering teams within the t=project so that these major changes can be managed effectively and with the greatest amount of care and collaboration.
  3. There are a number of objectives requiring more support and definition happening in the Fedora project that directly align with the five-year strategy. The council need to make sure these objectives have a clear remit and are well supported, so that they can become a success story to share both in the project and throughout the open source community in general as a great example of community-led development.


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.


Logistics

Logistics and event execution details for the hackfest.

Budget

This table represents the total event budget. Note that the amount proposed below is final, i.e. a sponsored attendee will NOT be reimbursed for more than what is written below.

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) Incidentals¹ ($USD) Total ($USD) Comments
1 Matthew Miller mattdm N/A $805 $TBD $805
2 Aoife Moloney amoloney N/A $805 $TBD $805
3 Sumantro Mukherjee sumantrom $1350 $805 $300 $2455
4 Akashdeep Dhar t0xic0der $1367 $805 $300 $2472
5 David Cantrell dcantrell $761 (air) + $45 (rail) $805 $TBD $1611
6 Jona Azizaj jonatoni $450 $805 $150 $1405
7 Fernando Fernandez Mancera ffmancera $TBD $805 $TBD $805
8 Robert Wright rwright N/A $805 $TBD $805
Totals -- -- $3973 $6440 $750 $11163 --

¹ — Taxi, meals, visas, travel insurance, other minor incidentals. Confirm other expense types with Community Architect before proposing here.

Q&A

  1. Is this realistic to accomplish?
    • Answer here.
  2. Does everyone need to be in the same room for this to happen?
    • Answer here.
  3. What happens if this hackfest does not happen?
    • Answer here.


External links

Retrieved from "https://fedoraproject.org/w/index.php?title=Council/2024_Hackfest&oldid=700129"