include::ROOT:partial$attributes.adoc[]

= Guiding Policy

This guiding policy represents the way the {team_name} would like the Project to make its mission a reality.

The Fedora Project's https://docs.fedoraproject.org/en-US/project/#_our_mission[Vision] is:

____
_The Fedora Project envisions a world where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities_.
____

To accomplish this, our https://docs.fedoraproject.org/en-US/project/#_our_mission[Mission] is:

____
_Fedora creates an innovative platform for hardware, clouds, and containers that enables software developers and community members to build tailored solutions for their users_.
____

We do this within the context of the Four Foundations: Freedom, Friends, Features, and First.


[[context]]
== Context

The {team_name} identifies the short-, medium-, and long-term goals necessary to keep the Project on the leading edge of technology.
The Fedora.next initiative focused the outputs of the project around use cases.
In 2017, we updated the mission statement to reflect changes in the computing landscape.
Today, it is too difficult to build new solutions in Fedora.


[[approach]]
== Our Approach

We will make it easy for the community to build solutions, address specific developer problems, and meet their end users’ specific needs.
We will do this by encouraging and helping Objectives which make the necessary changes required to ease the process.
This accelerates the transformation of Fedora into a community that enables the construction of solutions. 

Internally, Fedora focuses on enabling these solutions to be built.
The outputs of Fedora are the Solutions our community members build.
Our focus on enablement allows experimentation without prior judgement or gate-keeping.


[[meaning]]
== What does this mean?

Teams such as Design, Documentation, Packagers, Release Engineering, and Quality Assurance provide building blocks and offer services to other community members and Teams.
Services and building blocks include the following:

* CI infrastructure
* Community building advice and guidance
* Event funding
* Logo services
* RPM or other software packages
* Swag
* Testing and validation
* User support
* UX design

Anyone may use building blocks like software packages and artwork to create a Solution.
Example solutions include: Fedora Workstation, KDE Plasma, and the Python Classroom Lab.
Teams define criteria for services they provide to solution-builders.
For example, teams providing press and promotional support may choose to provide additional support to Solutions with larger user bases.

Teams are free to define elements of their Solutions, such as intent, deliverables, and release cadence.
Teams can build Solutions from any building block and pick and choose what tools they use.
Based on their choices, they get different levels of ability to use the Fedora trademark (i.e. “Fedora Remix” vs “Powered by” vs “Fedora”).
Some solutions are the premier showcases that we call Editions; these are used in the gating tests for our releases.
