Fedora Community Action and Impact Coordinator
The Fedora Community Action and Impact Coordinator (or FCAIC) is a full-time, Red Hat-employed job to lead initiatives to grow the Fedora user and developer communities, and to make Red Hat & Fedora interactions more transparent and positive. 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 FCAIC supports the Project Leader with all things "Community" and works directly with the Fedora Leadership to help bring more Heat and Light to the project.
The FCAIC is appointed to the Community Action and Impact seat on the Fedora Council, Fedora’s top-level community leadership and governance body. The Council is responsible for stewardship of the Fedora Project as a whole, and supports the health and growth of the Fedora Community.
Current F-🎂[1]

Justin W. Flory (pronouns: he/him) became the FCAIC in October 2022.
Justin is a creative maker. He is best known as an Open Source contributor and Free Culture advocate originally from the United States.
Justin has participated in numerous Open Source communities and led different initiatives to build sustainable software and communities for nearly ten years. This includes his participation in the Fedora Project since 2015. In Fedora, he co-founded and led the Community Operations team for four years and was a founding member of the Diversity, Equity, & Inclusion Team. You can read more about Justin’s past and present Fedora activities on his website.
Previous to Red Hat, from June 2020 to September 2022, Justin supported the UNICEF Office of Innovation as the first Open Source Technical Advisor. At UNICEF, he supported the UNICEF Venture Fund and other Open Source activities within the Office of Innovation. Together with a team of mentors, Justin mentored twenty-three start-up companies of diverse start-up companies from nineteen countries and five continents.
Roles and Responsibilities
Council
-
Work with other Council 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 Council 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
Metrics
-
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
Opportunities
-
Identify opportunities to engage new contributors and community members; align project around supporting those opportunities
Liaise between Red Hat and FOSS Community
-
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.
Budget
The FCAIC will work with Fedora Council and OSAS to determine annual Fedora Budget
-
Ensure that budget is published and tracked transparently, with a public page indicating how each year’s budget is earmarked and its current state.
Fedora Event Planning and Participation
Participate in planning and organizing Fedora’s Flagship events each year, including:
-
Flock, Nest, & Hatch
-
Release Parties
-
Fedora contributor hackfests
The FCAIC 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
Previous Fedora Community Action and Impact Coordinators
- Marie Nordin
-
November 2019 – October 2022
- Brian Exelbierd
-
October 2016 – November 2019
- Remy DeCausemaker
-
February 2015 – June 2016
Want to help? Learn how to contribute to Fedora Docs ›