Planning to write an extension of my previous article on buildah based
on below points
1) Using Docker file to create image
2) using buildah bud to allocate cpu, memory limits
3) mounting volumes using buildah command
4) buildah commit
5) buildah copy
Looking for approval and suggestions
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 asked a question here, a few days back, to get recommendations on
screencasters. Unfortunately nothing worked for me. I ask at Ask Fedora
and got the explanation of the problem root and a solution. The link
below is to the Ask Fedora thread in case anyone here is in need of a
screen caster that does both audio and video and works well with F31 and
Have a Great Day!
Here are some editorial guidelines we've previously had around the
Magazine. We've added some new editors recently, and I don't think
these have been clearly communicated elsewhere.
It's not my place to say these are "forever rules." We can decide to
change them. But we need to agree on and respect a "voice" for the
Magazine, so we don't confuse or put off readers with severe tonal
shifts from article to article. Let's see whether we agree on these.
If so, they can be included on docs.fp.o.
1. Articles in the Magazine generally don't refer to the Magazine
staff or the Fedora Project ("we", "us," "our"). Neither authors nor
the Magazine staff speak for all of the Fedora Project contributors.
The Magazine is also not an amplifier for a specific team.
RULE: Editors should rewrite sentences to eliminate "we," "us," and
"our," or work with the author to do so.
EXCEPTIONS: It's OK to use "we" if the specific usage is relating
something about the Magazine, however -- like soliciting contribution,
for example. In those cases we're speaking as a group.
(Are there other reasonable exceptions?)
2. Articles in the Magazine generally don't refer to their author
("I", "me," "my"). The Magazine doesn't publish op-ed pieces or
personal blogs; it publishes factual help and news articles. The
Magazine does not rely on personal statements from authors; it's the
editors' job to check accuracy, so readers can rely on articles.
RULE: Editors should rewrite sentences to eliminate "I," "me," and
"my," or work with the author to do so.
EXCEPTIONS: It's OK to use "I" if the article is a personal
announcement, such as from the FPL.
(Are there other reasonable exceptions?)
I made this draft:
The working title is *Fedora - The Origins* and my idea is covering the
time prior the first release and the first release itself. I'm thinking of
adding a part about the technical bits of this first release such as system
requirements and type of software included, maybe with some screenshots or
images, to give an idea how this system looked like in the beginning. I
don't know what others think.
Still waiting to be added to the Team Writers in Taiga.
I propose the following publishing schedule for the upcoming week:
Wednesday 27 November:
#105 How to rebase to Fedora 31 on Silverblue(needs edit + image)
Friday 29 November:
Create and install a virtual machine using Cockpit (ready)
Monday 2 December:
#45 Quick introduction to Toolbox (needs image)
Wednesday 4 December:
#69 Using Ansible to organize SSH keys (needs edit + image)
I'll edit and provide an image for the #105 for this Wednesday so we can
get it out — it's a bit overdue so I shifted the rest of the schedule in
order to get it out ASAP.
Anyone can edit or make an image for the rest?
Senior Software Engineer