| |
@@ -1,16 +1,69 @@
|
| |
include::ROOT:partial$attributes.adoc[]
|
| |
|
| |
= Fedora Community Architect (FCA)
|
| |
+ :page-authors: {author}, {author_2}, {author_3}, {author_4}
|
| |
:page-aliases: fcaic.adoc
|
| |
+ :description: The Fedora Community Architect (FCA) is responsible for the stewardship of key community resources, including the Fedora budget, the Flock contributor conference, and Community Initiatives.
|
| |
+ Remy DeCausemaker; Brian Exelbierd; Marie Nordin; Justin Wheeler
|
| |
+ // Article content last reviewed and verified by a human onā¦
|
| |
+ 2025-07-07
|
| |
|
| |
- The _Fedora Community Architect_ (FCA) is employed full-time by Red Hat to lead initiatives that grow the Fedora user and developer communities.
|
| |
- They also help make Red Hat and Fedora interactions more transparent and open.
|
| |
- The Fedora community budget comes to us through the Red Hat Open Source Program Office (OSPO).
|
| |
- This position facilitates decision-making on how to best focus that to meet our community's goals and objectives.
|
| |
- The FCA supports the xref:fpl.adoc[Project Leader] with all things "community" and works directly with the Fedora Leadership to help bring more Heat and Light to the project.
|
| |
+ {description}
|
| |
+ This role is a permanent member of the Fedora Council, focused on the effective management and utilization of resources that enable community growth and governance.
|
| |
+ The FCA ensures the Fedora community has the necessary financial support, events, and community engagement to thrive.
|
| |
|
| |
- The FCA is appointed to the Community Architect seat on the xref:index.adoc[{team_name}], Fedoraās top-level community leadership and governance body.
|
| |
- The {team_name} is responsible for stewardship of the Fedora Project as a whole, and supports the health and growth of the Fedora community.
|
| |
+
|
| |
+ [[roles]]
|
| |
+ == Roles and Responsibilities
|
| |
+
|
| |
+ The Fedora Community Architect has the following key responsibilities:
|
| |
+
|
| |
+ [[roles-budget]]
|
| |
+ === Budget Management
|
| |
+
|
| |
+ * Serve as the permanent Chair of the Fedora Mindshare Committee, the primary body for reviewing and approving community funding proposals.
|
| |
+ * Analyze previous fiscal year spending and event impact to inform future budget strategy.
|
| |
+ * Lead the annual budget planning process, gathering requirements from the Fedora Council and community stakeholders.
|
| |
+ * Develop the annual budget proposal, creating forecasts based on strategic priorities and anticipated event costs.
|
| |
+ * Negotiate the final budget with OSPO leadership, aligning community needs with corporate financial realities.
|
| |
+ * Oversee the public processes for event funding requests and other community initiatives throughout the year.
|
| |
+ * Maintain accurate accounting of all expenditures, providing regular financial reports to both the Fedora community and OSPO.
|
| |
+
|
| |
+ [[roles-flock]]
|
| |
+ === Flock Contributor Conference
|
| |
+
|
| |
+ * Analyze post-event feedback and survey data to set strategic goals for the next conference.
|
| |
+ * Lead the venue selection and negotiation process based on community needs and logistical requirements.
|
| |
+ * Assemble and lead the Flock organizing committee, defining clear roles and responsibilities.
|
| |
+ * Serve as the overall project manager for the conference, ensuring all functions remain synchronized and on schedule.
|
| |
+ * Curate a conference program that addresses key project challenges, showcases innovation, and creates a welcoming environment for all contributors.
|
| |
+
|
| |
+ [[roles-initiatives]]
|
| |
+ === Community Initiative Support
|
| |
+
|
| |
+ * Serve as an executive sponsor for selected Community Initiatives, providing guidance and support to community leaders to ensure successful adoption and implementation.
|
| |
+ * Facilitate onboarding of Community Initiatives to the Fedora Council.
|
| |
+ * Maintain documentation related to Fedora Council governance, policies, and procedures.
|
| |
+ * Coordinate the creation and revision of Council documents, working with Council members to ensure accuracy and clarity.
|
| |
+ * Coordinate the publication and communication of Council documentation to the Fedora community.
|
| |
+
|
| |
+ [[roles-commops]]
|
| |
+ === Collaboration with Community Ops
|
| |
+
|
| |
+ * Serve as the primary leader and advocate for the xref:commops::index.adoc[Fedora Community Ops Team].
|
| |
+ * Set the strategic direction for Community Ops to ensure its work in community enablement and analytics aligns with broader project goals.
|
| |
+ * Act as a primary advisor for Fedora teams seeking support from CommOps, connecting them with the appropriate resources.
|
| |
+ * Provide ethical and community-centric guidance for all Community Ops data analysis initiatives.
|
| |
+ * Facilitate trusted Community Ops members' access to the data, tooling, and resources required to support the health of the community.
|
| |
+
|
| |
+ [[roles-coc]]
|
| |
+ === Fedora Code of Conduct Committee Chair
|
| |
+
|
| |
+ * Uphold and champion the psychological safety of the Fedora community.
|
| |
+ * Facilitate the xref:project:code-of-conduct:committee.adoc[Code of Conduct Committee]'s operations and regular meetings.
|
| |
+ * Present new cases to the Committee and act as the primary liaison between the Committee and the reporting party.
|
| |
+ * Coordinate the publication of official Committee responses and annual transparency reports.
|
| |
+ * Maintain the Committee's charter, membership records, and official documentation.
|
| |
|
| |
|
| |
[[current]]
|
| |
@@ -27,67 +80,61 @@
|
| |
You can read more about his participation and history in Fedora https://jwheel.org/#fedora[on Justin's website].
|
| |
|
| |
|
| |
- [[roles]]
|
| |
- == Roles and Responsibilities ==
|
| |
-
|
| |
- [[roles-council]]
|
| |
- === {team_name} ===
|
| |
-
|
| |
- * Work with other {team_name} members to identify the short, medium, and long term goals of the Fedora community and to organize and enable the project to best achieve them
|
| |
- * Primary {team_name} member with responsibility for the development of the annual Fedora community budget
|
| |
- * Participate in decision-making about use of trademarks, project structure, community disputes or complaints, and other such issues
|
| |
+ [[decision-making]]
|
| |
+ == Decision-Making
|
| |
|
| |
- [[roles-special]]
|
| |
- === Special Initiatives ===
|
| |
+ The Fedora Community Architect (FCA) is a Red Hat employee, and this context is a primary factor in their role.
|
| |
+ The FCA has professional goals and responsibilities within Red Hat's Open Source Program Office (OSPO).
|
| |
+ This sponsorship by Red Hat is a bias the FCA must remain aware of and transparent about.
|
| |
|
| |
- * Design and spearhead special initiatives to grow user and contributor bases
|
| |
+ However, the FCA's primary objective is to ensure the long-term health and success of the Fedora Project and its global community.
|
| |
+ This requires acting as a bridge between Red Hat's interests and the broader community's needs, advocating for the community's perspective within Red Hat while communicating Red Hat's context back to the community.
|
| |
|
| |
- [[roles-metrics]]
|
| |
- === Metrics ===
|
| |
+ Decisions are made through the following collaborative processes:
|
| |
|
| |
- * Implement metrics for community engagement, participation, and satisfaction; create and execute projects to improve those metrics; report regularly on progress and adjust approach as needed
|
| |
+ * Decisions related to budget allocation and official project documentation are made with the xref:council::index.adoc[{team_name}].
|
| |
+ * Decisions related to Flock planning are made in collaboration with the Flock organizing team and relevant community stakeholders.
|
| |
|
| |
- [[roles-opportunities]]
|
| |
- === Opportunities ===
|
| |
+ [[guiding-principles]]
|
| |
+ === Guiding Principles
|
| |
|
| |
- * Identify opportunities to engage new contributors and community members; align project around supporting those opportunities
|
| |
+ The FCA's core responsibilities provide a framework for day-to-day decisions.
|
| |
+ However, situations will arise where these responsibilities conflict, or where the best path forward is unclear.
|
| |
+ In these moments, the FCA must navigate the complexity by relying on a deeper set of principles.
|
| |
|
| |
- [[roles-community-liaison]]
|
| |
- === Liaise between Red Hat and FOSS Community ===
|
| |
+ This is a role of significant influence and trust within the community.
|
| |
+ That influence should be used intentionally and with care.
|
| |
+ The FCA has a fundamental responsibility to the community of contributors and the long-term health of the Fedora Project.
|
| |
+ When faced with a difficult choice, the FCA should use Fedora's xref:project::index.adoc#_what_is_fedora_all_about[Four Foundations] (Freedom, Friends, Features, and First) as the primary framework for their reasoning.
|
| |
+ These are the core values of the project and should consistently inform the FCA's judgment.
|
| |
|
| |
- * Communicate community needs to Red Hat and participate in regular meetings with internal Red Hat stakeholders; align Red Hat participation in Fedora beyond platform engineering
|
| |
- * Represent Red Hatās stake in Fedora community success
|
| |
- * Improve on-boarding materials and presentation of Fedora to new Red Hat hires; develop standardized materials on Fedora which can be used at Red Hat globally.
|
| |
|
| |
- [[roles-budget]]
|
| |
- === Budget ===
|
| |
+ [[communication]]
|
| |
+ == Communication
|
| |
|
| |
- The Fedora Community Architect works with the {team_name} and Red Hat Open Source Program Office (OSPO) to determine the annual Fedora Budget.
|
| |
+ The Fedora Community Architect (FCA) acts as a central communication hub for the project.
|
| |
+ The FCA is responsible for maintaining strong lines of communication with key stakeholder groups and the community at large.
|
| |
|
| |
- * Ensure that budget is published and tracked transparently, with a public page indicating how each yearās budget is earmarked and its current state.
|
| |
+ *Serve as a liaison to key stakeholder teams:*
|
| |
|
| |
- [[roles-events]]
|
| |
- === Fedora Event Planning and Participation ===
|
| |
+ * *Fedora Council*:
|
| |
+ 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.
|
| |
|
| |
- Participate in planning and organizing Fedoraās Flagship events each year, including:
|
| |
+ *Communicate regularly and transparently with the broader community:*
|
| |
|
| |
- * Flock, Nest, & Hatch
|
| |
- * Release Parties
|
| |
- * Fedora contributor hackfests
|
| |
-
|
| |
- The Fedora Community Architect also represents Fedora at other major industry conferences and hackathons such as:
|
| |
-
|
| |
- * All Things Open
|
| |
- * DevConf CZ, IN, US
|
| |
- * FOSDEM
|
| |
- * PyCon (and Sprints)
|
| |
- * LibrePlanet
|
| |
- * Red Hat Summit
|
| |
-
|
| |
- [[roles-communications]]
|
| |
- === Communications ===
|
| |
-
|
| |
- The Fedora Community Architect provides and facilitates regular communications to Fedora Magazine, the Fedora Community Blog, and other mass communication channels to talk about community goals/progress and general community boosting.
|
| |
+ * Proactively share updates and progress related to the five core responsibilities of the role.
|
| |
+ * 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.
|
| |
|
| |
|
| |
[[previous]]
|
| |
@@ -103,7 +150,7 @@
|
| |
February 2015 ā June 2016 (_Fedora Linux 22 to 24_)
|
| |
|
| |
[[previous-titles]]
|
| |
- === What about FCAIC and FCL?
|
| |
+ === Why so many titles?
|
| |
|
| |
The title of this role evolved and changed over the years since its inception in February 2015.
|
| |
The creation of the role was largely envisioned and advocated for by xref:fpl.adoc#previous[Robyn Bergeron], then the Fedora Project Leader.
|
| |
@@ -117,12 +164,9 @@
|
| |
This title was lengthier but better captured what community engagement means in a large, globally-distributed community like Fedora.
|
| |
Over time, more projects, organizations, and companies working on Free & Open Source Software (FOSS) introduced new roles in community management and leadership.
|
| |
However, community work does not have an industry-accepted job ladder, as is more common with software engineering.
|
| |
- Red Hat eventually settled on the title of _community architect_ for community work in its pioneering Open Source communities.
|
| |
-
|
| |
- Fast forward to 2023.
|
| |
- The landscape has changed and evolved!
|
| |
- So, it was the ideal time to reflect on the title for this role.
|
| |
- The title was changed in January 2023 to *Fedora Community Architect* (FCA).
|
| |
- Ultimately, the goal of changing the name was to better describe the role and what the FCA does in Fedora.
|
| |
- The lengthy "FCAIC" title usually came with an explanation to others unfamiliar with Fedora and our community culture.
|
| |
- FCA is also a handy shortening of the longer FCAIC acronym too!
|
| |
+ Red Hat eventually settled on the title of _community architect_ for a career path in community management in its pioneering Open Source communities.
|
| |
+
|
| |
+ The title was changed in January 2023 to *Fedora Community Architect* (FCA) to reflect the changing landscape.
|
| |
+ Ultimately, the goal of changing the name then was to better describe the role and what the FCA did in Fedora.
|
| |
+ The lengthy "FCAIC" title often came with an explanation to others unfamiliar with Fedora and our unique community culture.
|
| |
+ FCA was also a handy shortening of the longer FCAIC acronym too!
|
| |
jflory7
commented 7 months ago
This commit is a complete rewrite of the Fedora Community Architect (FCA) charter page to better reflect core responsibilities. The Community Architect role was often misinterpreted as a broad "Community Manager" role, while the actual focus is on the stewardship of key project resources: the Fedora budget, the Flock contributor conference, and Fedora Council documentation. This change clarifies the role's priorities and aligns it with performance expectations.
The core motivation was to move beyond abstract statements and define the specific actions, accountabilities, and guiding principles of the FCA. This was achieved by systematically expanding each section to reflect the practical, day-to-day realities of the work.
Key changes include: