council/docs
council/docs
13
1
Fork 5
Code Issues 5 Pull requests 1 Projects Activity Actions

📝 council(ROOT): Align key stakeholders list with actual FCA duties

Browse source 
The "Communication" section's stakeholder liaison list and its
responsibility count both drifted out of sync with the "Roles and
Responsibilities" restructuring done earlier in this rewrite. This
commit brings both back into alignment.

"Proactively share updates and progress related to the five core
responsibilities of the role" was a leftover from the old five-section
structure (Budget, Flock, Community Initiative Support, Community Ops,
Code of Conduct). That structure is now four sections (Governance,
Budget, Flock, CentOS), so the hardcoded count was wrong. Rather than
update it to "four" and risk the same drift the next time this section
changes, the count is dropped in favor of "the FCA's core
responsibilities."

The stakeholder list itself claimed the FCA serves as a liaison to the
DEI Team, the CommOps Team, Mentored Projects, and the Docs Team. None
of those relationships are a formal, dedicated part of the role as
defined elsewhere on this page, however. The FCA may support any of
these teams informally through the responsibilities that are actually
assigned to the role, but listing them as key stakeholder relationships
overstated the FCA's mandate. All four entries are removed.

In their place, the list now names the Code of Conduct Committee, the
Flock Organizing Team, the CentOS Board, and the CentOS Connect
Organizing Team. Each of these traces directly to an explicit duty
already stated in Roles and Responsibilities: the Code of Conduct
Committee and CentOS Board relationships come from the "Fedora Council
and Governance" and "CentOS Ecosystem Stewardship" sections, and the two
organizing-team entries reflect the FCA's conference-management duties
for Flock and CentOS Connect. The result is a stakeholder list that
reads as a direct index of the role's actual responsibilities, rather
than a broader list of teams the FCA happens to interact with.

Assisted-by: Claude Sonnet 5 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
This commit is contained in:
Justin Wheeler 2026-07-05 04:59:41 -04:00
commit b7f97cea6e
Signed by: jflory7
GPG key ID: 7748B15FA8FA4C7E
1 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

18
council/modules/ROOT/pages/fca.adoc
View file

@ -115,18 +115,18 @@ The FCA is responsible for maintaining strong lines of communication with key st
Report on the status of key responsibilities and provide context for community needs.
* *Mindshare Committee*:
Lead budget discussions and guide outreach strategy.
* *DEI Team*:
Champion diversity and inclusion initiatives and integrate DEI principles into community-wide planning.
* *CommOps Team*:
Guide strategic direction and enable the team's work in community support and analytics.
* *Mentored Projects*:
Promote internship programs and support both mentors and interns.
* *Docs Team*:
Advocate for the team's needs and facilitate documentation onboarding for new initiatives.
* *Code of Conduct Committee*:
Coordinate committee meetings, ensure timely follow-up on submitted cases, and maintain committee documentation.
* *Flock Organizing Team*:
Coordinate conference logistics and programming for Flock.
* *CentOS Board*:
Represent Fedora's interests in CentOS governance, elections, and community transitions.
* *CentOS Connect Organizing Team*:
Coordinate conference logistics and programming for CentOS Connect.
*Communicate regularly and transparently with the broader community:*
* Proactively share updates and progress related to the five core responsibilities of the role.
* Proactively share updates and progress related to the FCA's core responsibilities.
* Utilize various channels, including the Fedora Community Blog, Fedora Discussion, and Matrix, to reach different audiences.
* Create structured opportunities for community participation and feedback on relevant topics.