From 514905ef770340f1a3423290a2bc88c114a074c8 Mon Sep 17 00:00:00 2001
From: Matthew Miller <mattdm@mattdm.org>
Date: Oct 25 2023 15:20:49 +0000
Subject: [PATCH 1/2] docs(council): Convert Program Manager to Operations Architect


ref: https://pagure.io/Fedora-Council/tickets/issue/462

---

diff --git a/council/modules/ROOT/nav.adoc b/council/modules/ROOT/nav.adoc
index 01f11f4..1952ef1 100644
--- a/council/modules/ROOT/nav.adoc
+++ b/council/modules/ROOT/nav.adoc
@@ -5,7 +5,7 @@ include::ROOT:partial$attributes.adoc[]
 * xref:members.adoc[Current Council Members]
 ** xref:fpl.adoc[Fedora Project Leader]
 ** xref:fca.adoc[Fedora Community Architect]
-** xref:fpgm.adoc[Fedora Program Manager]
+** xref:foa.adoc[Fedora Operations Architect]
 ** xref:dei:roles:council-advisor.adoc[Fedora DEI Advisor]
 * Council Policies
 ** xref:policy/coc-response-policy.adoc[Code of Conduct Response Policy]
diff --git a/council/modules/ROOT/pages/foa.adoc b/council/modules/ROOT/pages/foa.adoc
new file mode 100644
index 0000000..50bcb1b
--- /dev/null
+++ b/council/modules/ROOT/pages/foa.adoc
@@ -0,0 +1,6 @@
+= Fedora Operations Architect =
+
+
+This role replaces the previous xref:fpgm.adoc[Fedora Program Manager] position. 
+
+Full description to be developed.
diff --git a/council/modules/ROOT/pages/index.adoc b/council/modules/ROOT/pages/index.adoc
index bc2301e..4bd216c 100644
--- a/council/modules/ROOT/pages/index.adoc
+++ b/council/modules/ROOT/pages/index.adoc
@@ -134,14 +134,14 @@ The Fedora Project Leader is hired by Red Hat with the advice and consent of the
 The xref:fca.adoc[Fedora Community Architect] (FCA) works to grow the Fedora user and developer communities, and to make Red Hat / Fedora interactions even more transparent and positive.
 The Fedora community budget comes to us through the Red Hat Open Source Program Office, and this position facilitates decision-making on how to best focus that to meet our collective objectives.
 
-[[composition-appointed-fpgm]]
-==== Fedora Program Manager (FPgM)
+[[composition-appointed-foa]]
+==== Fedora Operations Architect
 
-The xref:fpgm.adoc[Fedora Program Manager] (FPgM) coordinates the planning and scheduling of Fedora releases, and tracks changes and features during the development and testing cycle.
-He or she also assists with the creation, maintenance, and execution of formal, repeatable Fedora processes.
-Additionally, the FPgM serves as record keeper and secretary for {team_name} meetings.
+The Fedora Operations Architect (FOA) guides contributors proposing and implementing Fedora Linux changes and features and coordinates the planning and scheduling of our release cycle.
+They also assist with the creation, improvement, maintenance, and execution of formal, repeatable Fedora processes.
+Additionally, the FOA serves as record-keeper and secretary for Fedora Council Meetings.
 
-This position is funded by and hired for by Red Hat, with the approval of the {team_name}.
+This position is funded by and hired for by Red Hat, with the approval of the Council.
 
 
 [[coda]]
diff --git a/council/modules/ROOT/pages/procedures/welcome.adoc b/council/modules/ROOT/pages/procedures/welcome.adoc
index 3eff160..c87c107 100644
--- a/council/modules/ROOT/pages/procedures/welcome.adoc
+++ b/council/modules/ROOT/pages/procedures/welcome.adoc
@@ -33,7 +33,7 @@ Think of it as finding a bug in the documentation!
 [[access]]
 == Access
 
-When you were elected or appointed to the {team_name}, the xref:fpgm.adoc[FPgM] (or someone else) opened an issue in our link:{team_issue_tracker}[ticket tracker].
+When you were elected or appointed to the {team_name}, the xref:foa.adoc[Fedora Operations Architect] (or someone else) opened an issue in our link:{team_issue_tracker}[ticket tracker].
 This provides a checklist for all of the places you need to be granted access.
 Don't worry!
 There's not much you need to do there.

From 9a8d4e2bd5fee7de6e1e1561b301a78df73c5fbe Mon Sep 17 00:00:00 2001
From: Justin W. Flory (he/him) <jwf@redhat.com>
Date: Oct 25 2023 15:20:54 +0000
Subject: [PATCH 2/2] docs(council): Incorporate edits from Operations Architect onboarding


This commit introduces changes discussed by @mattdm, @jflory7, and
@amoloney during the on-boarding hackfest for the Fedora Operations
Architect role. This reflects the final version of the role page and the
Council charter with the new role introduced.

