We’re working on filling out the Logic Model for the strategy overall. We’ve identified four areas where we have immediate work in progress:
- Mentorship (see: https://fedoraproject.org/wiki/Initiatives/and Mentored_Projects_2024 mentored-projects-team )
- Collaboration & Communication Tooling (four areas: git-forge-future, bug-tracking future, moving mailing lists to Discussion, and Matrix as official real-time communications platform)
- Image-Based OS: (See Initiatives/Fedora bootc - Fedora Project Wiki and bootc-initiative)
- AI: (tbd, but see Fedora-Council/tickets ticket #486: Discuss and decide on a Fedora Council policy on the use of AI-based tooling for contributions and 2024-05-22 Council meeting summary)
We decided today to focus on identifying key stakeholder groups for selected projects in these areas (like the above initiatives). Each initiative lead will consult with those stakeholders to develop specific short- and medium-term Outcomes[1], and the Outputs[2]
Today, we (mostly) completed this for the Modernize Comms Tooling Objective. We’ve decided that, rather than trying to schedule half-day working sessions to continue, we’re going to schedule two video meetings weekly[3] until we’re done. Not every council member will be able to make every meeting (today, there were five of us), and that’s totally okay. We’ll adjust each meeting’s content for the people who can make it.
When that’s done, we’ll move forward with three things in parallel:
- the leads for each Initiative will identify Activities required for each Output, and then the Inputs (people, time, system resources, money) needed for each Activity.
- actually doing those Activities
- continuing the stakeholder/leader process for the Objectives we’ve tagged with the next priority level: revamping Fedora SIGs, improving Spins & Rebuilds[4], and (re-)building support for our local communities.
measurable changes which result from our efforts, and which lead to the Objectives and Impact we’ve already identified in each area ↩︎
Tangible things we will produce which are necessary and sufficient for every desired Outcome ↩︎
excepting the DevConf.cz week ↩︎
this might increase in scope to bigger build pipeline improvements ↩︎