The Fedora Project has high standards, and our users expect that when something carries the Fedora name, it meets a certain bar for reliability, reproducibility, sanity, and elegance. At the same time, two of our basic values are "Features" and "First". Often, emerging features aren't yet reliable. Experimental designs might not be pretty. Messiness is very likely when we aim to integrate these new ideas first.
Historically, we've waited until things mature outside of the project before we include them — even ideas generated inside the Fedora community, or created with Fedora in mind. Shutting the door keeps Fedora's high standards intact — but at a cost. It takes significantly more work on everyone's part to integrate completely-external projects. And, these new concepts don't get valuable feedback from our community.
We need a way to include experimental, innovative ideas under the broad Fedora Project umbrella, while still preserving the quality implications of the Fedora brand.
Fedora Playground is a label for services, offerings, and subprojects which are officially part of the Fedora Project as a whole, but which we know are a rough around the edges. Unlike a Fedora Remix, something with the Fedora Playground label can use Fedora Project resources and — within the general trademark guidelines — the Fedora name.
All software include in a Fedora Playground subproject must be free and open source software, and must meet the same legal rules that apply to inclusion in the Fedora distribution.
What is this for?
The Fedora Playground brand can be applied to experimental combinations of Fedora software using new technologies. It could be Fedora software delivered in a new format — perhaps you've invented a new package manager — or with a default configuration very different from the general Fedora OS.
It can be used for Fedora adapted and built for a new class of hardware where not everything works yet and the user experience wouldn't be what we'd expect for an official Alternate Architecture.
It can also be used for applications or services which aren't ready to be official or up to the standards of Fedora Infrastructure.
What is this not for?
If you have an RPM package that's free / open source (and legal), but doesn't fit the packaging guidelines, use Copr.
If you have a combination of existing Fedora software without extensive customization, that's probably a Spin.
If you have a combination of Fedora software and non-Fedora software (possibly including non-free software), that could be a Fedora Remix.
If you have a project which doesn't align with the Fedora mission or the Fedora foundations, Fedora overall is probably not the right place for it.
File a ticket with the Fedora Council, at https://pagure.io/Fedora-Council/tickets/. As long as the project fits the rules above and fits within a broad conception of the Fedora Project mission, logo permission will be granted. Note, though, that requests for additional support and resources (hardware, hosting, people's time, or anything else) will have to clear a naturally higher bar. The best way to argue for this kind of support is to tie your Fedora Playground project to a Fedora Council Objective.
Do not use the Fedora Playground label or mark prior to Council approval. The Council reserves the right to remove this approval if it becomes necessary.
How can the Fedora Playground label and mark be used?
Currently approved Fedora Playground projects
None yet. Check back soon!