Release announcements

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Process)
 
(2 intermediate revisions by one user not shown)
Line 16: Line 16:
 
#* Any Fedora contributor who reads the language is an eligible editor.
 
#* Any Fedora contributor who reads the language is an eligible editor.
 
# Formal announcements are sent out to fedora-announce, fedora-list (either the main list or a language-specific one), via blogs, and into various support channels (#fedora, fedoraforum.org, fedoraunity.org et al, etc.), either international or local ones.
 
# Formal announcements are sent out to fedora-announce, fedora-list (either the main list or a language-specific one), via blogs, and into various support channels (#fedora, fedoraforum.org, fedoraunity.org et al, etc.), either international or local ones.
 +
 +
This process section may be moved to [https://fedoraproject.org/wiki/Final_announcement_SOP the SOP.]
  
 
== Talking points ==
 
== Talking points ==
  
{{admon/note|Use [[{{FedoraVersion|short|next}} Talking Points]] for {{FedoraVersion|long|next}}.}}
+
{{admon/note|Use [[{{FedoraVersion|short|next}} talking points]] for {{FedoraVersion|long|next}}.}}
  
 
A ''talking point'' is a term meaning, "These are the topics the group wants to address, in the same way, with the same message, for all audiences."  Having a common set of talking points helps keep a common message about the Fedora release.  The talking points cover technology, features, exciting news, and participation/contribution invitations.
 
A ''talking point'' is a term meaning, "These are the topics the group wants to address, in the same way, with the same message, for all audiences."  Having a common set of talking points helps keep a common message about the Fedora release.  The talking points cover technology, features, exciting news, and participation/contribution invitations.
Line 51: Line 53:
 
These give you an idea of how they have been written in the past.
 
These give you an idea of how they have been written in the past.
  
 +
* [http://lists.fedoraproject.org/pipermail/announce/2009-November/002725.html F-12]
 +
* [http://lists.fedoraproject.org/pipermail/announce/2009-June/002662.html F-11]
 
* [http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00015.html F-10]
 
* [http://www.redhat.com/archives/fedora-announce-list/2008-November/msg00015.html F-10]
 
* [http://www.redhat.com/archives/fedora-announce-list/2008-May/msg00007.html F-9]
 
* [http://www.redhat.com/archives/fedora-announce-list/2008-May/msg00007.html F-9]

Latest revision as of 22:39, 14 October 2010

An important part of a Fedora release is its announcement. The release team composes a release announcement sent on the day of the release. These announcements are typically whimsical, meaning they take a fun approach rather than a typically serious press release approach.

Each local team is encouraged to write its own announcement in a way that makes the most sense for the local community. This is a truly localized version of the release announcement for Fedora.

For Fedora 21, use F21 talking points. Read #Talking points for more about how that works.

Contents

[edit] Process

  1. A small committee of Fedora writers, marketeers, and technical leaders draft and approve a final list of release talking points.
  2. A Release announcement template is produced using structured text in plain ASCII. It includes a block at the top for the local content, then a complete amount of standard boilerplate.
    • To use the template, copy the content from the Release announcement template page and paste in to a plain text editor so it removes all formatting from the HTML/wiki.
  3. Any local group wanting to write a native-language Fedora release announcement needs to form a group of 2 or more collaborators.
  4. Drafts can be worked on here on the Wiki, via direct email, or whatever method the collaborators choose.
  5. The draft must be reviewed and approved by an independent reader of that language.
    • This needs to be someone from outside of the collaboration circle that wrote the draft
    • Any Fedora contributor who reads the language is an eligible editor.
  6. Formal announcements are sent out to fedora-announce, fedora-list (either the main list or a language-specific one), via blogs, and into various support channels (#fedora, fedoraforum.org, fedoraunity.org et al, etc.), either international or local ones.

This process section may be moved to the SOP.

[edit] Talking points

Note.png
Use F21 talking points for Fedora 21.

A talking point is a term meaning, "These are the topics the group wants to address, in the same way, with the same message, for all audiences." Having a common set of talking points helps keep a common message about the Fedora release. The talking points cover technology, features, exciting news, and participation/contribution invitations.

You do not need to use all of the talking points in an announcement or presentation, but at least some of them should be covered. If you substitute others, be sure that you have a good reason for not using the common talking points. An example would be if a technology or feature is particularly useful in your region.

[edit] How to use the talking points

  • Use at least some of the content
  • If you list all of the talking points, you can reduce the words to just a sentence per point
  • You can make the talking points part of the narrative of your whimsical announcement

[edit] Where to send your announcement

These release announcements are for use in your local region. No one in Fedora is gathering these to send out. The best resource is to work with your local Ambassador team(s), who know where to send announcements regionally.

Ideas include:

  • News media outlets (websites, newspapers, etc.)
  • Technical journalists
  • Technical and free/open bloggers
  • Educational organizations (IEEE, etc.)
  • User groups (LUGs, JUGs, etc.)

[edit] F21 Announcements Schedule

The Marketing and Documentation teams keep tasks on their respective release schedules for the release announcement. The respective team leads and both teams' members should be coordinating and communicating regularly as they move toward the release date.

[edit] Past Release Announcements

These give you an idea of how they have been written in the past.

(And now you know why we don't let Bill write them anymore!)