From 27d5fb67f6ea1b63da060c0680c525d130f4bbcc Mon Sep 17 00:00:00 2001
From: Ben Cotton <bcotton@fedoraproject.org>
Date: Dec 20 2022 14:56:39 +0000
Subject: Add detail to FPgM page


---

diff --git a/council/modules/ROOT/pages/fpgm.adoc b/council/modules/ROOT/pages/fpgm.adoc
index ad21592..f0684e4 100644
--- a/council/modules/ROOT/pages/fpgm.adoc
+++ b/council/modules/ROOT/pages/fpgm.adoc
@@ -1,27 +1,61 @@
 = Fedora Program Manager
 
-The _Fedora Program Manager_ (or _FPgM_) is responsible for managing the planning and release processes for Fedora.
+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.
 
-image::bcotton-rh_neo.jpeg[float="right",50%]
-https://fedoraproject.org/wiki/User:Bcotton[Ben Cotton] is the current FPgM.
+[[current]]
+== Current Program Manager
+
+[.profile-picture]
+image::bcotton-rh_neo.jpeg[float="right"]
+
+https://fedoraproject.org/wiki/User:Bcotton[Ben Cotton] (pronouns: he/him) became the Fedora Program Manager in June 2018.
 He joined Red Hat after a decade in high performance computing (HPC) administration and marketing.
 Ben first started contributing to Fedora in 2009 as a member—and later leader—of the Fedora Docs team.
 He is an Open Organization Ambassador, and was formerly a Correspondent for Opensource.com.
+He is the author of https://pragprog.com/titles/bcosp/[_Program Management for Open Source Projects_].
 
-Contact Ben on Libera.Chat IRC (`bcotton`) or by email (`bcotton@fedoraproject.org`).
+Contact Ben by email (`bcotton@fedoraproject.org`).
 
+[[roles]]
 == Roles and Responsibilities ==
 
-Within the Fedora Project, the Program Manager (FPGM) is primarily responsible for:
+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 Council, FESCo, and Mindshare
+* Ad-hoc election support for other teams when needed
+
+[[roles-council]]
+=== Council ===
+
+* Serve as a member of the Fedora Council
+* Act as Council secretary
 
-* planning and https://fedorapeople.org/groups/schedule/[scheduling] of xref:releases::index.adoc[Fedora Linux releases]
-* tracking the changes/features during the development/testing cycle
-* release coordination (within QA, releng, FESCo, etc.)
-* managing xref:program_management::elections.adoc[elections]
-* processes behind Fedora Project
-* serving as a member of Fedora Council—Auxiliary Seat, Council 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 ==