wiki: Revision History & and periodical freezes
Subject:
Re: [wiki] Revision History & and periodical freezes
From:
"Robert Spencer" ####@####.####
Date:
27 Aug 2008 19:13:13 +0100
Message-Id: <8b8c4c740808271113l64ff1c99s57b4514c287ddf7a@mail.gmail.com>
On 8/27/08, jdd ####@####.#### wrote:
> Hello :-)
Hi jdd,
> HOWTOs need a "revision history tag". However, now we have a wiki, so
> revision are to be done each minute or so, and it's not usefull to add
> a revision history line for each typo edited.
It depends on the type of revision tag.
> I'm very gratefull to the people who took the time to correct my typos
> and ortograph mistakes (too many :-(), but we must take into account
> the *readers* needs. Wiki already have an history of the work (see
> info) and the last modified date (bottom of each page).
>
> So I propose we only add a revision history line when the author feels
> it's necessary. At least when making static pages from wiki.
That's not very user friendly, when you Google for a howto/guide you
normally get multiple hits and only spend a few seconds deciding which
one to read -- the revision number at the top of the page is normally
the clincher.
> Of course this is to be discussed ! when anybody could give advice,
> the result will be written to the author's page.
We need a visible revision number, I suggest going over to date based
revision numbers and finding some way to get moin to add it near the
top -- the bottom is to far away.
We also need to get a style for moin that doesn't display the path
name so prominently, that way we can have pages names that are the
same as on the main site and full titles. This will also make
automatic document retrieval easier to script.
> In fact we should discuss on the way how will the relation from the
> wiki and the static mirrored site setup.
I'm still struggling with that, I was hoping to find a 1:1
relationship between wiki and site, but due to limitations in wiki
design that isn't possible.
> That mean, when, how and why should we "freeze" the wiki. Remember,
> it's necessary to mirror the HOWTOs and include then into
> distributions or other CDs
Why, we haven't had scheduled freezes before? That's a job for the
distributer and not one we necessary need worry about.
> I see several way to do so, very different in scope:
>
> * do this each quarter. Each quarter (January, April...), the wiki
> will be freezed, that is only the registered Authors can write and
> only to they own HOWTO. After, say, 15 days, all the HOWTOs are copied
> to dockbook and to the static web site.
>
> -> pretty hard to manage, I guess, but distros work like that
We're not a distro. They do things like that for reason's that don't
apply to us.
> * manage the ACL's of moin to allow the author of a HOWTO to freeze
> his HOWTO at will. When the author is happy of the result, he mails
> the discuss list, add a "to be stored" tag to his howto and copy the
> page to a new wiki page for editing again. (or the other way round)
>
> ->more author friendly, but need some work from the author. more like
> the present management
"The present management" setup is not efficient, please leave the wiki
to do what wiki's do best and handle freezes in CVS.
> * ??? any other idea??
Yes, please don't have everything revolve around author co-operation,
they have let us down in the past and that's mostly because we aren't
thinking like a library.
The LDP is a library and should be run as one, many of our problems
would be reduced if we did and we would be offering a better service
to the community that way.
--
Robert Spencer
