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 https://fedoraproject.org/wiki/Zodbot[zodbot]. You can use the following commands the start the meeting, to set topics, record important information and decisions, etc.
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:
The script consumes data from the individual cards, so please make sure the date, and the assignees are set properly.
This can be generated by a script. Run:
This is the standard agenda. Announcing it in advance helps newcomers understand the structure of the meeting.
#topic 1/ Last week's stats
#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
#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
#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
#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
#topic 6/ Editor of the Week
#topic 7/ Open floor
#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 --
To start the meeting, run the following set of commands.
When the schedule is set and agreed upon, announce it by:
(where <N> is the release being developed)
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.