council/flock
council/flock
12
0
Fork 0
Code Issues 6 Pull requests Projects Activity

📝 README: Add comprehensive Flock 2026 planning guide

Browse source 
Establishes the README as the central reference document for the Flock
to Fedora 2026 planning effort. This was drafted after reviewing the
full history of bi-weekly planning call notes (Aug 2025 -- Apr 2026),
the event checklist, timeline, and the 37 legacy Flock 2024 issues
migrated from GitLab.com.

The README covers the event overview (dates, venue, schedule, CfP
themes), the planning team and their role assignments, a complete guide
to the issue tracker's label taxonomy and milestones, the planning
timeline and its six phases, sponsorship information, and contribution
guidelines.

The label taxonomy documented here reflects a deliberate redesign: repo-
specific `area/*` labels (non-exclusive, for workstream tagging) and
`priority/*` labels (exclusive) complement the inherited org-level
labels from the Fedora Council organization on Forgejo. This replaces
the original flat label set carried over from GitLab.com.

Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
This commit is contained in:
Justin Wheeler 2026-04-09 00:13:23 -04:00
commit 323f6acaf0
Signed by: jflory7
GPG key ID: 7748B15FA8FA4C7E
1 changed files with 184 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

184
README.md Normal file
View file

@ -0,0 +1,184 @@
# Flock to Fedora 2026
**June 14--16, 2026 | Prague, Czech Republic**
Flock to Fedora is the annual contributor conference for the [Fedora Project](https://fedoraproject.org/).
It brings together Fedora contributors, users, and upstream developers for talks, workshops, hackfests, and social activities focused on the project's future.
Flock 2026 will be held at the [Vienna House by Wyndham Anděl's Prague](https://www.wyndhamhotels.com/vienna-house/prague-czech-republic/vienna-house-andels-prague/overview) in the Anděl neighborhood of Prague.
The conference follows [DevConf.CZ](https://devconf.cz/) (June 18--20 in Brno), making it possible for attendees to participate in both events during a single trip.
## 📅 Schedule at a glance
| Day | Date | Focus |
|-----|------|-------|
| Day 0 | Sunday, June 14 | Meetups, workshops, and hands-on contributor sessions |
| Day 1 | Monday, June 15 | Opening keynote, plenary sessions, breakout rooms, main social event |
| Day 2 | Tuesday, June 16 | Plenary sessions, breakout rooms, closing remarks, sponsor dinner |
Saturday, June 13 is the travel and arrival day.
The conference hotel room block covers June 13--17 and includes breakfast.
## 🎤 CfP themes
The Call for Proposals was organized around Fedora's four foundations:
- **Freedom: The Open Frontier** -- FOSS approaches to AI, open hardware (RISC-V), open standards, and data privacy
- **Friends: Our Fedora Story** -- Mentorship, team collaboration, onboarding, and partnerships with other FOSS communities
- **Features: Engineering Fedora's Core** -- Infrastructure, release engineering, quality assurance, packaging, and community tooling
- **First: Blueprint for the Future: Fedora Linux 45 & 46** -- Near-term innovations for F45/F46, the foundation for RHEL 11 and EPEL 11
## 📦 About this repository
The Fedora Council and the Flock Organizing Team use this repository to plan and coordinate the Flock conference.
It is hosted on the [Fedora Project Forgejo instance](https://forge.fedoraproject.org/council/flock).
### What lives here
- **Issue tracker** -- The primary tool for tracking planning tasks across all workstreams (sponsorships, speaker management, venue logistics, design, marketing, registration, etc.)
- **Scripts and tooling** -- Automation to support the planning team's workflow (e.g., Forgejo API scripts for label/milestone management, issue triage)
- **Documentation** -- This README and supporting reference material for the planning team
### What lives elsewhere
| Resource | Location |
|----------|----------|
| CfP platform (Pretalx) | [cfp.fedoraproject.org](https://cfp.fedoraproject.org/flock-to-fedora-2026/) |
| Registration (Pretix) | [rsvp.fedoraproject.org](https://rsvp.fedoraproject.org/community/flock-2026/) |
| Event website | [fedoraproject.org/flock](https://fedoraproject.org/flock/) |
| Planning deck (slides) | [Google Slides](https://docs.google.com/presentation/d/1XEfi0h4N56Whe-1Tv7PB8orM4cWDC7BEtUanDznEV_8/edit?usp=sharing) |
| Shared drive | [Google Drive -- Flock 2026](https://drive.google.com/drive/folders/1vFu5FZRkLyR4dHXy9xSCi6tFQo4WJe4I?usp=drive_link) |
| Budget | [Flock 2026 Expense Scratchpad](https://docs.google.com/spreadsheets/d/1C2Tjs84UW6EVGobM89hdYvYM5efuhjTLLBmrKD_bUsw/edit?usp=sharing) |
| Design epic | [Fedora Design Team GitLab epic](https://gitlab.com/groups/fedora/design/team/-/epics/8) |
| Sponsor prospectus | [Google Slides](https://docs.google.com/presentation/d/1po9DzrIjanmte6_kE32wvQ9oSsAdL9bzhvdPKMtT7lw/edit?usp=sharing) |
## 👥 Planning team
Flock is organized by volunteers and Red Hat community team staff working under the direction of the [Fedora Council](https://docs.fedoraproject.org/en-US/council/).
| Role | Lead(s) |
|------|---------|
| Overall coordination | Justin Wheeler (FCA) |
| CfP and schedule | Justin Wheeler, Lidija Balija |
| Sponsor management | Justin Wheeler, Shaun McCance |
| Speaker management | Justin Wheeler, Lidija Balija |
| Social events and venue logistics | Dorota "Dorka" Volavkova |
| Design | Emma Kidney, Madeline Peck |
| Marketing and comms | Justin Wheeler, Shaun McCance |
| Travel sponsorships | Justin Wheeler, Juliana Furlow |
| Website | Shaun McCance, Jason Brooks (backup), Jess Chitas (redesign) |
### Communication channels
- **Flock Staff mailing list:** flock-staff@fedoraproject.org
- **Sponsor inquiries:** sponsors@fedoraproject.org
- **Planning calls:** Bi-weekly (switching to weekly closer to the event)
- **Chat:** Flock Staff channel on Red Hat Slack; Fedora Matrix channels
## 🏷️ Issue tracker guide
Issues in this repository represent planning tasks for Flock.
They are organized using **labels** and **milestones**.
### Labels
Labels are split between the [council org-level labels](https://forge.fedoraproject.org/org/council/settings/labels) (shared across all Council repos) and repo-specific labels defined here.
#### Repo labels: area (what workstream -- non-exclusive, multiple can apply)
| Label | Description |
|-------|-------------|
| `area/CfP & Schedule` | Call for Proposals, schedule building, session management |
| `area/Design & Swag` | Branding, t-shirts, stickers, badges, signage |
| `area/Marketing & Comms` | Blog posts, social media, website, announcements |
| `area/Registration` | Pretix platform, attendee management, check-in |
| `area/Social Events` | Evening activities, sponsor dinner, walking tours |
| `area/Speakers` | Speaker communications, onboarding, confirmations |
| `area/Sponsors` | Sponsor outreach, contracts, invoicing, fulfillment |
| `area/Travel & Financial Aid` | Travel sponsorships, BEAR approvals, reimbursements |
| `area/Venue & Logistics` | Room setup, AV, catering, hotel, accessibility |
| `area/Volunteers` | Recruitment, orientation, on-site coordination |
#### Repo labels: priority (how urgent -- exclusive, one per issue)
| Label | Description |
|-------|-------------|
| `priority/critical` | Blocking the event; resolve immediately |
| `priority/high` | Important for the current milestone |
| `priority/medium` | Should be done this milestone if possible |
| `priority/low` | Nice to have; can slip |
#### Org labels (inherited from council)
These labels are managed at the organization level and available across all Council repositories.
They cover roles (`role/fca`, `role/fpl`, `role/foa`, `role/engineering`, `role/mindshare`, `role/initiative lead`), triage states (`?/needs triage`, `?/needs changes`, `?/needs reporter feedback`, `?/needs vote`), scope (`scope/new`, `scope/improvement`, `scope/bug`), workflow state (`state/approved`, `state/blocked`, `state/duplicate`, `state/invalid`, `state/wontfix`), and community tags (`good first issue`, `help wanted`).
### Milestones
Milestones map to phases of the planning timeline:
| Milestone | Due | Purpose |
|-----------|-----|---------|
| April 2026: Schedule & Speakers | Apr 30 | Publish schedule, fill final slots, speaker checklist |
| May 2026: Pre-Event Prep | May 31 | Venue/AV finalization, swag, sponsor fulfillment, volunteers |
| June 1--13: Final Sprint | Jun 13 | Shipments, comms, volunteer orientation, last venue check-ins |
| June 14--16: Event | Jun 16 | On-site execution |
| Post-Event | Jul 31 | Survey, recordings, retrospective, reimbursements, sponsor follow-up |
## 🗓️ Timeline
### Key dates
| Date | Milestone |
|------|-----------|
| Nov 4, 2025 | Announce date, location, and timeline |
| Oct--Dec 2025 | Contact sponsors |
| Dec 8, 2025 | Open CfP and registration |
| Feb 2, 2026 | Soft close CfP |
| Feb 8, 2026 | Hard close CfP |
| Feb 9--28, 2026 | CfP review |
| Mar 2--6, 2026 | Speaker confirmations |
| Mar 8, 2026 | Deadline for financial aid form |
| Mar 23--27, 2026 | Publish initial schedule |
| Apr--Jun 2026 | Final logistics, swag orders, venue confirmation |
| Jun 14--16, 2026 | **Flock to Fedora 2026** |
| Jun 18--20, 2026 | DevConf.CZ (Brno, CZ) |
### Planning phases
The event checklist is organized into phases that correspond to milestones in the issue tracker:
1. **September--November** -- Venue, budget, sponsor prospectus, public announcement, design kickoff, registration and CfP platform setup
2. **December--February** -- CfP promotion, CfP review, sponsor outreach, travel sponsorship form, website updates, design assets
3. **March--April** -- Speaker notifications, schedule building, sponsor contract finalization, social event planning, swag orders, travel coordination
4. **April--June** -- Venue confirmation (A/V, catering, rooms), speaker updates, registration push, volunteer recruitment, swag shipping, final comms
5. **Event week** -- Opening remarks deck, venue check-in, volunteer orientation, shipment tracking
6. **Follow-up** -- Post-event survey, photo/recording publication, retrospective, reimbursements, budget reconciliation, sponsor thank-you notes
## 💰 Sponsorship
Flock is made possible by the support of Red Hat and external sponsors.
Sponsorship tiers are Bronze, Silver, and Gold, with optional add-ons.
Red Hat is listed as a Gold sponsor.
For sponsorship inquiries, contact **sponsors@fedoraproject.org**.
The [Sponsor Prospectus](https://docs.google.com/presentation/d/1po9DzrIjanmte6_kE32wvQ9oSsAdL9bzhvdPKMtT7lw/edit?usp=sharing) contains full details on tier benefits and pricing.
## 🤝 Contributing
Flock planning is a community effort.
If you would like to help, here are some ways to get involved:
1. **Browse issues labeled [`help wanted`](https://forge.fedoraproject.org/council/flock/issues?labels=help+wanted) or [`good first issue`](https://forge.fedoraproject.org/council/flock/issues?labels=good+first+issue)** for tasks where the team needs assistance.
2. **Join the conversation** on the Fedora Matrix channels or mailing lists.
3. **Volunteer on-site** -- closer to the event, we recruit volunteers for registration desk, A/V support, and attendee assistance.
## 📜 Code of Conduct
Flock to Fedora follows the [Fedora Code of Conduct](https://docs.fedoraproject.org/en-US/project/code-of-conduct/).
All participants, including speakers, sponsors, and volunteers, are expected to abide by it.
## ⚖️ License
Content in this repository is licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) unless otherwise noted.