Guidelines for release names

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(New page: = Naming process = * Names are suggested by the community. ** The [http://redhat.com/archives/fedora-devel-list fedora-devel-list] mailing list was previously used for suggestions. ** Be...)
 
(Naming process)
Line 5: Line 5:
 
** Beginning with Fedora 11, name suggestions are solicited through a wiki page.
 
** Beginning with Fedora 11, name suggestions are solicited through a wiki page.
 
* To suggest a name, a community member ''must'':
 
* To suggest a name, a community member ''must'':
** Show how the name meets the "is-a" test.  For example, "Schnozz is a ____, and so is Keister."
+
** Show how the name meets the "is-a" test.  For example, "Schnozz is a ____, and so is Keister." Names for releases ''N'' and ''N+1'' must be related, and names for releases ''N'' and ''N+2'' cannot share the same relationship.
 
** Document preliminary searches showing the name is not encumbered by trademarks or other use that makes it a bad or risky choice.
 
** Document preliminary searches showing the name is not encumbered by trademarks or other use that makes it a bad or risky choice.
 
* Names are vetted through the Red Hat Legal department for a more intensive trademark search.
 
* Names are vetted through the Red Hat Legal department for a more intensive trademark search.

Revision as of 21:16, 14 July 2008

Naming process

  • Names are suggested by the community.
    • The fedora-devel-list mailing list was previously used for suggestions.
    • Beginning with Fedora 11, name suggestions are solicited through a wiki page.
  • To suggest a name, a community member must:
    • Show how the name meets the "is-a" test. For example, "Schnozz is a ____, and so is Keister." Names for releases N and N+1 must be related, and names for releases N and N+2 cannot share the same relationship.
    • Document preliminary searches showing the name is not encumbered by trademarks or other use that makes it a bad or risky choice.
  • Names are vetted through the Red Hat Legal department for a more intensive trademark search.
  • The Fedora Board is responsible for making sure the name ballot is of sufficient size and composition.
  • The final release name is decided through a community vote.
  • Problems are resolved through the Fedora Board and the FPL.