From Fedora Project Wiki
< Magazine
(→Agenda) |
No edit summary |
||
Line 15: | Line 15: | ||
#* Reassign any pending stories if necessary | #* Reassign any pending stories if necessary | ||
# Pitch votes | # Pitch votes | ||
#* Include pitches in [http://fedoramagazine.org/wp-admin/edit.php?post_type=feedback feedback] | |||
#* If yes, is now an unfinished draft | #* If yes, is now an unfinished draft | ||
#* If no, suggest new scope to contributor and trash pitch | #* If no, suggest new scope to contributor and trash pitch |
Revision as of 19:37, 1 September 2015
Schedule: See Marketing team calendar
Goal
The goal of this meeting is to set and execute a publishing schedule of appropriate material for the Fedora Magazine.
Agenda
Typically we practice the same agenda each meeting:
- Retrospective of last week's publishing timeline
- Move any pending stories to this week's schedule
- Reassign any pending stories if necessary
- Pitch votes
- Include pitches in feedback
- If yes, is now an unfinished draft
- If no, suggest new scope to contributor and trash pitch
- Drafts not finished
- ETA? If still not finished for >2 weeks, consider dropping (this means new pitches have no more than 2 weeks to turn in)
- Assign for review
- Review/set publication date and add to schedule
- Pending Review
- Assign for review
- Review/set publication date and add to schedule
Exceptions
The following types of articles generally can route around the weekly meetings. This helps us get critical information out to the audience without waiting for the next board meeting.
- Security updates
- Critical security updates that affect a broad user audience are pre-authorized. Generally an editor will write the update article. If possible, one other editor does a quick spot check. If that would affect the timing, however, the posting editor simply publishes the article and notifies the marketing list. An example is a Firefox security issue.