From Fedora Project Wiki
< Magazine
(Revision) |
(http -> https) |
||
Line 3: | Line 3: | ||
== Goal == | == Goal == | ||
The goal of this meeting is to set and execute a publishing schedule of appropriate material for the [ | The goal of this meeting is to set and execute a publishing schedule of appropriate material for the [https://fedoramagazine.org Fedora Magazine]. | ||
== Agenda == | == Agenda == | ||
Line 11: | Line 11: | ||
Typically we practice the same agenda each meeting: | Typically we practice the same agenda each meeting: | ||
# Retrospective of last week's [ | # Retrospective of last week's [https://fedoramagazine.org/wp-admin/index.php?page=calendar publishing timeline] | ||
#* Ensure all posts were echoed to social media | #* Ensure all posts were echoed to social media | ||
#* If any pending, reviewed stories are not published, schedule and assign social media duty | #* If any pending, reviewed stories are not published, schedule and assign social media duty | ||
# [ | # [https://fedoramagazine.org/wp-admin/edit.php?post_status=pitch&orderby=date&order=asc Pitch votes] (starting with oldest) | ||
#* '''GOAL:''' Determine whether pitch is appropriate for a story, and if so, move to Draft status and set publication date | #* '''GOAL:''' Determine whether pitch is appropriate for a story, and if so, move to Draft status and set publication date | ||
#* Include pitches in [ | #* Include pitches in [https://fedoramagazine.org/wp-admin/edit.php?post_type=feedback feedback] | ||
#* If not, either: | #* If not, either: | ||
#** Trash pitch, and assign someone to respond to author to thank them | #** Trash pitch, and assign someone to respond to author to thank them | ||
#** Assign someone to work with author to refine story idea | #** Assign someone to work with author to refine story idea | ||
# [ | # [https://fedoramagazine.org/wp-admin/edit.php?post_status=draft&post_type=post&orderby=date&order=asc Drafts not finished] (starting with oldest) | ||
#* '''GOAL:''' Determine if draft is ready for final review, and if so, move to Pending Review status | #* '''GOAL:''' Determine if draft is ready for final review, and if so, move to Pending Review status | ||
#* If not: | #* If not: | ||
Line 27: | Line 27: | ||
#* Assign for review and set to Pending Review status | #* Assign for review and set to Pending Review status | ||
#* Review/set publication date and add to schedule | #* Review/set publication date and add to schedule | ||
# [ | # [https://fedoramagazine.org/wp-admin/edit.php?post_status=pending&post_type=post&orderby=date&order=asc Pending Review] (starting with oldest) | ||
#* Confirm editor deadline | #* Confirm editor deadline | ||
#* Review/set publication date and confirm schedule | #* Review/set publication date and confirm schedule |
Revision as of 18:54, 20 November 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
- Ensure all posts were echoed to social media
- If any pending, reviewed stories are not published, schedule and assign social media duty
- Pitch votes (starting with oldest)
- GOAL: Determine whether pitch is appropriate for a story, and if so, move to Draft status and set publication date
- Include pitches in feedback
- If not, either:
- Trash pitch, and assign someone to respond to author to thank them
- Assign someone to work with author to refine story idea
- Drafts not finished (starting with oldest)
- GOAL: Determine if draft is ready for final review, and if so, move to Pending Review status
- If not:
- If author is still working, editor is responsible for ensuring completion
- If author is MIA for 2nd week, drop back to Pitch and rearrange publication schedule
- Assign for review and set to Pending Review status
- Review/set publication date and add to schedule
- Pending Review (starting with oldest)
- Confirm editor deadline
- Review/set publication date and confirm 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.