cvs commit: apachen STATUS
marc98/01/11 17:39:19 Modified:.STATUS Log: win32 update. Revision ChangesPath 1.76 +10 -7 apachen/STATUS Index: STATUS === RCS file: /export/home/cvs/apachen/STATUS,v retrieving revision 1.75 retrieving revision 1.76 diff -u -r1.75 -r1.76 --- STATUS1998/01/11 20:55:15 1.75 +++ STATUS1998/01/12 01:39:18 1.76 @@ -302,12 +302,10 @@ - how CGIs work - update README.NT - short/long name handling + - better status page on current state of NT for users * http_main.c hell - -* mod_example isn't multithreadreded - -* mod_info + - split into two files? * who should run the service? Who exactly is the system account? @@ -330,8 +328,13 @@ That _really_ sucks. Can we recommend running Apache as some other user? -* mod_example isn't multithreadreded - -* mod_info +* need a crypt() of some sort. + - sources are easy; problem is export restrictions on DES + - if we don't do DES, can do md5 + +* modules that need to be made to work on win32 + - mod_info +- mod_example isn't multithreadreded +* do something to disable bogus warnings
cvs commit: apache-devsite guidelines.html
fielding98/01/11 17:53:37 Added: .guidelines.html Log: A start on a complete update of the Apache Project voting rules and guidelines. Revision ChangesPath 1.1 apache-devsite/guidelines.html Index: guidelines.html === HTML HEAD TITLEApache Project Guidelines and Voting Rules/TITLE /HEAD !-- Background white, links blue (unvisited), navy (visited), red (active) -- BODY BGCOLOR=#FF TEXT=#00 LINK=#FF VLINK=#80 ALINK=#FF CENTER IMG SRC=images/apache_logo.gif ALT= H1 ALIGN=CENTERApache Project Guidelines and Voting Rules/H1 PBDRAFT/B: These guidelines are not yet approved./P /CENTER P This document defines the rules and guidelines for the Apache Project. It includes definitions of how conflict is resolved by voting, who is able to vote, and the procedures to follow for proposing and making changes to the Apache products. /P P The objective here is to avoid unnecessary conflict over changes and continue to produce a quality system in a timely manner. Not all conflict can be avoided, but at least we can agree on the procedures for conflict to be resolved. /P P The following define some common terms: /P DL DTSTRONGApache Group/STRONG/DT DDThe group of volunteers who are responsible for managing the Apache Project. This includes deciding what is distributed as products of the Apache Project, maintaining the Project's shared resources, speaking on behalf of the Apache Project, resolving license disputes regarding Apache products, and establishing these rules and guidelines. PMembership in the Apache Group is by invitation only and must be approved by consensus of the active Apache Group members. A member is considered inactive by their own declaration or by not contributing in any form to the project for over six months. An inactive member can become active again by reversing whichever condition made them inactive (i.e., by reversing their earlier declaration or by once again contributing toward the project's work). Membership can be revoked by a unanimous vote of all the active members other than the member in question./DDP DTSTRONGApache Developers/STRONG/DT DDAll of the volunteers who are contributing time, code, documentation, or resources to the Apache Project. A developer that makes sustained, welcome contributions to the project for over six months is usually invited to join the Apache Group, though the exact timing of such invitations depends on many factors./DDP DTSTRONGmailing list/STRONG/DT DDThe Apache developers' primary mailing list for discussion of issues and changes related to the project (inew-httpd@apache.org/i). Subscription to the list is open, but only subscribers can post directly to the list./DDP DTSTRONGprivate list/STRONG/DT DDThe Apache Group's private mailing list for discussion of issues that are inappropriate for public discussion, such as legal, personal, or security issues prior to a published fix. Subscription to the list is only open to Apache Group members./DDP DTSTRONGCVS/STRONG/DT DDAll of the Apache products are maintained in shared information repositories using a href=devnotes.htmlCVS on idev.apache.org/i./a Only some of the Apache developers have write access to these repositories; everyone has read access via a href=anoncvs.txtanonymous CVS/a. Developers who want write access need to ask for it on the mailing list and, if approved, need to ask the admin of idev.apache.org/i for a user account./DD /DL HR SIZE=6 H2IMG SRC=images/apache_feather_bullet.gif alt=o STATUS/H2 P Each of the Apache Project's active source code repositories contain a file called STATUS which is used to keep track of the agenda and plans for work within that repository. The STATUS file includes information about release plans, a summary of code changes committed since the last release, a list of proposed changes that are under discussion, brief notes about items that individual developers are working on or want discussion about, and anything else that might be useful to help the group track progress. The active STATUS files are automatically posted to the mailing list three times each week. /P P Many issues will be encountered by the project, each resulting in zero or more proposed action items. Issues should be raised on the mailing list as soon as they are identified. Action items STRONGmust/STRONG be raised on the mailing list and added to the relevant STATUS file. All action items may be voted on, but not
cvs commit: apache-devsite guidelines.html
jim 98/01/11 18:15:37 Modified:.guidelines.html Log: Provide a loophole for the compile condition Revision ChangesPath 1.2 +4 -4 apache-devsite/guidelines.html Index: guidelines.html === RCS file: /export/home/cvs/apache-devsite/guidelines.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- guidelines.html 1998/01/12 01:53:36 1.1 +++ guidelines.html 1998/01/12 02:15:37 1.2 @@ -228,10 +228,10 @@ --- higher than the typical [PATCH] post to new-httpd. UL -LIAdvance notice (eg: I'll be working on flurgl.c) will be given; -this will help in cause others wish to help and to avoid -stepping on people's toes/concurrent patches on the same code. -LIThe CVS tree should be expected to compile at all times +LIAdvance notice (eg: I'll be working on flurgl.c) will be given +LIThe CVS tree should be expected to compile at all times; If it +is possible that the code will result in some platforms not +compiling, notice of this should be announced. LIExperimental new features must be discussed before implemented LIThe committer is responsible for the quality of the third-party code they bring into the code.
cvs commit: apache-devsite styleguide.html
pcs 98/01/12 06:18:07 Modified:.styleguide.html Log: Update my email address. Hey, spam bots, new email address over here! Revision ChangesPath 1.5 +1 -1 apache-devsite/styleguide.html Index: styleguide.html === RCS file: /export/home/cvs/apache-devsite/styleguide.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- styleguide.html 1997/08/01 20:08:49 1.4 +++ styleguide.html 1998/01/12 14:18:06 1.5 @@ -5,7 +5,7 @@ H1Apache Developers' C Language Style Guide/H1 STRONGCompiled by Paul Sutton A -HREF=mailto:[EMAIL PROTECTED][EMAIL PROTECTED]/A/STRONG. Based on a vote +HREF=mailto:[EMAIL PROTECTED][EMAIL PROTECTED]/A/STRONG. Based on a vote taken in November, 1996. BR Further refinements voted upon in July 1997.
cvs commit: apache-devsite todo.html
pcs 98/01/12 06:27:36 Modified:.todo.html Log: Umm, the is pretty redundand. The bugdb does all this tracking much better. I was going to just remove the bits I've done, but I've also cleaned out some other items which are clearly done. But I think we should remove this file completely. Nobody'll notice it's gone. Revision ChangesPath 1.2 +0 -26 apache-devsite/todo.html Index: todo.html === RCS file: /export/home/cvs/apache-devsite/todo.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- todo.html 1997/06/17 10:43:34 1.1 +++ todo.html 1998/01/12 14:27:36 1.2 @@ -28,14 +28,6 @@ LIMore tolerant config-file parsing - beb -LIAllow ErrorDocument anywhere (One line change but needs user configuration) - mjc - -LIClean Shambhala messages in source - mjc - -LINicer Access Control (allow OneOf,AND,OR ala NCSA) - mjc - -LICheck returns from all system calls: read, write, etc. - beb - LIFormalized internal error-logging system, like sendmail/syslogd interaction - beb @@ -54,34 +46,17 @@ LIConfigurable Error Reporting UL LISeparate logs for stderr and server error messages - LIEnable all virtual hosts to error-log to the same log - LIDifferent debugging levels, a la named or sendmail /UL -LIMore than one transferlog per virthost, each with its own transferformat. - in progress/pcs - LIDynamic Package builder - so that people can download binaries with exactly the options and packages they want. - beb LIImplementation of the LINK Method - beb -LIFull HTTP/1.1 Content negotiation support - beb - LIData store abstraction API? So we're not always presuming we sit on top of a filesystem. - beb -LIPort to Windows NT - beb - LIPort to BeBox - beb -LIAllow Byte Ranges for completion of interrupted transfers (Netscape 2.0b4+ client seems to have byte-range code in it) - mjc - -LIClean up source/comments still left from NCSA/1.3 - mjc - -LINamed Access Methods - in progress/pcs - -LIregular expression library in the core, rather than in numerous -different modules. - beb - LIgive an Option, like IncludesNoExec, except allow for CGI includes, not CMD includes. -beb, and others @@ -93,7 +68,6 @@ LIStandards for Modules - beb LICGI Extensions - beb LISetting up logging and logfile analysis system - beb -LICookie Module - mjc LIDBM documentation: explain about having username/group in same file - mjc LIMSQL documentation -dv LIPolicy - what it takes for a module to move from contrib to the regular distribution. - aw
Re: cvs commit: apache-devsite todo.html
On 12 Jan 1998 [EMAIL PROTECTED] wrote: pcs 98/01/12 06:27:36 Modified:.todo.html Log: Umm, the is pretty redundand. The bugdb does all this tracking much better. I was going to just remove the bits I've done, but I've also cleaned out some other items which are clearly done. But I think we should remove this file completely. Nobody'll notice it's gone. No, the bugdb doesn't really address the same things. The only reason we wouldn't notice it is gone is because it is obsolete...
cvs commit: apache-devsite index.html
dgaudet 98/01/12 12:34:29 Modified:.index.html Log: enough people have been confused Revision ChangesPath 1.13 +3 -4 apache-devsite/index.html Index: index.html === RCS file: /export/home/cvs/apache-devsite/index.html,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- index.html1997/12/20 16:06:44 1.12 +++ index.html1998/01/12 20:34:28 1.13 @@ -23,10 +23,9 @@ be waiting for someone to get around to updating them. /BLOCKQUOTE UL TYPE=SQUARE - LIDeveloper access to the -A - HREF=http://dev.apache.org/private/bugdb.cgi; -bug database/A + LIA href=http://bugs.apache.org/;Read-only/a, or +a href=http://bugs.apache.org/private/;read-write/a access to the +bug database. /LI LIArchives of the A
cvs commit: apache-devsite index.html
coar98/01/12 13:02:53 Modified:.index.html Log: Add a note about R/W access to the bugdb requiring an account, and more details about what's in /from-cvs/. Revision ChangesPath 1.14 +8 -7 apache-devsite/index.html Index: index.html === RCS file: /export/home/cvs/apache-devsite/index.html,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- index.html1998/01/12 20:34:28 1.13 +++ index.html1998/01/12 21:02:53 1.14 @@ -23,9 +23,9 @@ be waiting for someone to get around to updating them. /BLOCKQUOTE UL TYPE=SQUARE - LIA href=http://bugs.apache.org/;Read-only/a, or -a href=http://bugs.apache.org/private/;read-write/a access to the -bug database. + LIA HREF=http://bugs.apache.org/;Read-only/A, or +A HREF=http://bugs.apache.org/private/;read-write/A access to the +bug database. (Read-write access requires authorisation.) /LI LIArchives of the A @@ -87,13 +87,14 @@ (last modified on !--#flastmod virtual=todo.html --) /LI LIThe A HREF=from-cvs/latest source tree/A pulled from the - CVS repository. Not guaranteed to do anything, especially not - compile or work. + CVS repository, packaged with SAMPtar/SAMP, and compressed + with SAMPgzip/SAMP. Not guaranteed + to do anything, especially not compile or work. /LI - LIa href=anoncvs.txtInstructions/a + LIA HREF=anoncvs.txtInstructions/A on using anonymous CVS to access the development repository. /LI - LIa href=http://www.engelschall.com/pw/apache/cvsguide/;Instructions/a + LIA HREF=http://www.engelschall.com/pw/apache/cvsguide/;Instructions/A on developer access to the repository via CVSup. /LI LIA Web-based view of the
