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 / news
source, not documentation.
The target audience of the magazine does not make this distinction. I
wish they did, but it appears that as far as they are concerned, they
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 read
them, they ask why documented information does not work:
https://ask.fedoraproject.org/t/dhcp-does-not-recognise-mac-address-of-in...
As you,'ll see there, this led me to file this ticket with docs:
https://pagure.io/fedora-docs/docs-fp-o/issue/116
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:
https://fedoramagazine.org/fedora-28-end-of-life/
While this would be something nice to have, IMHO keeping old
articles
up-to-date should definitely have a much lower priority than creating new,
fresh, content.
Sure.
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> wrote:
>
> 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 make
> 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?
--
Thanks,
Regards,
Ankur Sinha "FranciscoD"
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London