Council Strategy Summit 2026 – 2-6 February 2026 – Tirana, Albania #555
Labels
No labels
category
budget
category
code-of-conduct
category
docs
category
elections
category
events
category
initiatives
category
mindshare
category
policies
category
spending-request
category
Strategy Summit
category
trademarks
Next Meeting
state
resolved
good first issue
help wanted
needs
changes
needs
reporter feedback
needs
triage
needs
vote
role
engineering
role
fca
role
foa
role
fpl
role
initiative lead
role
mindshare
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Reference
council/tickets#555
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
This ticket proposes the Fedora Council 2026 Strategy Summit in Tirana, Albania, requiring full-day engagement from February 3–5, 2026, to align leadership on Strategy & Governance, Engineering, and critical Community Initiatives.
Background
The annual Fedora Council Strategy Summit provides a high-bandwidth, in-person environment for the Council to focus exclusively on the project's health, vision, and strategic direction. This 2026 summit is particularly critical as it will be the first for the new Fedora Project Leader, @jspaleta, providing a prime opportunity to set a cohesive vision for the future of Fedora. Participants are expected to arrive in Tirana on Monday, February 2, 2026, for three full working days from Tuesday, February 3 to Thursday, February 5, before departing on Friday, February 6.
The agenda is structured around three strategic pillars: Strategy & Governance, Initiatives, and Engineering. A significant portion of the summit is dedicated to Community Initiatives, where the four Council members serving as Initiative Leads will present on the state of their Initiatives such as the Git Forge 2025 Initiative, Fedora Docs 2025 Initiative, Fedora bootc 2026 Initiative to identify blockers and resource needs. Additionally, the Council will focus on operationalizing the Fedora Strategy 2028 and addressing technical topics such as Konflux, AI, and Flatpak/Flathub. To ensure transparency, the Council commits to a communication plan following the summit, which will include a public-facing report on Fedora Magazine and a presentation to the Fedora/RHEL/CentOS Leadership (FRCL).
Details
To move this event from the planning phase to execution, specific administrative actions are required from Council members regarding budget forecasting and attendance confirmation. Furthermore, while the agenda has been iteratively developed, we are now soliciting feedback from the wider community before finalizing the schedule in early January 2026.
Outcome
Generate clear, tactical outputs for the Fedora Strategy 2028, ensure robust support for the Community Initiatives driven by Council leadership, and achieve alignment on major engineering shifts like Konflux, AI, and Flatpak/Flathub.
See linked Fedora Discussion topic for Ticket 555
Discussed during the 2025-12-17 Council meeting.
The Council held a final check-in regarding the upcoming Strategy Summit in Tirana. That week was the final week for input, with @jflory7 and @jspaleta finalizing the agenda on Friday, December 18th to ensure stability leading into January. The Council emphasized that if any critical topics are missing from the agenda, they must be raised immediately before the holiday break. Brief travel logistics were also clarified, noting that while the hotel bookings are centrally managed, attendees are generally responsible for booking their own airfare.
Discussed during the 2026-01-14 Council meeting.
At the January 14th meeting, the Fedora Council finalized logistics for the 2026 Strategy Summit (Feb 2-6, 2026) in Tirana, Albania, confirming the venue and instructing non-Red Hat travelers to coordinate bookings with @jflory7. We assigned leadership pairs to the primary agenda items, with @dcantrell and @jspaleta leading the Flatpak/Flathub strategy, and @bookwar joining @jspaleta to lead the Konflux/git forge discussion. Remote participation hardware is currently being tested, and all remote attendees are asked to log their time availability on the Wiki.
Strategy Summit Recap (Tirana, February 3–5, 2026)
As an experiment in transparency, the Fedora Council posted daily summaries to this Fedora Discussion thread throughout the summit instead of waiting for a single post-event Magazine article — we collaboratively drafted and edited each day's summary together as a closing task before posting, and the community engaged directly with each day's summary in the thread. Recapping here for the ticket record:
Day 1 — Strategy & Governance: @jspaleta introduced a "Fedora as a University" model for Council governance, with the Council acting more like university regents chartering and supporting semi-autonomous "departments" (SIGs, Editions, Working Groups) rather than a corporate board. We also opened the Open Collective discussion that became #561.
Day 2 — Initiatives & Engagement Metrics: Community Initiative Leads gave status updates, including @ryanlerch on the Git Forge 2025 migration progress, @pboy and @pbokoc on the Fedora Docs 2025 Initiative, and @nimbinatus on the Fedora Atomic Desktops Initiative. @ryanlerch and @nimbinatus joined virtually from home for their presentations. We also worked through an engagement-metrics exercise with @alking.
Day 3 — Engineering: @jspaleta laid out five problem statements on Fedora's relationship with Flatpak/Flathub (default enablement, single-maintainer bottleneck, SIG mission statement, upstream relationship, and Freedesktop spec issues), which we mapped to next steps. We also covered Konflux and closed with a retrospective on the summit format itself.
Community discussion that followed: The thread generated substantive discussion beyond the daily summaries, most notably on the membership/voting eligibility policy floated during Day 1 — whether "non_cla" FAS groups are too easy to game for election eligibility, and what an "active lifecycle" membership model (similar to openSUSE's Emeritus Member status) could look like. @bookwar, @pbokoc, and @jspaleta fielded most of the community questions on this, and it's clear this needs its own dedicated proposal and community review rather than resolution in a Discourse thread — that work continues in #557. There was also a good-natured but real critique (@adamwill, @cverna) that the "university" metaphor is US-centric, with @cverna offering a Kubernetes/microservices alternative.
We held the planned video call follow-up on February 25, opened with a presentation from @jspaleta and community Q&A, and gave the FRCL presentation on the summit outcomes afterward as committed to above.
Forward progress: #557 (membership/voting eligibility, from the Day 1 discussion), #561 (Open Collective, from the Day 1 discussion), and #570 (public-facing outreach coordination) all continue work that came out of this summit. I'm marking those as depending on this ticket to keep the lineage visible, and closing this one out now that the summit itself is complete.
Thanks to everyone who traveled to Tirana, to @jonatoni for handling local logistics and the hotel block, and to everyone in the Discussion thread who engaged with the daily updates.
Assisted-by: Claude Sonnet 5 (1M context)