Difference between revisions of "Press Release Process"

From OSGeo
Jump to navigation Jump to search
 
(16 intermediate revisions by 7 users not shown)
Line 1: Line 1:
== Press Release Process - Draft ==
 
 
 
The goal is to have a simple and understandable process for creating, reviewing and issuing press releases.
 
The goal is to have a simple and understandable process for creating, reviewing and issuing press releases.
  
Once initiated, the process will be driven by a member of the Visibility Committee.  There are five basic steps:
+
Once initiated, the process will be driven by a member of the Visibility Committee.  The basic steps are:
  
=== 1) Conception ===  
+
== Conception ==
 
Something newsworthy happens - a new software release of an OSGeo project, for example.  The "owner" of said event wishes to publish this development to a wider audience.
 
Something newsworthy happens - a new software release of an OSGeo project, for example.  The "owner" of said event wishes to publish this development to a wider audience.
  
=== 2) Creation ===
+
== Creation ==
The owner of their OSGeo-related newsworthy event or their proxy writes the release to the wiki using the [[Press Release Template]] and notifies the foundation of the url by emailing dev@visibilitycommittee.osgeo.org and board@visibilitycommittee.osgeo.org.
+
The owner of their OSGeo-related newsworthy event or their proxy writes the release to the wiki using the [[Press Release Template]] and notifies the foundation of the url by emailing viscom-dev@lists.osgeo.org and board@lists.osgeo.org.
  
=== 3) Review and Approval ===
+
== Review and Approval ==
* Review and approval - members of the Board and the Visibility Committee will have two days to review and comment on the content of the release.
+
* Review and approval - members of the Board and the [[Marketing Committee]] will have two days to review and comment on the content of the release.
  
 
* Legal review - because the foundation is a legal entity a quick review by our legal representative (on the board alias), will also be performed.  This need will be reduced depending on the content of the release and as we ascend the learning curve.
 
* Legal review - because the foundation is a legal entity a quick review by our legal representative (on the board alias), will also be performed.  This need will be reduced depending on the content of the release and as we ascend the learning curve.
Line 20: Line 18:
 
The review and approval process is driven by a member of the Visibility Committee, in concert with the initiator.
 
The review and approval process is driven by a member of the Visibility Committee, in concert with the initiator.
  
=== 4) Distribution ===
+
== Formats ==
  
''Due to the possibility of a Slashdot affect, CollabNet operations needs to be notified 24 hours in advance of press releases whenever possible. Please email Auke and Michael Lavoie at the following addresses as soon as you have an aproximate time and date: auke@collab.net, mlavoie@collab.net''
+
Press releases should be done in plain old ascii text.  If you wish to submit an HTML version (simple, bare-bones tags only!), that's cool.  If you want to submit in Word or Open Office, that's cool too. But you need to have a nice ASCII version first.
  
A) The press release gets published to the osgeo-news-publisher mailing list.  Journalists, bloggers and others potentially interested in OSGeo activities will be invited to join the list.
+
== Distribution ==
 +
 
 +
A) The press release gets published to the osgeo-news-publisher mailing list.  Journalists, bloggers and others potentially interested in OSGeo activities will be invited to join the list.  Currently this is done as per [https://www.osgeo.org/content/news/submit_news.html Submitting News Items] page.
  
 
B) The press release will also be submitted to:
 
B) The press release will also be submitted to:
Line 30: Line 30:
 
''for below sites that need logins, ask mpg for the password''
 
''for below sites that need logins, ask mpg for the password''
  
 +
* [mailto:news_item@osgeo.org OSGeo]
 
