I would have no issue manually doing this, but the problem is as soon as I do, every page will automatically be updated to today's date with my name as soon as I hit "Save." So a bot might be good. Or a template change.
BKP ----- Original Message ----- > From: "Sandro Bonazzola" <[email protected]> > To: "Dave Neary" <[email protected]>, "Bob Doolittle" <[email protected]>, > "users" <[email protected]> > Sent: Monday, March 17, 2014 8:03:23 AM > Subject: Re: [Users] Request for Wiki - dates > > Il 14/03/2014 18:16, Dave Neary ha scritto: > > Hi Bob, > > > > What I'd love to see is a way for people to flag content out-of-date. > > "Last updated" doesn't tell you about the feature that is stable and > > unchanged since 3.0, nor does it tell you that the feature is in > > constant flux and the latest commit just changed everything. > > > > You need 2 dates for maximum usefulness: "Last updated", and "Flagged > > out of date" - if last updated is after the flagged date, something is > > wrong (flag should have been removed). If the flag is there then the > > page needs updating. Ideally, flagging the page would indicate the > > reason for the flag. > > > > Anyone know how you'd do this in a maintainable way in MediaWiki? > > Looking at mediawiki the only way I see is flagging all pages not updated in > the last month with > > http://www.mediawiki.org/wiki/Template:Outdated > > And having people to review them. > I'm not sure if a bot can do the work of automatically flagging all pages not > updated. > > > > > > > Cheers, > > Dave. > > > > On 03/13/2014 05:53 PM, Bob Doolittle wrote: > >> Hi, > >> > >> As most are aware, there's a lot of information on the Ovirt Wiki that's > >> out of date. In spite of our best efforts, that will probably always be > >> true - it's the nature of Wikis. > >> > >> When I look for information on our Wiki, I never know where the most > >> current information is. > >> > >> I think it would be really helpful if someplace on each Wiki page was a > >> useful date to let us know the currency of the info. Probably the most > >> useful date is last-modified, although creation date might also be > >> useful. Maybe we could even map/display the date to the version number > >> of whatever the current stable release was at the time for context > >> (sometimes the content of a page calls out a particular version it's > >> addressing, but a lot of the time it does not). > >> > >> Just as an example, I want to find out about migrating my existing > >> configuration to self-hosted, using 3.4 RC2. A google search shows the > >> following links (in order shown): > >> > >> http://www.ovirt.org/Features/Self_Hosted_Engine > >> http://www.ovirt.org/Migrate_to_Hosted_Engine > >> http://www.ovirt.org/Hosted_Engine_Howto > >> ... > >> > >> I'm sure the Features page is ancient at this point. It's hard to tell > >> about the 2nd page. > >> > >> Of course the date a page was last modified doesn't directly indicate > >> how correct/current the information is, but there's a correlation. > >> Knowing the date would be useful in making a judgment. It might even > >> help the task of identifying and cleaning up obsolete pages. > >> > >> Easy to do? > >> > >> -Bob > >> > >> _______________________________________________ > >> Users mailing list > >> [email protected] > >> http://lists.ovirt.org/mailman/listinfo/users > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
