Difference between revisions of "Press Release Process"
Line 9: | Line 9: | ||
=== 2) Creation === | === 2) Creation === | ||
− | The owner of the newsworthy event or their proxy writes the release to the wiki, and notifies the Visibility Committee of the url by emailing dev@visibilitycommittee.osgeo.org | + | The owner of the newsworthy event or their proxy writes the release to the wiki using a standard template (to come), and notifies the Visibility Committee of the url by emailing dev@visibilitycommittee.osgeo.org |
=== 3) Review === | === 3) Review === |
Revision as of 13:57, 2 May 2006
Press Release Process - Draft
The goal is to have a simple and understandable for creating, reviewing and issuing press releases. Feel free to contribute your thoughts and experience.
There are five basic steps:
1) Conception
Something newsworthy happens - a new software release, for example. The owner of said event wishes to publish this development to a wider audience.
2) Creation
The owner of the newsworthy event or their proxy writes the release to the wiki using a standard template (to come), and notifies the Visibility Committee of the url by emailing dev@visibilitycommittee.osgeo.org
3) Review
Legal review - because the foundation is a legal entity, a quick review by our legal representative is required.
If other organizations are mentioned in the release, then they will also need to be included in the review process.
Open question: is the review process driven by VisCom or the creator?
4) Approval
By VisCom or board?
5) Distribution
The press release gets published to the osgeo-news-publisher alias. This alias will be seeded with journalists and others known to be interested in OSGeo activities, to include:
- submit.news@consortiuminfo.org (see: http://www.consortiuminfo.org/bulletins/ ).
- DirectionsMag online
- Slashgeo online
- GeoPlace.com online