Hello From reading a couple of messages recently there appears to be a few misconceptions of our PR process. The short answer is no, Louis does not control the press releases. However, Louis is a very active contributor in the area of OOo PR.
The checklist below is basically how the PR process works. PR activities are conducted on the [EMAIL PROTECTED] list. This is a private list to MP members. It is a working list as opposed to a discussion list in that any MP who wishes to be involved in PR is invited to join and contribute, i.e. no lurking :) Regards Jacqueline McNally Lead, OpenOffice.org Marketing Project OOoCon2006 in Lyon (http://marketing.openoffice.org/conference/) Are you a computer angel? (www.computerangels.org.au) ---///--- ACTIVITIES - Propose and accept topic or subject for press release. - Collate information (e.g. quotes, release notes, project infos}. - Identify where need additional information or assistance from other OOo members and or projects. - Develop English version of press release. See notes below with regard to press releases in languages other than English. MEMBERS OpenOffice.org members who /actively/ participate in the collation, generation, and distribution of PR. PR members may also be marketing contacts (marcons), e.g. some of the n-l PR team members are also marcons. PROCESS ***pr@ list is used: - To propose and discuss press release topics. - Draft outline and post to marcon list. This is to alert marcons that PR is in process and proposed schedule. Discussion with regard to press release to be held on pr@ list. - Discuss targeting and potential distribution of proposed press release. - Collate information. - Draft press release based on guidelines and template (see below). - Edit, proofread, draft to production copy. - Decide when final to post to marcon@ list for localisation and or translation, and distribution. ***marcon@ list is used: - Subscribers are marketing contacts based on a geographical basis nominated or volunteered from native-lang projects and other projects, especially the Marketing Project (MP). - Receive draft outline of press releases in development, i.e. notice of PR and schedule. Notify pr@ with any queries, concerns or discussion. - Marcons who wish to participate in PR development encouraged to join the pr@ list. - Receive final/production copy of PR to be used for localisation and or translation, and distribution in their area. ***guidelines and template - Establish guidelines and template to be used for press releases. - Establish process to update and maintain guidelines and template. - Establish and maintain plain text, HTML and OpenOffice.org (output to PDF) templates. *** website - Publish final press release (pdf). - Add to ongoing issue (http://www.openoffice.org/issues/show_bug.cgi?id=27664)used to collate pr, particularly from n-l projects. In addition or replace of posting to pr@ list. - Publish localised and translated press releases submitted to issue 27664. ***distribution 1. marcon@ list - Draft outline and final production copy to marcons. 2. [EMAIL PROTECTED] list - Final production copy with links to other languages to MP members. 3. announce@ - Final production copy to OpenOffice.org announcement list. 4. Global - MP Lead 5. MARCON members - in their region liaising with MP Lead where some publications are syndicated. ***frequency and timeline - Varies depending on the proposed topic. Timeline is tighter for new releases of OpenOffice.org due to working with other team members, e.g. release team. - Initially, would like to work towards having one press release per fortnight. They may not be applicable to all regions, i.e. distributed by marcons. Targeting to be discussed and developed by marcons and PR team. - Regardless of topic, each step of the process needs a turn around of at least 24-48 hours to allow for time differences. There are approx five steps (see "pr list is used" above). So I see the need for a continuous process. ***coordination - MP Lead to listen and fill in the gaps. - MP Lead to follow the process and let members know when we diverge. Consult with active participants and change the process or agree to resume current process. NOTES - Process is partly was has happened, and slightly altered to formalise future process. - In the past, process was to develop English version and marcon to translate. Would like to consider PR team generate in another language, and it to be translated into English for pushing to MARCON team for translation into other languages. - Potential to hold release until a number of translations are ready. Currently English version is released with other versions to follow. - [EMAIL PROTECTED] list to be used for marketing strategic and planning discussions inclusive of press releases, e.g. 2.0. - Joint press releases with Sun and other sponsors will require an extra process step of checking the production copy of the press release before it is posted to the marcon@ list. ---///--- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
