Fedora Magazine editorial meetings

The goal of this meeting is to set and execute a publishing schedule of appropriate material for the Fedora Magazine.

Meetings happen every Wednesday 12:00 - 13:00 UTC on IRC in the #fedora-meeting channel on freenode. See the Fedora Magazine Editorial board meeting in the Fedora calendar.


Roll call

#startmeeting Magazine editorial board
#meetingname magazine
#topic Roll call
#chair stickster ryanlerch cverna asamalik sub_pop gregbartholomew bcotton misc rwaltr


#topic Agenda
#link https://docs.fedoraproject.org/en-US/fedora-magazine/workflow/
#info -- 1/ Last week's stats --
#info -- 2/ In progress followup --
#info -- 3/ Finished articles to review --
#info -- 4/ Articles to edit --
#info -- 5/ Publishing schedule --
#info -- 6/ Article proposals to clarify / approve --
#info -- 7/ Open floor --

1/ Last week’s stats

#topic 1/ Last week's stats
#info Week of <MONTH DD>: <NN.N>K pageviews -- <COMMENT>

2/ In progress followup

#topic 2/ In progress followup
#info Looking at the 'in progress' column, is there something that's been finished? Anything to follow up on with its author?
#link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban

3/ Finished articles to review

#topic 3/ Finished articles to review
#info Looking at the 'review' column, let's decide which articles are good to go. Move each either to the 'to edit' (finished) or to the 'in progress' (needs more work) and provide feedback.
#link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban

4/ Articles to edit

#topic 4/ Articles to edit
#info Looking at the 'to edit' column, assign an editor and a cover image creator.
#link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban

5/ Publishing schedule

#topic 5/ Publishing schedule
#info Looking at the 'queued' and 'to edit' columns, decide the publishing schedule for the next week period.
#info If there is not enough content, we might also need to look at the 'in progress' or even the 'article spec' columns come up with additional content.
#link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban
#proposed #agreed PUBLISHING SCHEDULE:
DAY DATE, NAME (NICK:edit/NICK:image) --
DAY DATE, NAME (NICK:edit/NICK:image) --
DAY DATE, NAME (NICK:edit/NICK:image) --

6/ Article proposals to clarify / approve

#topic 6/ Article proposals to clarify / approve
#info Review the the article proposals and decide about what's next — a new article spec? more discussion?
#link Article proposals: https://pagure.io/fedora-magazine-proposals/issues

7/ Open floor

#topic 7/ Open floor

Meeting ends


After the meeting

Send the minutes to the list Subject: Editorial board meeting recap YYYY-Mmm-DD


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 magazine list. An example is a Firefox security issue.