On Wed, May 22, 2019 16:59:36 -0400, Ben Cotton wrote:
On Tue, May 21, 2019 at 5:35 PM Ankur Sinha
> Maybe something like this plugin that marks posts as outdated after a
> while? One release cycle maybe, given that most posts on tooling apply
> to current releases and we simply don't have the man power to keep all
> old posts up to date?
I'm not sure I'd want to automatically mark posts more than one
release cycle old as outdated. I wouldn't want to send someone away
unnecessarily. At least when things are outdated, it should be more
obvious (e.g. commands will fail or not exist), whereas if something
is falsely marked as outdated, no one will know.
+1 I was working on the general assumption that with the development
pace in Fedora, information is likely to get outdated every release or
two---but this isn't necessary.
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?
Maybe we can have a flag that we set on posts when someone reports
outdated post and just have a footer that gives readers instructions
on how to report that?
One caveat: I don't think authors can edit articles after they've been
published. So, the editors will have to do it.
Alternatively, and I'm not sure how much of a burden this would
but we could automatically email authors at each release cycle and ask
them to verify that their posts are still valid and if not either
update or apply this hypothetical "outdated" flag.
I don't know how well this will work in our community where people tend
to move on to other things, sometimes other communities. Additionally,
it has the same issue as the previous one---the editing team will have
to do more work, even if it is temporarily providing access to the
authors to edit posts.
> Also an issue on docs, by the way:
> We had someone following F14 documentation asking questions on AskFedora
> the other day---mostly why official documentation doesn't work.
Ugh. I like your proposal in that ticket. That's a slightly different
approach since, in theory, we're branching the docs for each release
anyway, so the latest version should exist and we can point people to
it, even if the old docs are still valid. That's not the case for
Yes, not explicitly, but each post that is published really refers to
the state of things at that point in time.
It's a general issue that, for example, news agencies are also grappling
with. Here's an example of The Guardian now marking their posts to make
it clearer to readers: https://www.bbc.co.uk/news/technology-47799878
Ankur Sinha "FranciscoD"
Time zone: Europe/London