FOSS4G 2009 Press Release Process
Revision as of 15:08, 15 July 2009 by Wiki-Camerons (talk | contribs) (New page: == References == * Look back at FOSS4G_2009_Press_Releases for examples of prior press releases, translations and emails to community members. * For a list of community leaders, email ...)
References
- Look back at FOSS4G_2009_Press_Releases for examples of prior press releases, translations and emails to community members.
- For a list of community leaders, email lists, media publications and other marketing channels, use the password protected Google Doc: http://spreadsheets.google.com/ccc?key=pu9014gybzrd1M6FqyOzGWg&hl=en_GB . The FOSS4G 2009 conference chair (Cameron Shorter) and OSGeo Officer (Tyler Mitchel) have access to the list.
Two weeks before release date
For non major press releases, this can be completed in the week before the release.
- Write a draft press release, following the convensions at: FOSS4G_2009_Press_Releases.
- Include the words "___DRAFT___" at the top of the press release.
- Ensure you include Media Sponsors, in order to honour our Media Sponsor agreements.
- Ensure at least one other Committee Member reviews the press release, preferably more.
One week before release date
For major press releases:
- Create a "Translation" wiki page, with English version of the press release. See translation examples linked at: FOSS4G_2009_Press_Releases.
- Send an email to translators asking them to translate. See examples link from: FOSS4G_2009_Press_Releases. A list of translators is available in the "Translators" tab of the contact list referenced above.
One day before the release
- If the press release is referencing new web pages, then make sure these pages have been populated.
- Send a courtesy email to the press release recipients letting them know that a press release is coming