Introduction
This is a draft schedule for the marketing team to follow in the build up to the Fedora 11 release. Included is a description of the tasks and the steps required to complete them, as well as a preliminary schedule to help guide our priorities as the release approaches.
Schedule
These are just task titles; descriptions of the tasks can be found further down the page.
| Completion Date | Task Title |
|---|---|
| 2009-03-03 | Lay press contacts list |
| Guide to translating Fedora software | |
| Guide to testing Fedora releases | |
| 2009-04-21 | Feature Summary |
| Features for general art sites | |
| Features for system-administrator sites & magazines | |
| Release note contributors | |
| Fedora Forum | |
| 2009-04-28 | Release & countdown banners |
| 2009-05-19 | Release announcement |
Task Descriptions
Lay press contacts list
While Red Hat's internal marketing teams will handle communication with the larger press outlets as well as arranging interviews with the FPL, the marketing team will work with smaller press outlets, bloggers and podcasters to help drive interest and increase knowledge about Fedora in these areas. To achieve this we will need to:
- Create a list of contacts
- Get in touch with contacts and
- Advise them of the feature list (feature summary when ready)
- Arrange interviews with developers, project members
Guide to translating Fedora software
One of the primary tasks of the marketing team is to help increase participation in all areas of the project, gathering new contributors from all around the world. As a result, we should work with other areas of the project to provide material that will help get new contributors started, including the translation team. To achieve this we will need to:
- Contact glezos about producing a guide to using Transifex
- Produce and edit the guide, perhaps working with the docs project
- Publish the guide in a suitable location
As an aside, it might be nice to provide regular updates of translation statistics to help motivate people to keep going or to get involved. When ever we publish these statistics, we should point back to the guide.
Guide to testing Fedora releases
Lots of QA needs to be done to ensure the final release is as good as possible. Providing material that explains how to test Fedora development releases, and critically, how to report bugs against it will hopefully enable more people to take part in testing. To achieve this we will need to:
- Talk to jlaska about re-purposing and expanding his series of tutorials for this
- Produce and edit the guide, perhaps working with the docs project
- Publish the guide in a suitable location
As an aside, it might be nice to provide regular updates about the number of open bugs reported against Rawhide.