Signed-off-by: Justin W. Flory (he/him) <jwf@redhat.com>

---

diff --git a/council/modules/ROOT/assets/images/amoloney.png b/council/modules/ROOT/assets/images/amoloney.png
new file mode 100644
index 0000000..9e3ba2f
Binary files /dev/null and b/council/modules/ROOT/assets/images/amoloney.png differ
diff --git a/council/modules/ROOT/pages/foa.adoc b/council/modules/ROOT/pages/foa.adoc
index 50bcb1b..e6281e3 100644
--- a/council/modules/ROOT/pages/foa.adoc
+++ b/council/modules/ROOT/pages/foa.adoc
@@ -1,6 +1,95 @@
-= Fedora Operations Architect =
+include::ROOT:partial$attributes.adoc[]
 
+= Fedora Operations Architect
+:page-aliases: fpgm.adoc
 
-This role replaces the previous xref:fpgm.adoc[Fedora Program Manager] position. 
+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.
 
-Full description to be developed.
+
+[[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)
diff --git a/council/modules/ROOT/pages/fpgm.adoc b/council/modules/ROOT/pages/fpgm.adoc
deleted file mode 100644
index ae8d71a..0000000
--- a/council/modules/ROOT/pages/fpgm.adoc
+++ /dev/null
@@ -1,73 +0,0 @@
-include::ROOT:partial$attributes.adoc[]
-
-= Fedora Program Manager
-
-The xref:program_management::index.adoc[_Fedora Program Manager_] (or _FPgM_) is the Chief Operating Officer of the Fedora Project.
-They are employed full-time by Red Hat to manage the planning and release processes for Fedora Linux.
-This includes schedule management, change wrangling, and providing status reports to the community and to Red Hat.
-
-
-[[current]]
-== Current Program Manager
-
-The role was eliminated in May 2023.
-
-
-[[roles]]
-== Roles and Responsibilities
-
-Within the Fedora Project, the Program Manager is primarily responsible for release coordination activities.
-
-[[roles-changes]]
-=== Changes Process
-
-* Shepharding Change proposals through the xref:program_management::changes_policy.adoc[Changes process]
-* Tracking the status of Changes during the development/testing cycle
-
-[[roles-releases]]
-=== Release Coordination
-
-* https://fedorapeople.org/groups/schedule/[Scheduling] xref:releases::index.adoc[Fedora Linux releases]
-* Coordinating release readiness (within QA, Release Engineering, FESCo, etc.)
-* Manage the Spins keepalive process
-* Perform mass updates of bugs at branch and end-of-life time
-
-[[roles-elections]]
-=== Elections
-
-* Managing xref:program_management::elections.adoc[elections] for {team_name}, FESCo, and Mindshare
-* Ad-hoc election support for other teams when needed
-
-[[roles-council]]
-=== {team_name}
-
-* Serve as a member of the {team_name}
-* Act as {team_name} secretary
-
-[[roles-misc]]
-=== Miscellaneous
-
-* Advise on the processes in the Fedora Project
-* Provide regular status reports to the community
-* Coordinate the xref:program_management::prioritized_bugs.adoc[Prioritized Bugs process]
-* Manage the processes for removing inactive packagers and inactive provenpackagers
-
-
-[[history]]
-== History
-
-Previous 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)
-
-
-[[links]]
-== Useful links
-
-* https://fedorapeople.org/groups/schedule[Schedules] in HTML, ICS, and JSON formats
-* https://pagure.io/fedora-pgm/schedule[Schedule repository] to report scheduling issues
-* xref:releases::lifecycle.adoc[Fedora Linux Release Life Cycle], A.K.A. how to schedule next Fedora release
diff --git a/council/modules/ROOT/pages/index.adoc b/council/modules/ROOT/pages/index.adoc
index 4bd216c..53d16f8 100644
--- a/council/modules/ROOT/pages/index.adoc
+++ b/council/modules/ROOT/pages/index.adoc
@@ -137,11 +137,10 @@ The Fedora community budget comes to us through the Red Hat Open Source Program 
 [[composition-appointed-foa]]
 ==== Fedora Operations Architect
 
-The Fedora Operations Architect (FOA) guides contributors proposing and implementing Fedora Linux changes and features and coordinates the planning and scheduling of our release cycle.
+The xref:foa.adoc[Fedora Operations Architect] (FOA) is employed full-time by Red Hat to assist the community in managing technical changes.
+This includes oversight of the Change process, schedule management, communications, and ownership of key strategic efforts.
 They also assist with the creation, improvement, maintenance, and execution of formal, repeatable Fedora processes.
-Additionally, the FOA serves as record-keeper and secretary for Fedora Council Meetings.
-
-This position is funded by and hired for by Red Hat, with the approval of the Council.
+Additionally, the Fedora Operations Architect serves as record-keeper and secretary for Fedora Council Meetings.
 
 
 [[coda]]

