FOSS4G 2009 Press Release Process

Overview
We divide our press releases into major, and minor. Minor press releases are sent out to a specific interested community, (like the OSGeo discuss list, and our chair's blog.

Major press releases are aimed to go as far as we can possibly get them. We limit the number of major press releases we put out in order to ensure we don't wear out the people involved in sending them, and ensure that the message is fresh and hence read by less interested recipients.

For FOSS4G major press releases, we send emails to community leaders, and ask them to forward onto their respective email lists, along with a personal recommendation from the community leader. Emails received from people you know are much more likely to be read and acted upon.

Two weeks before release date
For non major press releases, this can be completed in the week before the release.
 * 1) Write a draft press release, following the convensions at: FOSS4G_2009_Press_Releases.
 * 2) Include the words "___DRAFT___" at the top of the press release.
 * 3) Ensure you include Media Sponsors, in order to honour our Media Sponsor agreements.
 * 4) Ensure at least one other Committee Member reviews the press release, preferably more.

One week before release date
For major press releases:
 * 1) Create a "Translation" wiki page, with English version of the press release. See translation examples linked at: FOSS4G_2009_Press_Releases.
 * 2) 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

 * 1) If the press release is referencing new web pages, then make sure these pages have been populated.
 * 2) Send a courtesy email to the press release recipients letting them know that a press release is coming

Release date

 * 1) Send out a cover email, plus the press release to each of the groups of community leaders listed in the Google Docs Contacts sheet mentioned above: Projects, Lists, Media, Regional Lists, Local Chapters. (See FOSS4G_2009_Press_Releases for links to example Cover Email letters from other press releases)
 * 2) Let each recipient know what list they are responsible for emailing. This can be done by copying a table of who is chasing what.
 * 3) BCC all recipients
 * 4) CC the conference organisor (Cameron Shorter)
 * 5) CC anyone who may be chasing down leaders to forward on press releases
 * 6) For Web Entry media releases, like SlashGeo, add the press release directly into the web page, as per "Web Submissions" form on the Contacts list.
 * 7) Send out a Twitter message. (Todo, ask Shoaib how to do this)

Day or 2 after release

 * 1) Check each email list to see if the press release was forwarded on by the community leader. Chase the leader if he/she have not sent it with a friendly email. If that doesn't work, in the following day try to find an alternative leader, or send the email yourself. (Someone like Tyler is subscribed to most lists, and could be used to forward on most emails).