Return-Path: Delivered-To: apmail-httpd-cvs-archive@www.apache.org Received: (qmail 39976 invoked from network); 17 Jan 2006 18:38:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Jan 2006 18:38:15 -0000 Received: (qmail 70052 invoked by uid 500); 17 Jan 2006 18:38:13 -0000 Delivered-To: apmail-httpd-cvs-archive@httpd.apache.org Received: (qmail 70033 invoked by uid 500); 17 Jan 2006 18:38:13 -0000 Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list cvs@httpd.apache.org Received: (qmail 70022 invoked by uid 99); 17 Jan 2006 18:38:13 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jan 2006 10:38:13 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 17 Jan 2006 10:38:11 -0800 Received: (qmail 39764 invoked by uid 65534); 17 Jan 2006 18:37:50 -0000 Message-ID: <20060117183750.39760.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r369861 - in /httpd/site/trunk/docs: ./ docs-project/ Date: Tue, 17 Jan 2006 18:37:45 -0000 To: cvs@httpd.apache.org From: noirin@apache.org X-Mailer: svnmailer-1.0.5 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Author: noirin Date: Tue Jan 17 10:37:36 2006 New Revision: 369861 URL: http://svn.apache.org/viewcvs?rev=369861&view=rev Log: Update of transforms Modified: httpd/site/trunk/docs/ABOUT_APACHE.html httpd/site/trunk/docs/bug_report.html httpd/site/trunk/docs/docs-project/docsformat.html httpd/site/trunk/docs/docs-project/index.html httpd/site/trunk/docs/docs-project/translations.html httpd/site/trunk/docs/download.html httpd/site/trunk/docs/index.html httpd/site/trunk/docs/lists.html httpd/site/trunk/docs/related_projects.html httpd/site/trunk/docs/usersdelist.html httpd/site/trunk/docs/userslist.html Modified: httpd/site/trunk/docs/ABOUT_APACHE.html URL: http://svn.apache.org/viewcvs/httpd/site/trunk/docs/ABOUT_APACHE.html?rev=369861&r1=369860&r2=369861&view=diff ============================================================================== --- httpd/site/trunk/docs/ABOUT_APACHE.html (original) +++ httpd/site/trunk/docs/ABOUT_APACHE.html Tue Jan 17 10:37:36 2006 @@ -179,7 +179,7 @@

If you just want to send in an occasional suggestion/fix, then you can -just use the bug reporting form at +simply use the bug reporting form at <http://httpd.apache.org/bug_report.html>. You can also subscribe to the announcements mailing list (announce@httpd.apache.org) which we use to @@ -211,22 +211,22 @@

-

There is a core group of contributors, formed from the project -founders, which is augmented from time to time with the outstanding +

There is a core group of contributors, formed initially of the project +founders, and augmented from time to time by other outstanding contributors. There are 'committers', who are granted access to the source code control respositories to help maintain the project or docs, -and the core group now managing the project is called the Apache HTTP +and the core group now managing the project, which is called the Apache HTTP Project Management Committee (PMC, for short). In fact, each Apache -Software Foundation project has its own PMC to determine committers, +Software Foundation project has its own PMC, to determine committers, project direction and overall management. The terms "The Apache Group" or "Apache Core" are no longer used.

The project is a meritocracy -- the more work you have done, the more -you are allowed to do. The group founders set the original rules, but +you will be allowed to do. The group founders set the original rules, but they can be changed by vote of the active PMC members. There is a group of people who have logins on our server and access to the source code repositories. Everyone has read-only access to the repositories. Changes to the code are proposed on the mailing list and usually voted on by active -members -- three +1 (yes votes) and no -1 (no votes, or vetoes) are needed +members -- three +1 ('yes' votes) and no -1 ('no' votes, or vetoes) are needed to commit a code change during a release cycle; docs are usually committed first and then changed as needed, with conflicts resolved by majority vote.

@@ -238,10 +238,10 @@ communicated using a patch (output of a unified "diff -u oldfile newfile" command), and then applied to the source code control repositories by one of the committers. -Anyone on the mailing list can vote on a particular issue, but we only -count those made by active members or people who are known to be experts -on that part of the server. Vetoes must be accompanied by a convincing -technical justification.

