No edit summary |
|||
Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
This page describes the process followed by the Marketing team to make a | This page describes the process followed by the Marketing team to make a talking points for a Fedora release. If you have suggestions on how to improve these instructions, please edit the page! | ||
== Steps == | == Steps == |
Revision as of 07:29, 15 February 2010
Introduction
This page describes the process followed by the Marketing team to make a talking points for a Fedora release. If you have suggestions on how to improve these instructions, please edit the page!
Steps
Create the Talking Points page
Using the prior talking points page as a template, create a new wiki page for the talking points of the current release, purging outdated content and updating it to reflect the working release's name and dates. The naming scheme is "F# talking points" where # is the number of the release (i.e. F12 talking points). Make sure the page is listed under,, and (where # is the number of the release). Create redirects to the "F# talking points" page from commonly mistyped pages and variants on capitalization, such as:
- F# Talking Points
- F# talking Points
- Fedora# Talking Points
- Fedora # Talking Points
- Fedora# talking points
=== Send out call for Talking Points
Prepopulate page with Talking Points
Categorize the Feature List into rough groups, based on which users will benefit from it: Desktop Users and Everyone, Administrators, Developers. Each of these will be a major header on the page (IE '= Desktop Users and Everyone =', '= Administrators =', '= Developers =') on the page. Include brief summary of that user group, taken from previous page Summarize each of the features in a single plain, short english sentence, and make that a section title under the user group which it fits into.