| |
@@ -0,0 +1,95 @@
|
| |
+ include::ROOT:partial$attributes.adoc[]
|
| |
+
|
| |
+ = Fedora Operations Architect
|
| |
+ :page-aliases: fpgm.adoc
|
| |
+
|
| |
+ 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]]
|
| |
+ == Current Fedora Operations Architect
|
| |
+
|
| |
+ [.profile-picture]
|
| |
+ image::amoloney.png[Aoife Moloney (she/her)]
|
| |
+
|
| |
+ 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 xref:cpe::index.adoc[Community Platform 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]]
|
| |
+ == 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.
|
| |
+
|
| |
+ [[responsibilities-changes]]
|
| |
+ === Manage the Changes Process
|
| |
+
|
| |
+ * Shepherd Change proposals through the xref:program_management::changes_policy.adoc[Changes process]
|
| |
+ ** Work with Change Owners to present their Changes to the community
|
| |
+ ** Create tracker issues for accepted changes
|
| |
+ ** Track the status of Changes during the development/testing cycle
|
| |
+
|
| |
+ [[responsibilities-releases]]
|
| |
+ === Manage Release Coordination
|
| |
+
|
| |
+ * https://fedorapeople.org/groups/schedule/[Schedule] xref:releases::index.adoc[Fedora Linux releases]
|
| |
+ * Coordinate Engineering release readiness (e.g. Quality Team, Release Engineering, FESCo, etc.)
|
| |
+ * Coordinate Mindshare release readiness (e.g. xref:marketing::index.adoc[Marketing Team], xref:websites::index.adoc[Websites & Apps Team], xref:fedora-docs::index.adoc[Docs Team], xref:fedora-magazine::index.adoc[Fedora Magazine], etc.)
|
| |
+ * Manage the Spins keep-alive process
|
| |
+ * Perform mass updates of bugs at branch and end-of-life time
|
| |
+
|
| |
+ [[responsibilities-council]]
|
| |
+ === Work with the Fedora Council
|
| |
+
|
| |
+ * Serve as a member of the Fedora Council
|
| |
+ * Act as Fedora Council secretary
|
| |
+ ** Prepare Council meeting agendas
|
| |
+ ** Periodically review backlog of Fedora Council tickets
|
| |
+ ** Chair meetings
|
| |
+ ** Invite community stakeholders to present periodically in video meeting updates
|
| |
+ * Support the advancement of strategic xref:project::initiatives.adoc[Community Initiatives]
|
| |
+ * Act as a Council stakeholder to teams within the project
|
| |
+ * Represent community interests around the schedule and change management to the Council
|
| |
+
|
| |
+ [[responsibilities-community]]
|
| |
+ === To the Fedora community
|
| |
+
|
| |
+ * Elections
|
| |
+ ** Running elections for Fedora Council, Mindshare and FESCo
|
| |
+ ** Support elected teams with documentation and permissions changes (if needed) after an election ends
|
| |
+ ** Ad hoc election support for other teams when needed
|
| |
+ * Reports
|
| |
+ ** Provide the community with regular reports on the activities of the project
|
| |
+ * Participate in various community teams, eg xref:commops::index.adoc[Community Operations]
|
| |
+ * Events
|
| |
+ ** Assist the xref:fca.adoc[Community Architect] in coordinating Fedora flagship events (e.g. Flock/Nest, Release Parties)
|
| |
+ ** Take part in (and sometimes host!) all fun community events!
|
| |
+
|
| |
+
|
| |
+ [[history]]
|
| |
+ == History
|
| |
+
|
| |
+ This is a new role for Fedora, https://fedoramagazine.org/introducing-fedora-operations-architect/[as of October 2023].
|
| |
+
|
| |
+ [[history-fpgm]]
|
| |
+ === 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.
|
| |
+
|
| |
+ [[history-fpgms]]
|
| |
+ === Former Fedora Program Managers
|
| |
+
|
| |
+ * link:{FWIKI}/User:Bcotton[Ben Cotton] (Fedora Linux 29–38)
|
| |
+ * link:{FWIKI}/User:Jkurik[Jan Kuřík] (Fedora 23-28)
|
| |
+ * link:{FWIKI}/User:Jreznik[Jaroslav Řezník] (Fedora 20-23)
|
| |
+ * link:{FWIKI}/User:Rbergero[Robyn Bergeron] (Fedora 17-20)
|
| |
+ * link:{FWIKI}/User:Poelstra[John Poelstra] (Fedora 8-16)
|
| |
mattdm
commented a year ago
The Fedora Council charter assumed the existence of a funded-by-Red-Hat Program Manager role. That position no longer exists. However, Red Hat is hiring for a new role to support Fedora. This updates our charter to include that position instead.
Please do not merge until to-be-filed-soon council ticket is resolved.