+Anyone on the mailing list can vote on a particular issue, but only those made +by active members or people who are known to be experts on that part of the +server are counted towards the requirements for committing. Vetoes must be +accompanied by a convincing technical justification.

New members of the Apache HTTP Project Management Committee are added when a frequent contributor is nominated by one member and unanimously approved by the voting members. In most cases, this "new" member @@ -265,30 +265,30 @@

Apache Software exists to provide robust and commercial-grade reference implementations of many types of software. It must remain a platform upon which individuals and institutions can build reliable systems, both for -experimental purposes and for mission-critical purposes. We believe the -tools of online publishing should be in the hands of everyone, and -software companies should make their money providing value-added services +experimental purposes and for mission-critical purposes. We believe that the +tools of online publishing should be in the hands of everyone, and that +software companies should make their money by providing value-added services such as specialized modules and support, amongst other things. We realize that it is often seen as an economic advantage for one company to -"own" a market - in the software industry that means to control -tightly a particular conduit such that all others must pay. This is +"own" a market - in the software industry, that means to control +tightly a particular conduit such that all others must pay for its use. This is typically done by "owning" the protocols through which companies conduct business, at the expense of all those other companies. To the extent that the protocols of the World Wide Web remain "unowned" by a single company, the Web will remain a level playing field for companies large and small. Thus, "ownership" -of the protocols must be prevented, and the existence of a robust reference +of the protocols must be prevented. To this end, the existence of robust reference implementations of various protocols and application programming interfaces, available free to all companies and individuals, is a tremendously good thing.

Furthermore, the Apache Software Foundation is an organic entity; those -who benefit from this software by using it often contribute back to it by +who benefit from this software by using it, often contribute back to it by providing feature enhancements, bug fixes, and support for others in public -lists and newsgroups. The amount of effort expended by any particular +lists and newsgroups. The effort expended by any particular individual is usually fairly light, but the resulting product is made very strong. These kinds of communities can only happen with freely available -software -- when someone pays for software, they usually aren't willing to -fix its bugs. One can argue, then, that Apache's strength comes from the +software -- when someone has paid for software, they usually aren't willing to +fix its bugs for free. One can argue, then, that Apache's strength comes from the fact that it's free, and if it were made "not free" it would suffer tremendously, even if that money were spent on a real development team.

@@ -298,10 +298,10 @@ could afford commercial software, and would pay for it without blinking, might get a "free ride" by using Apache. We are even happy when some commercial software companies completely drop their own HTTP server -development plans and used Apache as a base, with the proper attributions +development plans and use Apache as a base, with the proper attributions as described in the LICENSE. -That is to say, Apache HTTP Sever only comes from the Apache Software -Foundation, although many vendors ship their own product "based on the +That is to say, the Apache HTTP Sever only comes from the Apache Software +Foundation, but many vendors ship their own product "based on the Apache {Project}". There is no "{Vendor} Apache {Product}", this is an abuse of the Apache Software Foundation's marks.

