From Fedora Project Wiki
Line 24: Line 24:
 
#* Assign for review
 
#* Assign for review
 
#* Review/set publication date and add to schedule
 
#* 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 {{fplist|marketing}} list.  An example is a Firefox security issue.

Revision as of 13:55, 31 August 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

Note.png
Not set in stone
This is still a work in progress and input is gratefully accepted! We are trying to achieve an agenda we can follow each meeting, so any editor can chair if needed.

Typically we practice the same agenda each meeting:

  1. Retrospective of last week's publishing timeline
    • Move any pending stories to this week's schedule
    • Reassign any pending stories if necessary
  2. Pitch votes
    • If yes, is now an unfinished draft
    • If no, suggest new scope to contributor and trash pitch
  3. 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
  4. 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.