This is a worthwhile discussion. Aleksandra, we really appreciate the contribution and the thoughtful comments. Also, I can understand that one likes to get as big an audience as possible for one's efforts. I had a couple thoughts: It's important to recall the Magazine's audience is Fedora users. We don't assume they have any interest in what goes into making Fedora, or the workings of our community, unless it has a direct effect on them or they can participate with close to zero knowledge. So for example, we can tell them about Fedora Classroom, which is designed for people with close to zero knowledge, or about a Test Day, where a tester can follow a process step by step if they have required hardware and contribute results, or the wallpaper submissions for which you technically only need a camera. Or we might tell them about a critical security flaw and how to protect themselves. But we don't do articles about Fedora governance, release process, infrastructure, marketing efforts, and so on. Through this lens, we can tell that, while we consider CI very important to building Fedora now (and, I hope, a *LOT* more in the future), it's not something users will see for themselves. They do benefit from it in the end, of course, in the same way they benefit from worthwhile patches being worked upstream to improve software. But it needn't be visible to them. But here's another angle -- Are there general CI tools available in Fedora that could form the basis for an interesting article about CI on the Magazine? That might be a great way to inform users in a less obvious way. The mention of how CI is used in Fedora would only be a short epilogue to that article, not the main point. But it would be enough to make the topic more relevant to an end user. Paul On Mon, Dec 03, 2018 at 02:32:17PM +1000, Ryan Lerch wrote: > Earlier this year, we did have this post: > > https://fedoramagazine.org/contributing-fedora-testing-packages/ > > If i recall correctly, during the editorial meeting on this topic, it was > decided that it was the edge of going either to the community blog, or > staying on the magazine. Ultimately, we did post it on the magazine, as it > is an entry level contributor task. Anything more detailed, or involving > building packages or similar IMHO is more community blog focused. > > cheers, > ryanlerch > > On Mon, Dec 3, 2018 at 12:30 AM Aleksandra Fedorova <alpha@xxxxxxxxxxxx> > wrote: > > > Hi, > > > > My original proposal was about very practical How-To article, targeted to > > people who are already Fedora Packagers. > > So from this point, the Community Blog looks logical. > > > > But there are two concerns though. > > > > 1) as it says in [1] > > > > Ideally, Community Blog posts are big headlines pointing out the big > > stuff to be aware of. Someone can drill down on the details by following > > hyperlinks to learn more. > > > > My article with step-by-step how to doesn't fit into this description. I > > want it to be _the_place_. where you point to. That is why I was thinking > > of it as the article in a journal, not a mail to devel-list or a blog post. > > > > 2) The word CI is so rarely used around Linux distributions it would be > > nice to mention it once in a while in public. > > Thus making a bit of CI-noise on Fedora Magazine could be a good thing > > (right now there is not even a tag for it). > > Even if people won't be interested in the exact details of the article, > > they should still know that there is CI, and it actually works. > > > > > > Adam, > > would it work better for Fedora Magazine if I add some short introduction > > on how CI works at the beginning and make it more accessible for outsiders? > > > > > > [1] > > https://communityblog.fedoraproject.org/writing-community-blog-article/ _______________________________________________ Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to magazine-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/magazine@xxxxxxxxxxxxxxxxxxxxxxx
