From Fedora Project Wiki
No edit summary
mNo edit summary
 
(10 intermediate revisions by 6 users not shown)
Line 30: Line 30:
| 7 || [[User:Bt0dotninja|Alberto Rodríguez Sánchez]] || bt0dotninja || Mindshare Representative || N/A || yes || {{check}} || {{check}} || {{check}} || {{check}}
| 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] || Tirana, AL || 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 || N/A || yes || {{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}}
| 11 || [[User:Rwright|Robert Wright]] || rwright || Initiative Co-Lead || Brussels, BE || no || {{check}} || {{check}} || {{check}} || {{check}}
Line 58: Line 58:
* '''09:15''': Arrival at RH Amsterdam office, Young Meeting Room (''need RH badge for entry'')
* '''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
* '''09:30''': High-level refresh: goals for hackfest and current day schedule
* '''10:00''': Primary Goal 1
* '''10:00''': Strategy Review
* '''12:30''': Lunch
* '''12:30''': Lunch
* '''14:00''': Primary Goal 1
* '''14:00''': Strategy In Action
* '''17:00''': Quick retrospective, re-confirm next day schedule
* '''17:00''': Quick retrospective, re-confirm next day schedule
* '''17:30''': Depart from RH Amsterdam office
* '''17:30''': Depart from RH Amsterdam office
Line 69: Line 69:
* '''09:15''': Arrival at RH Amsterdam office, Fleury Meeting Room (''need RH badge for entry'')
* '''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
* '''09:30''': High-level refresh: goals for hackfest and current day schedule
* '''10:00''': Primary Goal 2
* '''10:00''': Fedora annd RHEL
* '''12:30''': Lunch
* '''12:30''': Lunch
* '''14:00''': Primary Goal 2
* '''14:00''': Git Forge Evaluation
* '''17:00''': Quick retrospective, re-confirm next day schedule
* '''17:00''': Quick retrospective, re-confirm next day schedule
* '''17:30''': Depart from RH Amsterdam office
* '''17:30''': Depart from RH Amsterdam office
Line 80: Line 80:
* '''09:15''': Arrival at RH Amsterdam office, Fleury Meeting Room (''need RH badge for entry'')
* '''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
* '''09:30''': High-level refresh: goals for hackfest and current day schedule
* '''10:00''': Primary Goal 3
* '''10:00''': CommOps 2.0 Reboot
* '''11:30''': Mentored Projects
* '''12:30''': Lunch
* '''12:30''': Lunch
* '''14:00''': Primary Goal 3
* '''14:00''': IRC & Matrix
* '''15:30''': Community Recognition
* '''17:00''': Quick retrospective, re-confirm next day schedule
* '''17:00''': Quick retrospective, re-confirm next day schedule
* '''17:30''': Depart from RH Amsterdam office
* '''17:30''': Depart from RH Amsterdam office
Line 91: Line 93:
* '''09:15''': Arrival at RH Amsterdam office, Fleury Meeting Room (''need RH badge for entry'')
* '''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
* '''09:30''': High-level refresh: goals for hackfest and current day schedule
* '''10:00''': Parking Lot (leftover topics from Primary Goals, Secondary Goals as time allows)
* '''10:00''': Governance and Administrative Topics - Video Call reboot, Elections scheduling, FPCA
* '''12:30''': Lunch
* '''12:30''': Lunch
* '''14:00''': Parking Lot (leftover topics from Primary Goals, Secondary Goals as time allows)
* '''14:00''': Parking Lot (leftover topics from Primary Goals, Secondary Goals as time allows)
Line 105: 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 117: 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 190: Line 191:
| 4 || [[User:T0xic0der|Akashdeep Dhar]] || t0xic0der || $1367 || $805 || $300 || '''$2472''' ||
| 4 || [[User:T0xic0der|Akashdeep Dhar]] || t0xic0der || $1367 || $805 || $300 || '''$2472''' ||
|-
|-
| 5 || [[User:Dcantrell|David Cantrell]] || dcantrell || $761.10 || $805 || style="background-color: red; color: #fff;" | $TBD || '''$1566.10''' ||
| 5 || [[User:Dcantrell|David Cantrell]] || dcantrell || $761 (air) + $45 (rail) || $805 || style="background-color: red; color: #fff;" | $TBD || '''$1611''' ||
|-
|-
| 6 || [[User:Jonatoni|Jona Azizaj]] || jonatoni || $450 || $805 || style="background-color: red; color: #fff;" | $TBD || '''$1255''' ||
| 6 || [[User:Jonatoni|Jona Azizaj]] || jonatoni || $450 || $805 || $150 || '''$1405''' ||
|-
|-
| 7 || [[User:Ffmancera|Fernando Fernandez Mancera]] || ffmancera || style="background-color: red; color: #fff;" | $TBD || $805 || style="background-color: red; color: #fff;" | $TBD || '''$805''' ||
| 7 || [[User:Ffmancera|Fernando Fernandez Mancera]] || ffmancera || style="background-color: red; color: #fff;" | $TBD || $805 || style="background-color: red; color: #fff;" | $TBD || '''$805''' ||
|-
|-
| 8 || [[User:Rwright|Robert Wright]] || rwright || N/A | $TBD || $805 || N/A || '''$805''' ||
| 8 || [[User:Rwright|Robert Wright]] || rwright || N/A || $805 || style="background-color: red; color: #fff;" | $TBD || '''$805''' ||
|-
|-
! Totals !! -- !! -- !! $3928.10 !! $6440 !! $600 !! $10968.10 !! --
! Totals !! -- !! -- !! $3973 !! $6440 !! $750 !! $11163 !! --
|}
|}


Latest revision as of 09:20, 6 February 2024

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
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 Boston, MA, US no
7 Alberto Rodríguez Sánchez bt0dotninja Mindshare Representative N/A yes
8 Jona Azizaj jonatoni DEI Advisor Tirana, AL no
9 Fernando Fernandez Mancera ffmancera Initiative Co-Lead Brussels, BE no
10 Smera Goel smeragoel Initiative Co-Lead N/A yes
11 Robert Wright rwright Initiative Co-Lead Brussels, BE no

 : present  : absent  : 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"