Modified: httpd/site/trunk/docs/bug_report.html URL: http://svn.apache.org/viewcvs/httpd/site/trunk/docs/bug_report.html?rev=369861&r1=369860&r2=369861&view=diff ============================================================================== --- httpd/site/trunk/docs/bug_report.html (original) +++ httpd/site/trunk/docs/bug_report.html Tue Jan 17 10:37:36 2006 @@ -68,7 +68,7 @@
-Reports of security issues should not be reported here. +Reports of security issues should not be made here. Please see the security report page if you have concerns or think you have discovered a security hole in the Apache Web server software. @@ -89,7 +89,7 @@ no other patches (so that we can make sure it's an Apache bug and not a bug in a module or patch provided by someone else). It is frustrating to take time and effort to track down a problem only - to figure out it caused by a broken third party module. + to figure out that it is caused by a broken third party module.
  • Looked at the error log. Please include any related messages in your report, or state that there are none. @@ -115,24 +115,24 @@
    -

    Unless you are sure you have found a bug in the Apache HTTP +

    Unless you are sure that you have found a bug in the Apache HTTP Server, we strongly recommend that you try the Apache HTTP Server Users List before using the bug database. If you don't receive a response within a few days, then please submit it to the Apache bug database. If it's a known issue, you'll probably get a faster response from the mailing list and you will help keep developer time free for improving Apache. Most bug reports submitted are actually user configuration - problems that could be easily fixed by asking in the mailing + problems that could be easily fixed by asking on the mailing list.

    Do not post to the mailing list and submit a bug report at the same time. This wastes everyone's time. - Post to the mailing list and wait a few days. + Post to the mailing list and wait a few days before submitting a bug report.

    If you have done all of the preceding, then please select the button -below and fill out the form, and we will respond to it as soon as we can. +below and fill out the form. We will respond to it as soon as we can.

    @@ -169,46 +170,46 @@
    @@ -148,7 +148,7 @@ sites now says 'It Worked! Apache is installed!' -- then contact the mail originator or the Web site's Webmaster directly, because they're just using our software and we have nothing to do with them. Don't - waste your time or ours by telling us about it. + waste your time, or ours, by telling us about it. Modified: httpd/site/trunk/docs/docs-project/docsformat.html URL: http://svn.apache.org/viewcvs/httpd/site/trunk/docs/docs-project/docsformat.html?rev=369861&r1=369860&r2=369861&view=diff ============================================================================== --- httpd/site/trunk/docs/docs-project/docsformat.html (original) +++ httpd/site/trunk/docs/docs-project/docsformat.html Tue Jan 17 10:37:36 2006 @@ -85,7 +85,7 @@ is also available in mod_template.txt. Obviously, the file extension should be xml. It was changed to make online viewing simpler.

    -

    To assure that your documentation follows the defined format, you +

    To ensure that your documentation follows the defined format, you should parse it using the DTD. Some help using Emacs with XML files is available from IBM developerWorks.

    @@ -100,23 +100,24 @@
    -

    The easiest way to view the tranformed docs is simply to open the +

    The easiest way to view the tranformed docs is to simply open the xml file directly in a recent verions of MSIE, Netscape, or Mozilla. -(MSIE 6 seems to work consistently. Some people have had luck with -Netscape 6+ and Mozilla, but others have not.) These browsers +(MSIE 6 seems to work consistently. Some people have had luck with +Netscape 6+ and Mozilla, but others have not.) These browsers will read the xsl file and perform the transformation for you -automatically, so you can see what the final output will look like. +automatically, so that you can see what the final output will look like. This means that you can work on the docs and check your work without any special transformation setup.

    For the final presentation, it is still necessary to transform to -html to accomodate older browsers. Although any standards-compliant +html to accomodate older browsers. Although any standards-compliant xslt engine should do, changing engines can lead to massive diffs on -the transformed files. Therefore, we have chosen a single recommended -transformation system based on Xalan+Xerces Java and Ant. These are +the transformed files. Therefore, we have chosen a single recommended +transformation system based on Xalan+Xerces Java and Ant. These are all Apache projects distributed under the Apache license.

    -

    The only requirement to do the transformation is a Java 1.2 or -greater JVM (which can be obtained free from Sun). Assuming you -already have httpd/httpd/branches/2.0.x/docs/ checked out from SVN, +

    The only prerequisite for the transformation is a Java 1.2 or +greater JVM (which can be obtained free from Sun). Assuming you +already have httpd/httpd/branches/2.0.x/docs/ (or the equivalent from another branch) +checked out from SVN, here is what you need to do to build: (If you need instructions on setting up SVN, see this page.)

    @@ -126,7 +127,7 @@ $ ./build.sh

    If you are running under win32, the build.sh script will work if -cygwin is installed. Alternatively, on Win32, you should be +cygwin is installed. Alternatively, on Win32, you should be able to run the build.bat script.

    If you don't want to get the build files from SVN, you can download a pkzipped version of the current build tools from our distribution @@ -155,7 +156,7 @@ accompanying metafile (newfilename.xml.meta). Since these tasks are written in perl, you'll need a working perl installation for this. If not, you should take these steps -manually or just drop a note onto the project mailing list that someone else +manually, or just leave a note on the project mailing list so that someone else can do it.

    The PDF version of the docs is generated by transforming the xml -files to LaTeX using the "latex-en" Ant target. The XSLT style files -for the transformation are under style/latex/. Once you +files to LaTeX using the "latex-en" Ant target. The XSLT style files +for the transformation are under style/latex/. Once you have the .tex equivalent of each .xml file, you can use pdflatex to convert this into a pdf file. Recommended versions of pdflatex can be obtained as part of TeTeX (unix) or MikTeX (win32), but any version of TeX should be fine, as -long as it is sufficiently complete and modern. To generate the PDF, +long as it is sufficiently complete and modern. To generate the PDF, you should process the sitemap.tex file, which contains the main LaTeX document code and will include all the other files. The outputed PDF will then be called sitemap.pdf, which you can rename how you choose.

    Some notes about the XML to LaTeX conversion are necessary. Although HTML and LaTeX have many similarities, there are enough -differences between the two to make targeting both outputs a difficult -proposition. In particular, the method of handling tables is very -different. To aid LaTeX in understanding tables designed for HTML, a +differences between the two to make targetting both outputs a difficult +task. In particular, the methods for handling tables are very +different. To aid in the conversion to LaTeX of tables designed for HTML, a <columnspec> section should be added to each table. Inside the <columnspec>, place a <column width=".xx"/> for each column in the table, where xx is the percentage of the line-width devoted to that -column. This will let the conversion handle basic tables. More -complex stuff (like spanning rows or columns) will not work.

    -

    In addition, pdflatex does not know how to incorporate -GIF files. So any graphics must be available in PNG format.

    +column. This will assist in the conversion of basic tables. More +complex stuff (like spanning rows or columns) is not currently convertible.

    +

    Further, pdflatex cannot incorporate +GIF files in a generated PDF, so any graphics must be available in PNG format.

    There are various other restrictive assumptions embedded in the XSLT that work for the current docs, but may need to be -modified in the future. For example, the code that transforms -HTML-style links to LaTeX cross-references will work only with the -main directory and one level of subdirectory. Also, -<pre> sections are very likely not to work well +modified in the future. For example, the code that transforms +HTML-style links to LaTeX cross-references will only work within the +main directory and one level of subdirectory. Also, +<pre> sections rarely work well in LaTeX because of differences in escaping and formatting rules in verbatim sections.

    Finally, there are various differences in escaping rules between -XML/HTML and LaTeX. Some characters need to be backslash-escaped in +XML/HTML and LaTeX. Some characters need to be backslash-escaped in LaTeX, and all XML entitites (&whatever;) must be converted to -LaTeX equivalents. This is currently handled for a limitted set of -characters using a big ugly search-replace in the XSLT. But this may +LaTeX equivalents. This is currently handled for a limited set of +characters using a big, ugly search-replace in the XSLT. This may need to be modified in the future, especially to handle translations. -Perhaps pre-processing with a perl script and a substitution table -would be better.

    +Pre-processing with a perl script and a substitution table +may be a better solution.

    Modified: httpd/site/trunk/docs/docs-project/index.html URL: http://svn.apache.org/viewcvs/httpd/site/trunk/docs/docs-project/index.html?rev=369861&r1=369860&r2=369861&view=diff ============================================================================== --- httpd/site/trunk/docs/docs-project/index.html (original) +++ httpd/site/trunk/docs/docs-project/index.html Tue Jan 17 10:37:36 2006 @@ -71,7 +71,7 @@ Version 2.2 | Current

    Downloadable documentation in Microsoft Help (CHM) and PDF -versions are available from our distribution mirrors.

    +formats are available from our distribution mirrors.

    The Documentation Project is an effort to maintain and improve the quality of the documentation included with the Apache HTTP Server. Participation is open to anyone with a little time, a little knowledge @@ -97,7 +97,7 @@ without becoming involved in the documentation project, you can submit it to the bug database.

    There are lots of ways to contribute to the documentation -project, including fixing a few typos and spelling mistakes, +project, including fixing typos and spelling mistakes, translating the documentation into other languages, writing tutorials to help new users, or just expressing your opinion about suggested changes.

    @@ -106,7 +106,7 @@ docs-subscribe@httpd.apache.org. For details on how to contribute, the best place to start is Ken Coar's Documentation Project Tutorial.

    -

    For information on our project to use XML in the documentation, see +

    For information on our use of XML in the documentation, see our Documentation Format and Transformation page.

    @@ -136,7 +136,7 @@

    Some of the participants are:

    • Erik Abele
      • -
    • Ryan Bloom
      • +
    • Ryan Bloom
    • Rich Bowen
    • Ken Coar
    • Eric Cholet
      • @@ -145,6 +145,7 @@
    • Astrid Keßler
    • André L. Malo
    • Chris Pepper
      • +
    • Noirin Plunkett
    • William A. Rowe, Jr.
    • Joshua Slive
    • Mads Toftum
      • Modified: httpd/site/trunk/docs/docs-project/translations.html URL: http://svn.apache.org/viewcvs/httpd/site/trunk/docs/docs-project/translations.html?rev=369861&r1=369860&r2=369861&view=diff ============================================================================== --- httpd/site/trunk/docs/docs-project/translations.html (original) +++ httpd/site/trunk/docs/docs-project/translations.html Tue Jan 17 10:37:36 2006 @@ -68,10 +68,11 @@

      We encourage translations of the documentation into other languages. If you would like to assist in translating the -docs, please start by subscribing to the documentation project -mailing list. The documentation project participants are -usually very willing to help you sort out any questions or technical -difficulties that may arise in your work.

      +docs, please start by reading the general documentation project +information, and subscribing to the +documentation project mailing list. The documentation project participants are +usually very willing to help you with any questions or technical +difficulties that may arise during your work.

    • @@ -126,12 +127,12 @@
    • The Documentation Format and Transformation page gives some information about the -transformation from xml to html. Especially translations of the version 2.0 -documentation should be sent as xml file. Commiters should take -care of generating and commiting the corresponding html file.
      • +transformation from xml to html. Translations of documentation for Apache +version 2.0 and higher should be sent as xml file. Committers will take +care of generating and committing the corresponding html file.
    • The -Documentation Project Tutorial gives you a general overview about the -work with the documentation and how to send in new files and +Documentation Project Tutorial gives a general overview of the +documentation project, and how to send in new files and updates.
    @@ -147,15 +148,15 @@

    Because English is the main development language of the Apache HTTP Server, it is difficult for the developers to check the quality -of documentation submitted in other languages. For this reason, we +of documentation submitted in other languages. Therefore, we require that all translated documentation be reviewed by another -fluent speaker of the relevant language before they are accepted. +fluent speaker of the relevant language, before it can be accepted. Each commit message should list the reviewer. If the translator is not -the same as the commiter, the translator should be named in the commit -message too.

    +the same as the committer, the translator should also be named in the commit +message.

    We also encourage you to place the name of the translator in a comment at the top of the file, along with the CVS revision -number of the english-language document that you are translating. +number of the English-language document that you are translating. This should make it easier to determine when files need updating.

    Modified: httpd/site/trunk/docs/download.html URL: http://svn.apache.org/viewcvs/httpd/site/trunk/docs/download.html?rev=369861&r1=369860&r2=369861&view=diff ============================================================================== --- httpd/site/trunk/docs/download.html (original) +++ httpd/site/trunk/docs/download.html Tue Jan 17 10:37:36 2006 @@ -207,15 +207,15 @@ CVE-2004-0492 (cve.mitre.org).

    For additional details, read the Official Announcement.

    -

    The Apache 1.3 series is being actively maintained and leisurely -developed, to maintain stability. Releases will be made to address security issues, or after +

    The Apache 1.3 series is being actively maintained, and +developed at a leisurely pace, to maintain stability. Releases will be made to address security issues, or after a comfortable number of bug fixes or improvements have been made. -Significantly new features will more than likely not be added to 1.3 +Significantly new features are unlikely to be added to 1.3 in preference to 2.0, although important new features and enhancements will be seriously considered for inclusion in 1.3.

    Use the Apache 1.3.34 version if you need to use third party -modules that are not yet available as an Apache 2.0 module. Apache -1.3 is not compatibile with Apache 2.0 modules.

    +modules that are not yet available as an Apache 2.x module. Apache +1.3 is not compatibile with Apache 2.x modules.

    @@ -101,7 +101,7 @@

    -The announce@httpd.Apache.Org mailing list is used to announce +The announce@httpd.apache.org mailing list is used to announce major releases and other important information about the Apache HTTP Server project. Messages are posted only by the Foundation; there is no discussion. @@ -114,11 +114,15 @@ Subscription address: - announce-subscribe@httpd.Apache.Org + announce-subscribe@httpd.apache.org + + + Digest subscription address: + None. Unsubscription address: - announce-unsubscribe@httpd.Apache.Org + announce-unsubscribe@httpd.apache.org Getting help with the list: @@ -132,7 +136,7 @@

  • Raw gzipped mbox files
  • Mailing list archives at MARC
  • Available back to 27 October 1999. Send a message to - announce-help@httpd.Apache.Org for information about accessing + announce-help@httpd.apache.org for information about accessing the archives.
    • @@ -152,15 +156,15 @@

    The lists and discussion groups listed here are the only place that configuration and how-to questions belong, ever. Every day, users -become frustrated, not with Apache, but how nobody will help them understand +become frustrated, not with Apache, but with how nobody will help them understand how to get started. 95% of the time, it's not for lack of helpers, but for lack of effort and well stated questions.

    Before you go further, please read Eric S. Raymond and Rick Moen's explanation of "How To Ask -Questions The Smart Way". If you follow his advice, you will +Questions The Smart Way". If you follow their advice, you will discover that these forums have dozens of helpers ready to provide you with guidance on using the Apache HTTP Server! Note: Do not -sent your Apache questions to Eric himself!

    +sent your Apache questions to Eric or Rick!

    There are now a few Apache HTTP Server Users Mailing Lists available in different languages.

    They are described on separate pages:

    @@ -200,7 +204,7 @@ Configuration and support questions should be addressed to a user support group. This list is only for discussion of changes to the source code and related issues. -Other questions will likely be ignored. +Other questions are likely to be ignored. @@ -211,14 +215,14 @@ + (Not a user support list!) - + @@ -250,8 +254,8 @@
    Subscription address: dev-subscribe@httpd.apache.org - (No user support list!)
    Digest subscription address: dev-digest-subscribe@httpd.apache.org
    Unsubscription addresses:Unsubscription address: dev-unsubscribe@httpd.apache.org
    - Apache HTTP server bug reports -list + Apache HTTP Server Bug Reports +List
    @@ -262,7 +266,7 @@ message each time a report is added or modified.

    If you take ownership of bug by assigning it to yourself, please -remember to add this mailing list to the cc: list so that it continues +remember to add this mailing list to the cc: list so that the list continues to receive updates.

    @@ -364,17 +368,15 @@
    - HTTP Server Documentation Project + Apache HTTP Server Documentation Project

    This mailing list is used by the people working on improving and -translating the documentation of the Apache HTTP server. Messages -posted to it include both discussion messages from people, and -automatic source-change notifications of alterations applied to the -documentation sources. +translating the documentation of the Apache HTTP server. It is primarily +used for discussion of changes to the documentation.

    @@ -462,6 +464,10 @@ + + + + @@ -540,8 +546,8 @@
    packagers-subscribe@httpd.apache.org
    Digest subscription address:None.
    Unsubscription addresses: packagers-unsubscribe@apache.org
    - Proxy module rework discussion -list + Proxy Module Rework Discussion +List
    @@ -592,8 +598,8 @@
    - Mailing list for HTTP server -testers of release candidates + Mailing List for Testers of +Apache HTTP Server Release Candidates
    @@ -602,8 +608,8 @@ This mailing list is for folks who want to test out snapshots and release candidates of the current development trees. Reports of differences in behaviour between the latest public release and the latest development -snapshots are appreciated. This list is not for testing released versions, -people should continue to submit bug reports to the bugdb for problems that +snapshots are appreciated. This list is not for testing released versions - +you should continue to submit bug reports to the bugdb for problems that exist the final released versions.

    @@ -611,8 +617,8 @@ consideration as the 'next release', or when some major milestone in the development process has been achieved. Subscribers to this list are invited (and encouraged) to 'test-drive' these candidates just before they're -generally released, note these candidates are NOT yet -released and should not be carried on announcement channels, until the +generally released. Note these candidates are NOT yet +released, and should not be carried on announcement channels, until the testing is complete and they have been voted for release on the dev@ list.

    Modified: httpd/site/trunk/docs/related_projects.html URL: http://svn.apache.org/viewcvs/httpd/site/trunk/docs/related_projects.html?rev=369861&r1=369860&r2=369861&view=diff ============================================================================== --- httpd/site/trunk/docs/related_projects.html (original) +++ httpd/site/trunk/docs/related_projects.html Tue Jan 17 10:37:36 2006 @@ -134,9 +134,9 @@ The mod_ssl package is distributed as a source extension and set of patches for the Apache 1.3 webserver from outside -the United States. Inside the United States you are able to use it for +the United States. Inside the United States you may use it for non-commercial purposes for free if you use RSAREF (due to various patents). -Outside the United States you can use it for non-commercial and commercial +Outside the United States you may use it for both commercial and non-commercial purposes for free.

    @@ -151,7 +151,7 @@

    Apache Quick Reference Card

    -

    A compact, tri-fold double-sided page listing all major directives, +

    A compact, tri-fold, double-sided page listing all major directives, available at http://www.refcards.com/. A mod_perl refcard is also available. @@ -164,16 +164,16 @@ source code.

    The webserver is distributed with the full source code. Inside the -United States you are able to use it for non-commercial purposes for +United States you may use it for non-commercial purposes for free if you use RSAREF (due to various patents). Outside the United -States you can use it for non-commercial and commercial purposes for +States you may use it for both commercial and non-commercial purposes for free. -

    Inside the United States in order to use Apache with SSL commercially +

    If you wish to use Apache with SSL commercially, inside the United States, you may want to look at Stronghold or Raven. -Get Apache-SSL from here. +Apache-SSL is available here.

    WebWeaving Internet Engineering

    WebWeaving is a commercial consulting company specialized -in apache related technology, integrated entitlement systems, -apache performance tuning and integration with legacy systems. +in Apache related technology, integrated entitlement systems, +Apache performance tuning and integration with legacy systems.
    For more information visit Modified: httpd/site/trunk/docs/usersdelist.html URL: http://svn.apache.org/viewcvs/httpd/site/trunk/docs/usersdelist.html?rev=369861&r1=369860&r2=369861&view=diff ============================================================================== --- httpd/site/trunk/docs/usersdelist.html (original) +++ httpd/site/trunk/docs/usersdelist.html Tue Jan 17 10:37:36 2006 @@ -87,7 +87,7 @@ Please configure your email client to send plain text so that everyone will be able to read your message. -
    Send german mails:
    The users-de list +
    Send German mails:
    The users-de list is a German-language mailing list. English mails should be directed to our English-language mailing list.
    @@ -99,7 +99,8 @@ questions in the group most targeted to your problem. For example, if you have a problem with a module that is not distributed as part of the standard Apache HTTP Server, you will probably find a more knowledgable -group by sending to a mailing list devoted to that module. +group by sending to a mailing list devoted to that module. In general, mails to +these groups should be sent in English. Some examples:
    • PHP
      • @@ -138,7 +139,7 @@
    -

    To get off the mailing list, send a messages to +

    To unsubscribe, send a messages to users-de-unsubscribe@httpd.apache.org. You must send the unsubscribe message from the same email address that you used to subscribe to the list.

    Modified: httpd/site/trunk/docs/userslist.html URL: http://svn.apache.org/viewcvs/httpd/site/trunk/docs/userslist.html?rev=369861&r1=369860&r2=369861&view=diff ============================================================================== --- httpd/site/trunk/docs/userslist.html (original) +++ httpd/site/trunk/docs/userslist.html Tue Jan 17 10:37:36 2006 @@ -126,7 +126,7 @@ measure. The list is moderated by volunteers from the Apache Software Foundation; moderation will mostly be notable by its absence. However, blatant abuse of the forum's purpose or the sensibilities - of the subscribers will not be tolerated. Any actions taken + of the subscribers will not be tolerated. Any action taken by the moderators is final, solely at their discretion, and not subject to formal appeal.
    @@ -163,7 +163,7 @@
    -

    To get off the mailing list, send a messages to +

    To unsubscribe, send a messages to users-unsubscribe@httpd.apache.org. You must send the unsubscribe message from the same email address that you used to subscribe to the list.