[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: concerning debian-reference and the necessity for the competitors

On Tue, Feb 25, 2003 at 06:09:39PM -0800, Osamu Aoki wrote:
> Hi, (I CCed folks affected by the Adam's posting in debian-doc, if you
> are subscribed, please tell us so.)
> > * system-administrator
> > 
> > Seems to overlap with debian-reference, only had two content commits
> > in 2002, and only a translation was adding all of 2001.  Probably has
> > some contents which could be integrated in debian-reference.
> The current maintainer (Tapio Lehtonen) wishes to keep it and want to
> grow document by the contribution from others.  My observation is that
> it has not work yet. He is DD.
> I also invited him to work together into "Debian Reference" long time
> ago.  He was not interested and wanted to keep working on his documents.
> That is my side of story.
> Can we hear from you, Tapio?

Seems the approach taken to get the manuals written, i.e. getting a
person to write one chapter on his/her expertice area does not work. I
originally agreed with the then maintainer of Sys Admin Manual to
write the chapter on "Time". I then wrote also the Backups
-chapter. No other chapters have been written, and it has been several
years now, so we can conclude that the manual is not going to be

I do think that a Debian System Administrator Manual is needed, but it
makes no difference in what manual the information is. If some other
manual is more attractive to prospective authors the usable parts of
the current Sys Admin Manual can be moved there.

I noticed the specification of less than 300 pages per manual. This
may be difficult to achieve if Sys Adm Manual is included with other
manuals, Sys Adm Manual could alone be under 300 pages but not with
other content added. Anyway, it seemed logical to have a separate
manuals for administrators and users.

To solve the Debian Documentation Problem:

The maintainer of a package should be responsible to notify the
documentation maintainers that a documentation change/addition is

For example, the last change I did to the Time chapter is there
because by chance I happened to notice discussion on that in irc or
mailing list, I forget which, and knew to add the info on changed
behaviour. There may be other things that are no longer accurate, but
I'm not going to wade through all change logs every month to find

Tapio Lehtonen
GPG public key from http://www.iki.fi/Tapio.Lehtonen

Attachment: pgpj4yOTDIe80.pgp
Description: PGP signature

Reply to: