English Chinese (Simplified) (zh_CN)
Process for promoting a Fedora deliverable to Edition
Fedora Editions are curated sets of packages, guidelines and configuration, and artifacts built from those pieces, that address a specific, targeted use-case. The Editions are the primary Fedora outputs that most Fedora users are encouraged to use and directed towards through the download site.
This document describes the process for promoting an existing Fedora deliverable to Edition status.
What makes an "Edition"?
A Fedora Edition:
addresses a distinct, relevant, and broad use-case or userbase that a Fedora Edition is not currently serving;
is a long term investment for the Fedora Project; and
is consistent with all of Fedora's foundations.
The candidate Edition must be backed by a team that holds regular public meetings
The candidate Edition must get trademark approval from the Fedora Council. If this includes a name change or a new name (e.g. “Fedora Bilverslue”), plan time for legal review.
The candidate Edition must have a product requirements document (PRD) (https://fedoraproject.org/wiki/Workstation/Workstation_PRD[example]). The PRD is used by other teams within Fedora (for example: the QA team uses it to develop release criteria and test cases, the marketing team uses it to develop collateral and positioning). The PRD must include:
Market target, including key use cases and personas
Core services and features
Core applications
Unique policies for installation, updates, etc
Scope of hardware support (including anything that is explicitly unsupported)
Produced deliverables, and whether or not they should be considered release blocking
The candidate Edition may have a technical specification (https://fedoraproject.org/wiki/Workstation/Technical_Specification[example]) that provides additional detail about the specific features described in the PRD.
It is helpful to have someone on the team assigned to handle the bureaucratic tasks