Hello, I've drafted an article discussing how Fedora Infrastructure is
turning off our Modern Paste servers and switching `fpaste` to use the
CentOS pastebin instead.
Please review and provide any feedback. The sooner we can get it out,
the better, because we are turning off those servers on December 1.
I tried posting it to the Community Blog instead but they said it should
go to Magazine instead.
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 think your email was caught up in the same "invited before logged in"
issue we've recently been having. Try again now.
On Fri, Nov 8, 2019, 5:05 PM Gregory Lee Bartholomew <
> I don't seem to have that option. Screenshot attached.
> Gregory Lee Bartholomew
> PGP Key ID: 3B67510E
> On November 8, 2019 9:59:28 PM UTC, Paul Frields <stickster(a)gmail.com>
> >I see "Type a new comment here" in a field directly under the last
> >On Fri, Nov 8, 2019, 1:57 PM Gregory Lee Bartholomew <
> >gregory.lee.bartholomew(a)gmail.com> wrote:
> >> Just now, I wanted to reply to Ryan through the teams system here:
> >> But I cannot seem to find the reply button. I am logged in. Am I
> >> something?
> >> Thanks.
> >> --
> >> Gregory Lee Bartholomew
> >> PGP Key ID: 3B67510E
> >> _______________________________________________
> >> Fedora Magazine mailing list -- magazine(a)lists.fedoraproject.org
> >> To unsubscribe send an email to
> >> Fedora Code of Conduct:
> >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> >> List Guidelines:
> >> List Archives:
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