Hello @rlengland I added a draft of an article on cool use cases for Fedora CoreOS. The article has been check by @joseph and I also collaborated with members of the Fedora CoreOS chat room during the writing process. I would appreciate your feedbacks and approval of the article. Here is the preview link: https://fedoramagazine.org/?p=40065&preview=1&_ppp=c41ad02db1 The Fedora CoreOS team and QA team are running test days from April 01 to April 07 and they mentioned that they would like to invite readers to check and participate with the post. I look forward to your response
Metadata Update from @aishat: - Custom field preview-link adjusted to https://fedoramagazine.org/?p=40065&preview=1&_ppp=c41ad02db1 - Issue assigned to aishat
@aishat The editors will take a look at your article.
Note that Pagure tickets are opened by the editors not by the authors.
For future reference there is a process for proposing an article and a work flow for getting them published. It would help the editors if you would follow that in the future to ensure that your articles are seen, reviewed, and edited in a timely manner. https://docs.fedoraproject.org/en-US/fedora-magazine/writing-a-pitch/ https://docs.fedoraproject.org/en-US/fedora-magazine/workflow/
Guidelines for writing are available here: https://docs.fedoraproject.org/en-US/fedora-magazine/contributing/
@aishat By the way there has already been an article posted for "Test Days" that included the announcement for CoreOS. This was coordinated with @sumantrom https://fedoramagazine.org/contribute-at-fedora-coreos-podman-and-toolbx-test-days/
....This is a duplicate of Pagure ticket #274 opened by @glb 3 hours ango and assigned to you, @aishat.
I am closing this ticket and we will continue tracking with #274
Thank you for the contribution, but please note the information about work flow I pointed to in a previous comment.
Metadata Update from @rlengland: - Issue tagged with: article
Issue status updated to: Closed (was: Open) Issue close_status updated to: published
Thank you very much @rlengland for your correction and guidance. I sincerely apologize for the confusion, I will make sure to follow the right process in the future