#289 Announcing Fedora bootc
Closed: published by rlengland. Opened by rlengland.

Article Summary:

Promoting Fedora Bootable Containers and a proposed community initiative around it

Article Description:

The purpose of this article would be to share with the Fedora audience the availability of a bootable containers for Fedora, and interest this audience in getting involved with a community initiative that will bring together representatives from different WGs to collaborate on bootable containers. This technology, and the way it’s being implemented now, makes image-based Fedora spins much much simpler to create and to collaborate around, which stands to benefit Fedora users. The flow of the article would be as follows:

  • What are bootable containers and what are the roots of this tech in Fedora
  • How are current WGs using this tech, and how might they collaborate on it
  • Share about a proposed community initiative around Fedora bootc (bootable containers)
  • Share links to documentation and communication channels for getting started with Fedora bootc

https://discussion.fedoraproject.org/t/article-proposal-announcing-fedora-bootc/115868


Metadata Update from @rlengland:
- Issue assigned to jasonbrooks
- Issue tagged with: article, needs-image

I've added a draft of the article into the wp admin console. I would like to publish this on Tuesday morning, May 7, if possible.

Metadata Update from @rlengland:
- Custom field preview-link adjusted to https://fedoramagazine.org/?p=40343&preview=true

@jasonbrooks
We usually publish articles on Monday, Wednesday, or Friday, but if you have a specific need for a Tuesday we can accommodate that.

In a first pass on your article I noted that these two links had difficulties:

Link proposed initiative links to http://LinkTk and "Can't be found"
Link bootc tag links to https://discussion.fedoraproject.org/tag/bootc and returns "That page doesn’t exist or is private."

Metadata Update from @rlengland:
- Custom field publish adjusted to 2024-05-07

By the way, do you have a preference for a featured image to accompany you article? Perhaps a logo or image that is freely licensed, such as CC-BY or CC-BY-SA. If not the editors can put something together for you.

Hey @rlengland, thanks for the review. I've added the proposed initiative link to the text, and I believe the tag is getting created. I'll check back on that.

On the publish date, I'm trying to coordinate with some upstream parties on timing, so if we could schedule for Tues morning, that would be awesome. It looks like the publish metadata is set.

On an image, I don't have something particular in mind, as is so often the case with software, it's not super visual :) Would a Fedora logo be too redundant?

@jasonbrooks I've made a few wordsmithing changes, nothing that should modify the information but another review on your part would be good.

We can publish on 7 May, not a problem.

I've added a featured image. See if it meets your approval.

Please verify that all the links in the article resolve properly. The links in the article have all been set to open a new browser window from a preview. That may make checking easier.

When you give me the "OK" we'll schedule for publication.

Metadata Update from @rlengland:
- Custom field editor adjusted to rlengland
- Custom field image-editor adjusted to rlengland

Thanks @rlengland, it's got my OK. I confirmed that @mattdm is going to create the bootc tag, so that last link should resolve soon.

Metadata Update from @rlengland:
- Issue untagged with: needs-image

@jasonbrooks @mattdm Just a subtle :clock830: reminder that the "bootc tag" link needs to resolvable before some time tonight if this article is to be published tomorrow.

Thanks

@rlengland Matthew created the topic as bootc-initiative -- I'm having trouble with fedora sso right now, can you modify the link to fix this?

Nevermind, I was able to log in @rlengland

@jasonbrooks I think we are good to go. I'll do the final schedule and the article should be posted 7 May at 0800 UTC

Thank you.

Issue status updated to: Closed (was: Open)
Issue close_status updated to: published

Metadata