If you'd like to become an active contributor to the Apache project (the
group of volunteers who vote on changes to the distributed server), then
-you need to start by subscribing to the new-httpd@apache.org mailing list.
+you need to start by subscribing to the dev@httpd.apache.org mailing list.
One warning though: traffic is high, 1000 to 1500 messages/month.
-To subscribe to the list, send "subscribe new-httpd" in the body of
-a message to <majordomo@apache.org>. We recommend reading the list for
-a while before trying to jump in to development.
+To subscribe to the list, send "subscribe dev" in the body of
+a message to <dev-subscribe@httpd.apache.org>. We recommend reading the
+list for a while before trying to jump in to development.
- NOTE: The developer mailing list (new-httpd@apache.org) is not
+ NOTE: The developer mailing list (dev@httpd.apache.org) is not
a user support forum; it is for people actively working on development
of the server code and documentation, and for planning future
directions. If you have user/configuration questions, send them
<!--#include virtual="header.html" -->
<H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
<P>
- $Revision: 1.7 $ ($Date: 2001/03/28 21:26:29 $)
+ $Revision: 1.8 $ ($Date: 2001/08/22 18:23:09 $)
</P>
<P>
The latest version of this FAQ is always available from the main
</P>
<P>
In general, the first course of action is to be a member of the
- <SAMP>new-httpd@apache.org</SAMP> mailing list. This indicates to
+ <SAMP>dev@httpd.apache.org</SAMP> mailing list. This indicates to
the Group that you are closely following the latest Apache
developments. Your patch file should be generated using either
'<CODE>diff -c</CODE>' or '<CODE>diff -u</CODE>' against
the latest CVS tree. To submit your patch, send email to
- <SAMP>new-httpd@apache.org</SAMP> with a <SAMP>Subject:</SAMP> line
+ <SAMP>dev@httpd.apache.org</SAMP> with a <SAMP>Subject:</SAMP> line
that starts with <SAMP>[PATCH]</SAMP> and includes a general
description of the patch. In the body of the message, the patch
should be clearly described and then included at the end of the