Re: CVS changes

> > >> Not everyone has sgml tools on their local machine, do they?
> > > But everyone committing changes to docs does, or should have, sgml tools
> > > on *their* machines. Right??
> > I think it's a bad idea to create such a policy; anything we do that
> > raises the bar for docs contributions will just mean that we have less
> > and worse documentation. Hasn't our past policy always been "submit
> > whatever you want, even plain text, and we'll fix the markup later"?

Certainly! I've never said otherwise, didn't suggest a change in policy,
and have always been committed to *doing* the markup to make the former
"submit anything" happen. If the docs are broken for a while, or if we
have to work on the submitted patches before committing them, then we
should do that.

But docs don't magically happen without someone babysitting them at
least a little; I know that from experience and I know that Peter and
others have done a lot of work to make this happen too.

Right now, folks are seeing that docs are not getting built, and are
heading off in several directions. I *thought* I've been paying
attention (but have been very busy so could have missed it) and I *know*
that lots of work is being done on the web site, things are being
rearranged etc etc but for those of us who are peripherally involved
with pieces of the web site it would be *really* helpful to know what is
planned, where things are going to go, when it might happen, etc etc.

I would like to resolve the 12 hour lag for CVSup and anoncvs service,
and frankly until that is resolved we should accept that we have a 12
hour turnaround on most changes. Coincidentally, that is the rate at
which the docs are (or would be, if I could figure out where they should
go) currently built.

Let's stop trying to each build a new wheel; we have plenty enough
already. There are fundamental breakages in the current servers, and
until those are resolve I'm not happy that we are changing web site info
etc to suggest workarounds as permanent solutions.

all imho of course ;)

- Thomas