Greetings!
First off, I would like to propose changing this list to be like
all the other Apache mailing lists by attaching a 'reply-to'
field to the headers. That way, when someone replies to a message
sent to the list, the reply will go to the list as well. I'll
do this in a couple of days if no-one has any objection.
Next:
As you probably could tell from the recent spate of commit messages,
the Apache HTTP Server documentation project is open for business.
The documentation has been split off from the source code tree
so people can work on it without having to have access to the
code. (People doing translations, or cleaning up the prose,
for instance.)
A number of people expressed interest in working on the
documentation, either because that's where their skills
lay, or they had an itch they wanted to scratch, or they wanted
to contribute to the Apache project and didn't feel comfortable
working on the code.
Well, here's your opportunity. :-)
You can get the documentation source files from the Sourcery.Org
site (among others). Use cvs:
cvs -d :pserver:anoncvs@CVS.Sourcery.Org:/cvs/apache login
(password is "anoncvs")
cvs -d :pserver:anoncvs@CVS.Sourcery.Org:/cvs/apache co httpd-docs-1.3
(or httpd-docs-2.0 if you want to work with the 2.0 documentation)
Go ahead and make changes to your copies, and then propose them
by generating a diff and sending it to this mailing list
(apache-docs@apache.org) with a subject beginning with "[PATCH]".
For instance, "[PATCH] Spelling correction for index.html.po".
Generate the patch with
cvs diff -u index.html.po
(or whatever the changed file is), and send the resulting output.
Commit access to the documentation will be handed out fairly
readily, once people have shown they know what they're up to.
--
#ken P-)}
Ken Coar <http://Golux.Com/coar/>
Apache Software Foundation <http://www.apache.org/>
"Apache Server for Dummies" <http://Apache-Server.Com/>
"Apache Server Unleashed" <http://ApacheUnleashed.Com/>
First off, I would like to propose changing this list to be like
all the other Apache mailing lists by attaching a 'reply-to'
field to the headers. That way, when someone replies to a message
sent to the list, the reply will go to the list as well. I'll
do this in a couple of days if no-one has any objection.
Next:
As you probably could tell from the recent spate of commit messages,
the Apache HTTP Server documentation project is open for business.
The documentation has been split off from the source code tree
so people can work on it without having to have access to the
code. (People doing translations, or cleaning up the prose,
for instance.)
A number of people expressed interest in working on the
documentation, either because that's where their skills
lay, or they had an itch they wanted to scratch, or they wanted
to contribute to the Apache project and didn't feel comfortable
working on the code.
Well, here's your opportunity. :-)
You can get the documentation source files from the Sourcery.Org
site (among others). Use cvs:
cvs -d :pserver:anoncvs@CVS.Sourcery.Org:/cvs/apache login
(password is "anoncvs")
cvs -d :pserver:anoncvs@CVS.Sourcery.Org:/cvs/apache co httpd-docs-1.3
(or httpd-docs-2.0 if you want to work with the 2.0 documentation)
Go ahead and make changes to your copies, and then propose them
by generating a diff and sending it to this mailing list
(apache-docs@apache.org) with a subject beginning with "[PATCH]".
For instance, "[PATCH] Spelling correction for index.html.po".
Generate the patch with
cvs diff -u index.html.po
(or whatever the changed file is), and send the resulting output.
Commit access to the documentation will be handed out fairly
readily, once people have shown they know what they're up to.
--
#ken P-)}
Ken Coar <http://Golux.Com/coar/>
Apache Software Foundation <http://www.apache.org/>
"Apache Server for Dummies" <http://Apache-Server.Com/>
"Apache Server Unleashed" <http://ApacheUnleashed.Com/>