Follow the directions for getting access at Getting access :: Fedora Docs Make certain you have signed the FPCA (Fedora Project Contributor Agreement) and that you have signed into Taiga. This is necessary before we can assign the Taiga card to you.
We use the Taiga cards to comment on the article as it progresses and to answer questions from the authors, from time to time. It is a handy way of keeping track of the article progress for both the authors and the editors. Also a good place to ask for help about specifics of what you are writing if needed.
When you have access you can start writing your article at Fedora Magazines Wordpress site, just log in with you FAS ID and create the post.
Once you are added to the magazines project tracking (Taiga) as a writer, and assigned to the card for your article spec by an editor you can move the card to in progress while you are writing the article. After you have completed the article, and feel it is ready for review, move the card to the Review column.
The editorial board meets weekly (Thursday’s at 1500 UTC) at #fedora-meeting channel on libera.chat (irc), and will review the article at that time and decide if it is ready for publishing or not. If publishing is decided, then an Editor and Image creator are assigned (often the same person) and the article gets scheduled. If the editors feel the article needs more work, it will be moved back to the in progress column, and the author will be informed of the reason(s), usually with helpful suggestions on what needs some more work.
@yannickduclap It looks like you have done some of the steps I suggested. I see you have accepted the FPCA but I expect you may have not logged in to Taiga as I show you pending membership there. Please check the steps over any way and log into Taiga so we can get that card assigned to you.
Thanks (and thanks in advance to your wife for reviewing )
It needs to be re-covered. 2016 is some time ago and honestly, anyone coming across it would be discouraged by the date. Linux is full of articles and commands sometimes going back decades, that new users look at, and assume it no longer applies to the current version due to the article date. I will say the same for podman, toolbox, policycoreutils-sandbox and a couple others…
hi, while doing some more research, I read this old article which explains why using systemd-nspawn is better than using chroot to run a command on a third party OS especially from systemd. I understand better why you proposed to make an article about it and I encourage you to do so… I find mine much less useful suddenly…
I read your article on Fedora magazine and it was great ! Congrats to you for that !. Love the example of using the Fedora Security spin as well. Cheers !
My use case for systemd-nspawn is different than the " chroot > recover system > happy " steps most use it for. I like to sandbox applications with it and have been doing so since Fedora 25. Flatpak and Podman have changed my work flow slightly and solved the no root required option, but toolbox falls short a bit here. policycoreutils-sandbox works great for isolation but it’s never covered.
a write up of these things would be an amalgamation of process, use case and how to’s. It would be more of a series than a write up…
I think podman need more attention, “What/Why you need to use podman, How to use” etc. There are so many articles that tie podman to docker, when you can effectively ignore docker altogether.
All of that sounds to me like stuff that other people might want to do as well. Certainly if you are using Fedora Linux and/or other FOSS to do it, such articles would be very welcome on the magazine. If it is highly complex, try to break it down into smaller “bite sized” pieces that people can read and comprehend in just a few minutes. There are no length requirements however. If it needs to be longer, that is OK.