I think that although some users may be expecting the Fedora Magazine
to be a knowledge resource, it is superfulous to the mandate of the
magazine. That being the spreading of information about Fedora-centric
"stuff". There are many times that articles fall into the howto or are
very technical in nature, this is indemic of the topic area chosen not
so much a core purpose of Fedora Magazine which is a place to talk
about all things Fedora related. There could be an arguement for some
articles to be copied over to the Quick Docs site if they present a
bona fide source of information that is seen to be important for the
community around Fedora. Tagging old articles, or even worse IMO
updating them to current best practices/ latest tech, does not fall
into the Fedora Magazine role. More importantly, there are limited
resources working on the project across the spectrum, no different in
the case of Fedora Magazine, so adding workload will always force a
decision on what to drop doing this week. Even the example post cited
as a reason in support of updating old/out of date magazine articles,
was an example of a user trying to do something that was very likely
out of their technical depth of understanding. More of their
frustration seemed to come from communication or a lack thereof.
This is just my two cents worth on the subject.
On Wed, 2019-05-29 at 22:30 +0200, Lennart Jern wrote:
How about something like what OMG! Ubuntu does? After a certain time
year?) they add a disclaimer at the top of the article.
Just a simple "this article is old, take it with a grain of salt".
See this for example:
On Wed, May 29, 2019 at 3:41 PM Ankur Sinha <sanjay.ankur(a)gmail.com>
> On Wed, May 29, 2019 21:53:19 +1000, Ryan Lerch wrote:
> > <snip>
> > It is important to note too that the Fedora Magazine is really a
> > blog /
> > source, not documentation.
> The target audience of the magazine does not make this distinction.
> wish they did, but it appears that as far as they are concerned,
> are both simply official sources of information.
> > Do users expect to read an article that is several years old and
> > have
> > instructions in that still work?
> If they find the article via an internet search, not only do they
> them, they ask why documented information does not work:
> As you,'ll see there, this led me to file this ticket with docs:
> > Would we then have to update say all the old Release
> > Announcements to
> > say this is an old version that has been EOL'ed?
> We do something of the sort already:
> > While this would be something nice to have, IMHO keeping old
> > articles
> > up-to-date should definitely have a much lower priority than
> > creating
> > fresh, content.
> > On Fri, May 24, 2019 at 5:26 AM Ben Cotton <bcotton(a)redhat.com>
> > wrote:
> > On Thu, May 23, 2019 at 6:58 AM Ankur Sinha <
> > sanjay.ankur(a)gmail.com>
> > >
> > > In posts related to tools, should we start including what
> > versions
> of the
> > > tools (and the Fedora release) the article refers to as a
> > way to
> > > users more aware? Would that work?
> > >
> > That's a great idea. Then at least people have some context
> > clues to
> > figure out if the post is out of date or not.
> Is this doable, though?
> Ankur Sinha "FranciscoD"
> Time zone: Europe/London
> Fedora Magazine mailing list -- magazine(a)lists.fedoraproject.org
> To unsubscribe send an email to
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines:
> List Archives:
Fedora Magazine mailing list -- magazine(a)lists.fedoraproject.org
To unsubscribe send an email to
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html