You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "Roy T. Fielding" <fi...@liege.ICS.UCI.EDU> on 1997/01/28 03:47:02 UTC

Re: [PATCH] update docs with fin_wait_2 webpage

We actually do have guidelines on documentation, and they are indeed
different from our code voting rules.  Basically, unless you are
writing something that says "this is the opinion of the Apache Group",
then go ahead and commit it.  It is incumbent on anyone who thinks
the documentation is wrong to either fix it or provide the words for
you to fix it.

I say go ahead and commit your update.  I have a few things I'd like
to flesh-out regarding my part of it, but I can do that easier after
you commit it.

.....Roy

Re: [PATCH] update docs with fin_wait_2 webpage

Posted by Alexei Kosut <ak...@nueva.pvt.k12.ca.us>.
On Mon, 27 Jan 1997, Marc Slemko wrote:

> How and how often is documentation updated on the web from the CVS
> repository?

It isn't. Do it manually; log onto taz, go to /export/pub/apache/docs,
and type "cvs update". The reason for this is so we can sync
documentation to releases. For example, if we have docs for 2.0 in
CVS, but 2.0 won't be released (even as a beta) for months yet, we
don't want the 2.0 docs on the web site, we want the 1.2 docs.

-- 
________________________________________________________________________
Alexei Kosut <ak...@nueva.pvt.k12.ca.us>      The Apache HTTP Server
URL: http://www.nueva.pvt.k12.ca.us/~akosut/   http://www.apache.org/


Re: [PATCH] update docs with fin_wait_2 webpage

Posted by Marc Slemko <ma...@znep.com>.
How and how often is documentation updated on the web from the CVS
repository?

On Mon, 27 Jan 1997, Roy T. Fielding wrote:

> We actually do have guidelines on documentation, and they are indeed
> different from our code voting rules.  Basically, unless you are
> writing something that says "this is the opinion of the Apache Group",
> then go ahead and commit it.  It is incumbent on anyone who thinks
> the documentation is wrong to either fix it or provide the words for
> you to fix it.
> 
> I say go ahead and commit your update.  I have a few things I'd like
> to flesh-out regarding my part of it, but I can do that easier after
> you commit it.

I figured you may want to do that.  I just trimmed the headers, you can do
whatever...