Fedora Magazine editorial meetings
The goal of this meeting is to set and execute a publishing schedule of appropriate material for the Fedora Magazine.
The meeting is powered by zodbot. You can use the following commands the start the meeting, to set topics, record important information and decisions, etc.
To start the meeting, run the following set of commands.
#startmeeting Magazine editorial board #meetingname magazine #topic Roll call #chair glb rlengland theevilskeleton cverna asamalik
People will then join using a
.hello2 or a
.hello NICK command.
This is the standard agenda. Announcing it in advance helps newcomers understand the structure of the meeting.
#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/ Editor of the Week -- #info -- 7/ Open floor --
#topic 1/ Last week's stats
#info Week of <MONTH DD>: <NN.N>K pageviews -- <COMMENT>
#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
Review anything that’s in progress. If an article is stuck in progress for a long time without an update, contact the author and ask them if they still plan to finish their work.
Anything that’s already finished can be moved to the Finished column.
You may also want to check the QA calendar for upcoming test days so that we can expect a new post submission. These tend to come in with very short notice, so the Editor of the Week should use their best judgment in deciding when to publish.
#info Are there any upcoming test days? #link https://calendar.fedoraproject.org/QA/
Also check the release schedule for upcoming tasks. This is generally only important a few weeks before the Beta and Final releases, but it doesn’t hurt to check just to keep it in mind.
#info Review release schedule #link https://fedorapeople.org/groups/schedule/f-<N>/f-<N>-magazine-tasks.html
(where <N> is the release being developed)
#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
Authors mark their articles as finished by moving them to this column. Review the articles and ehtier move them to the To Edit column, or in case they need some additional work, ask the author in the card about it and move it back the In Progress.
#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
Assign an editor and a cover image designer to each article so it can be moved forward.
#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
Setting the publishing schedule for the upcoming week period is one of the main goals of this meeting.
Decide which articles should be published when and set the dates for each card on the board.
The next step is to vote on the publishing schedule along with other attendees of the meeting. A proposal of the schedule has the following format:
#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) --
This can be generated by a script. Run:
$ podman run --rm -it asamalik/magazine-schedule
The script consumes data from the individual cards, so please make sure the date, and the assignees are set properly.
Find more information about the script in the asamalik/magazine-schedule github repository.
When the schedule is set and agreed upon, announce it by:
#agreed PUBLISHING SCHEDULE: DAY DATE, NAME (NICK:edit/NICK:image) -- DAY DATE, NAME (NICK:edit/NICK:image) -- DAY DATE, NAME (NICK:edit/NICK:image) --
Before the end of the meeting, we need to select next week’s Editor of the Week.
#topic 6/ Editor of the Week
Announce the volunteer using:
#info XXXX will be Editor of the Week next week
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.