Fedora Operations Architect
The Fedora Operations Architect (FOA) is employed full-time by Red Hat to assist the community in managing technical change. This includes change wrangling, schedule management, communications, and ownership of key strategic efforts. The Operations Architect also serves as a member of the Fedora Council. This role was created in 2023.
Current Fedora Operations Architect
Aoife Moloney is the current FOA. She is based in Waterford, Ireland and has been using Fedora Linux since 2018 when she joined the Red Hat Community Linux Engineering team. There, she served as a project manager, product owner, and general “cat herder”.
You can find Aoife on chat.fedoraproject.org as @amoloney:fedora.im, and she is happy to talk about anything.
Responsibilities
The Fedora Operations Architect is primarily responsible for coordinating technical change in the project. They work closely with a number of groups across the Fedora Project and have a range of responsibilities in each.
Manage the Changes Process
-
Shepherd Change proposals through the Changes process
-
Send reminders about upcoming deadlines in the release cycle for changes
-
Create tracker issues for accepted changes
-
Track the status of Changes during the development/testing cycle
-
Create and submit the Incomplete Changes Report to FESco
-
Maintain the Change Set Pages
-
-
Manage the Spins and Labs Keepalive process
Release Coordination and Management
-
Go/No-Go Meetings
-
Schedule Beta and Final meetings for Fedora Linux
-
Send reminders that these meetings are upcoming
-
Facilitate the meeting
-
Announce outcomes
-
-
Release Coordination
-
Work within the Release Day Fedora Chat/Matrix room to ensure all important details are raised for the upcoming release
-
Create Red Hat internal blog posts announcing Fedora Linux Beta and Fedora Linux Final releases
-
Work with Fedora Magazine for Fedora Linux release announcement articles
-
-
Perform mass updates of bugs at branch and end-of-life time
Elections
-
Running the Fedora Linux Elections
-
Opening elections cycle
-
Collecting and publishing candidate interviews
-
Creating and opening ballot box
-
Closing voting
-
Announcing the results
-
Council Administration
-
Creating council meeting agenda
-
Running the meetings
-
Assign and following up with action items
-
Post meeting agenda (ahead of), minutes and summary (after)
Fedora Forge Executive Sponsor for Council
-
Act as Council stakeholder to the project team, communicating Fedora Council (and at times, the wider Fedora Project’s) needs and requirements ahead of team sprint-planning
-
Support the development team by resolving any blockers within Council’s control or needs Council’s acknowledgment to proceed
-
Keep track of progress and encourage regular reporting from the team and provide regular status updates to the Fedora Council on the work
Release Party Team
-
Speaker Management and Coordination
-
Create and maintain the Release Party Schedule Wiki page
-
Build a shortlist of speakers and invite them to present at the event
-
Confirm speaker acceptance and schedule them based on their availability
-
Update schedule Wiki page with session information
See the Community Ops Fedora Docs page for how to contact and get in touch with the team.
Flock Organizer Team
-
Community Blog and Fedora Magazine
-
On the event website
-
In the Flock Fedora Chat/Matrix Room (
#flock:fedoraproject.org) -
Emails to
devel-announce@mailing list
History
This is a new role for Fedora, as of October 2023.
What about Fedora Program Manager (FPgM)?
In 2007, Red Hat began providing Fedora with assistance through a funded role in the company’s Program Management organization. In 2023, structural changes at the company eliminated this position. The Fedora Operations Architect is a new role situated in Linux Engineering at Red Hat, designed to be more closely aligned in both definition and practice with Fedora’s unique needs.
Former Fedora Program Managers
-
Ben Cotton (Fedora Linux 29–38)
-
Jan Kuřík (Fedora 23-28)
-
Jaroslav Řezník (Fedora 20-23)
-
Robyn Bergeron (Fedora 17-20)
-
John Poelstra (Fedora 8-16)
Want to help? Learn how to contribute to Fedora Docs ›