Feature profiles SOP

This page is a work in progress.
It is an incomplete draft that we are working on - if you can think of ways to make it better, please edit the page and improve it!

Introduction

This is a Marketing SOP that describes how to create Feature profiles.

Examples

You can see examples of past feature profiles at Category:Feature profiles.

Create the feature profiles page for the current release

1. Create a page named F(number) feature profiles where (number) is the number of the release under development. For instance, F13 feature profiles.
2. Add some text in the page explaining what feature profiles are. The template for a #Feature profiles page may be helpful.
3. Categorize the page properly - in Category:Feature profiles, in Category:Marketing, and in Category:F(number) where (number) is the number of the current release (for instance, Category:F12).

Select the feature profiles

Add a section to the feature profiles page you just created for keeping track of feature profiles. You can use the #Feature profiles table template to help you.

Select 3-5 features to profile and add them to the table. This is best done in a Marketing meeting with collaboration from the FPL.

Selection criteria:

1. Total amount of engineering effort required to complete the feature (higher is better - we want to celebrate the work engineers are doing!) Bonus points for being driven by Fedora people working in upstreams, OR (if not upstream-drivable - if it's a Fedora-specific thing) run by a contributor/volunteer (someone who's not paid to do what they did, whether or not they're a Red Hat employee).
2. How many of the 4 foundations does this hit? (More is better, of course.)
3. Do we want people to use this feature en masse because it would be helpful to the project, and would they be less likely to find out about it otherwise?

Templates

Feature profiles page

This page is the home of the Feature profiles for the F(number) release. For more information on what feature profiles are or how this deliverable was created, see the Feature profiles SOP.

For each feature, the marketing owner should do several things:

1. Create a wiki page that can be the home of the work that you do.
2. Conduct an interview with the primary developer(s). Written, podcast, or both. There is a page on how to make a podcast for those that are interested.
3. Make sure that the feature is reflected on the talking points for that release.
4. Prepare a tutorial or screenshot tour of the feature.

If you have any questions about these, or need any help, please do not be shy about asking on fedora-marketing-list! You can also reference the prior feature profiles pages to see examples of previous feature profiles.

Feature profiles table

Feature	Owner	Reference page	Notes

Improve this SOP!

If you see a way to improve this SOP, please go ahead and edit the page - you don't need to ask for anyone's permission. Read more about our contribution philosophy here.