From Fedora Project Wiki
m (moved Talk:Marketing HOWTO write a press release to Talk:How to write a Fedora press release: Use plain English title) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
I think that this HOWTO misses some detailed "approval" chain description: | I think that this HOWTO misses some detailed "approval" chain description: | ||
Let's say I decide to write a Press Release regarding Fedora 12, I probably need to announce my intention initially to the group then discuss some details on the scope and goals of that press release (maybe coordinate my efforts with ambassadors group or involve some technical group if I have in mind pinpointing some novelty), create a draft and ask for comments (in a strict timetable) and then release the material to the press?? | Let's say I decide to write a Press Release regarding Fedora 12, I probably need to announce my intention initially to the group then discuss some details on the scope and goals of that press release (maybe coordinate my efforts with ambassadors group or involve some technical group if I have in mind pinpointing some novelty), create a draft and ask for comments (in a strict timetable) and then release the material to the press?? | ||
: +1. I think a detailed approval chain isn't needed as a strict ''requirement,'' but some good practices for notification should certainly be written... this might make a good "Let's all pile into Gobby!" document writing and revising sprint some week. [[User:Mchua|Mel Chua]] 20:42, 19 November 2009 (UTC) | |||
Latest revision as of 20:42, 19 November 2009
I think that this HOWTO misses some detailed "approval" chain description: Let's say I decide to write a Press Release regarding Fedora 12, I probably need to announce my intention initially to the group then discuss some details on the scope and goals of that press release (maybe coordinate my efforts with ambassadors group or involve some technical group if I have in mind pinpointing some novelty), create a draft and ask for comments (in a strict timetable) and then release the material to the press??
- +1. I think a detailed approval chain isn't needed as a strict requirement, but some good practices for notification should certainly be written... this might make a good "Let's all pile into Gobby!" document writing and revising sprint some week. Mel Chua 20:42, 19 November 2009 (UTC)