* [http://geoplace.com/pressrelease/login.asp GeoPlace.com]  (login:osgeo)
 
* [http://geoplace.com/pressrelease/login.asp GeoPlace.com]  (login:osgeo)
* [mailto:submit.news@consortiuminfo.org www.consortiuminfo.org]
+
* [mailto:submit.news@consortiuminfo.org Consortiuminfo]
 
* [http://slashgeo.org/submit.pl slashgeo]
 
* [http://slashgeo.org/submit.pl slashgeo]
 
* [http://linuxpr.com/members/submit.cgi LinuxPR]  (login:osgeo)
 
* [http://linuxpr.com/members/submit.cgi LinuxPR]  (login:osgeo)
 
* [http://www.newsforge.com/submit.pl NewsForge]
 
* [http://www.newsforge.com/submit.pl NewsForge]
 
* [mailto:tips@macnn.com MacNN]
 
* [mailto:tips@macnn.com MacNN]
* [mailto:news@gismngt.de www.gis-news.de]
+
* <s>[mailto:news@gismngt.de www.gis-news.de]</s>
 
* [mailto:jan@intevation.de www.freegis.org]
 
* [mailto:jan@intevation.de www.freegis.org]
* [http://www.directionsmag.com/press.releases/?duty=Contribute DirectionsMag] (login:mpg@osgeo.org)
+
* <s>[http://www.directionsmag.com/press.releases/?duty=Contribute DirectionsMag] </s> released 15 Sept(login:mpg@osgeo.org)
* [mailto:matteo@gismonitor.com GIS Monitor]
+
* <s>[mailto:matteo@gismonitor.com GIS Monitor]</s>
 
* [mailto:news@gisdevelopment.net www.gisdevelopment.net]
 
* [mailto:news@gisdevelopment.net www.gisdevelopment.net]
 
* [http://news.eoportal.org/share_news.html eoportal.org]
 
* [http://news.eoportal.org/share_news.html eoportal.org]
 
* [http://www.foss4g.org/FOSS4G/modules.php?name=Submit_News foss4g.org]
 
* [http://www.foss4g.org/FOSS4G/modules.php?name=Submit_News foss4g.org]
 
 
* [http://www.giscafe.com GIS Cafe] (login:osgeo)  ([https://secure.ibsystems.com/GIS/nbc/members/index.php])
 
* [http://www.giscafe.com GIS Cafe] (login:osgeo)  ([https://secure.ibsystems.com/GIS/nbc/members/index.php])
 +
* [mailto:press@gisuser.com GISuser.com]
 +
* [mailto:irloginews@iolfree.ie IRLOGI News (Irish Organisation for Geographic Information)]
 +
* [mailto:admin@cartographyonline.com cartographyonline.com]
 +
* [http://linuxtoday.com/contribute.php3 linuxtoday.com] (?same as linuxpr.com above?)
 +
* [http://lxer.com/module/newswire/stories/ LXer.com] (login:osgeo)
  
''For these sites, see mpg for contact info:''
+
''For these sites, see mpg for contact info (these are personal email addresses, not be be published):''
  
 
* [http://www.geospatial-solutions.com/geospatialsolutions Geospatial Solutions Magazine]
 
* [http://www.geospatial-solutions.com/geospatialsolutions Geospatial Solutions Magazine]
Line 53: Line 58:
 
* [http://www.eijournal.com Earth Imaging Journal]
 
* [http://www.eijournal.com Earth Imaging Journal]
  
 
+
== Translation ==
C) The Visibility Committee will also investigate the feasability and desirability of using an electronic news service such as http://www.prnewswire.com that reaches AP and UPI.  Accounts are free, but distribution costs are $300-400 per release.  Content gets submitted as a Word file.
 
 
 
=== 5) Translation ===
 
  
 
The final press release will be posted on the OSGeo site for translation by volunteers for localization and distribution to local news agencies.
 
The final press release will be posted on the OSGeo site for translation by volunteers for localization and distribution to local news agencies.

Latest revision as of 21:35, 17 September 2008

The goal is to have a simple and understandable process for creating, reviewing and issuing press releases.

Once initiated, the process will be driven by a member of the Visibility Committee. The basic steps are:

Conception

Something newsworthy happens - a new software release of an OSGeo project, for example. The "owner" of said event wishes to publish this development to a wider audience.

Creation

The owner of their OSGeo-related newsworthy event or their proxy writes the release to the wiki using the Press Release Template and notifies the foundation of the url by emailing viscom-dev@lists.osgeo.org and board@lists.osgeo.org.

Review and Approval

  • Review and approval - members of the Board and the Marketing Committee will have two days to review and comment on the content of the release.
  • Legal review - because the foundation is a legal entity a quick review by our legal representative (on the board alias), will also be performed. This need will be reduced depending on the content of the release and as we ascend the learning curve.
  • If other organizations are mentioned in the release, then they will also need to be included in the review process.

The review and approval process is driven by a member of the Visibility Committee, in concert with the initiator.

Formats

Press releases should be done in plain old ascii text. If you wish to submit an HTML version (simple, bare-bones tags only!), that's cool. If you want to submit in Word or Open Office, that's cool too. But you need to have a nice ASCII version first.

Distribution

A) The press release gets published to the osgeo-news-publisher mailing list. Journalists, bloggers and others potentially interested in OSGeo activities will be invited to join the list. Currently this is done as per Submitting News Items page.

B) The press release will also be submitted to:

for below sites that need logins, ask mpg for the password

For these sites, see mpg for contact info (these are personal email addresses, not be be published):

Translation

The final press release will be posted on the OSGeo site for translation by volunteers for localization and distribution to local news agencies.