In my article "Organizing those 1s and 0s" I want to answer Frank, but
I'm not sure about magazine policy on the comment by seeker_moc. It
seems I can only approve both for posting. What shall I do?
Have a Great Day!
Hey everyone, I've just mentioned this in the "Holiday schedule coverage"
thread, but to make it easier for people to find, here's my proposal for
publishing schedule for the following week period:
Wed 11 Dec 2019: #105 How to rebase to Fedora 31 on Silverblue
Fri 13 Dec 2019: #104 Organizing all those 1s and 0s
Mon 16 Dec 2019: #93 Setting up and configuring the sway window manager
Wed 18 Dec 2019: #106 Using the screen utility
Senior Software Engineer
One weakness of the current editorial workflow is that there's no
obvious way to indicate that an article needs a featured image. There
are four possibilities I see. What does the team think?
1. Create a new column
Advantages: Easy to see which articles need images so that people can
easily claim those.
Disadvantages: Adds another step to the flow and doesn't represent
well that images can be done in parallel to editing.
2. Use a tag
Advantages: Color coding means the card indicates the article needs an
image in most view.
Disadvantages: It's not clear what the color coding means unless you
3. Use a custom field
Advantages: Can have multiple choices to represent state (needed, in
Disadvantages: Not visible without opening the card
4. Use a task within the user story
Advantages: Can be assigned and have it's own state. We could also
potentially do the same for editing, though that might be redundant.
Disadvantages: Not visible without opening the card.
He / Him / His
Fedora Program Manager
The holiday period in December will be here before you know it. The
Magazine has a lot of staff who are planning vacation and PTO time
over that period. That doesn't mean everyone will automatically
disappear. But in my case, I tend to spend my vacation away from the
keyboard and doing other things. I bet some others do likewise. The
hardest period to cover will be December 23 - January 1 -- which is 5
slots in our normal schedule. So we should figure out how to pre-fill
our schedule and not have the Magazine "run dry" for several weeks.
Here are some ideas for how we could accomplish this. But we need
other ideas and content, too. Please contribute your ideas and we can
discuss in the next meeting (Wednesday 1300 UTC, 8:00am EST, 2:00pm
CEST in IRC Freenode #fedora-meeting).
(1) If you're a new writer we would still love to have your
contributions early, so we could schedule articles to publish over the
(2) We could make a "best of 2019" series that would run for 3-5 slots
on the Magazine. Last year I think we chose articles that represented
for developers, sysadmins, and user tools. We could use those or even
add a couple categories. We could do a year-end wrap up as well.
(3) We could resurrect a few articles to refresh and repost. You can
reset a published article to scheduled, and it will be re-posted on
the new date. If we do this, the article should be checked for
accuracy and updated as needed to reflect Fedora 31 reality.
(4) We could get a bunch of like-minded writers to participate in a
new series that we finish and schedule to run over the holidays.
Other ideas are welcome.
I recently introduced myself to you for the first time. I saw there was an article spec about screen that was unassigned. I assigned it to myself and started working on the article (that you can see at https://fedoramagazine.org/?p=29819&preview=true).
Now I feel I have nothing else to write about the topic unless there's anyone to tell me there's anything to change, add or remove. I moved the user story to "Review" in Kanban.
Is that how everything is supposed to be done? Am I just supposed to wait now until anyone reviews it?