From Fedora Project Wiki
(MOARLINKZ)
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 publishing timeline
+
# Retrospective of last week's [http://fedoramagazine.org/wp-admin/index.php?page=calendar publishing timeline]
 
#* Move any pending stories to this week's schedule
 
#* Move any pending stories to this week's schedule
 
#* Reassign any pending stories if necessary
 
#* Reassign any pending stories if necessary
# Pitch votes
+
# [http://fedoramagazine.org/wp-admin/edit.php?post_status=pitch&post_type=post Pitch votes]
 
#* Include pitches in [http://fedoramagazine.org/wp-admin/edit.php?post_type=feedback feedback]
 
#* 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
# Drafts not finished
+
# [http://fedoramagazine.org/wp-admin/edit.php?post_status=draft&post_type=post 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)
 
#* 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
 
#* Assign for review
 
#* Review/set publication date and add to schedule
 
#* Review/set publication date and add to schedule
# Pending Review
+
# [http://fedoramagazine.org/wp-admin/edit.php?post_status=pending&post_type=post Pending Review]
 
#* Assign for review
 
#* Assign for review
 
#* Review/set publication date and add to schedule
 
#* Review/set publication date and add to schedule

Revision as of 19:40, 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

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
    • Include pitches in feedback
    • 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.
https://www.fedoraproject.org/w/index.php?title=Magazine/Editorial_meetings&diff=prev&oldid=421355
www.fedoraproject.org
crawl=CC-MAIN-2021-25
25142
application/http; msgtype=response
sha1:4UKWABIUAQDPJOYIGCRKMLNICO4HIJHP
<urn:uuid:0a674c01-1032-475a-a7d7-596d5053e8ec>
2021-06-23T13:02:13Z
140.211.169.206
text/html
sha1:APEIXGLCXMDV34GRVTYH6WMRXHDGWJAY
<urn:uuid:23aac3b8-91cf-471c-861b-3f4851c68f40>
https://www.fedoraproject.org/w/index.php?title=Magazine/Editorial_meetings&diff=prev&oldid=421355
response
<urn:uuid:8336e714-c942-483c-a58e-1a15a17604d5>
isPartOf: CC-MAIN-2021-25
publisher: Common Crawl
description: Wide crawl of the web for June 2021
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-168.ec2.internal
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/