httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodent of Unusual Size <c...@hyperreal.org>
Subject cvs commit: apache-site ABOUT_APACHE.html
Date Thu, 10 Jul 1997 11:36:44 GMT
coar        97/07/10 04:36:43

  Added:       .         ABOUT_APACHE.html
  Log:
  	A somewhat sanitised version of the ABOUT_APACHE text file that's
  	included in the distribution.  Suitable to convey information w/o
  	opening the Gates of Spam.
  
  Revision  Changes    Path
  1.1                  apache-site/ABOUT_APACHE.html
  
  Index: ABOUT_APACHE.html
  ===================================================================
  <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
  <HTML>
   <HEAD>
    <TITLE>About Apache</TITLE>
   </HEAD>
  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
   <BODY
    BGCOLOR="#FFFFFF"
    TEXT="#000000"
    LINK="#0000FF"
    VLINK="#000080"
    ALINK="#FF0000"
   >
    <DIV ALIGN="CENTER">
     <IMG SRC="images/apache_logo.gif" ALT="" HEIGHT="148" WIDTH="400">
    </DIV>
    <H1 ALIGN="CENTER">
     About the Apache HTTP Server Project
    </H1>
    <H3 ALIGN="CENTER">
     &lt;<A
          HREF="http://www.apache.org"
         >http://www.apache.org/</A>&gt;
     <BR>
     June 1997
    </H3>
    <HR>
    <H2>
     What <EM>IS</EM> the Apache Project?
    </H2>
    <P>
    The Apache Project is a collaborative software development effort aimed
    at creating a robust, commercial-grade, featureful, and freely-available
    source code implementation of an HTTP (Web) server.  The project is
    jointly managed by a group of volunteers located around the world, using
    the Internet and the Web to communicate, plan, and develop the server and
    its related documentation.  These volunteers are known as the Apache Group.
    In addition, hundreds of users have contributed ideas, code, and
    documentation to the project.  This file is intended to briefly describe
    the history of the Apache Group and recognize the many contributors.
    </P>
    <HR>
    <H2>
     How Apache Came to Be
    </H2>
    <P>
    In February of 1995, the most popular server software on the Web was the
    public domain HTTP daemon developed by Rob McCool at the National Center
    for Supercomputing Applications, University of Illinois, Urbana-Champaign.
    However, development of that httpd had stalled after Rob left NCSA in
    mid-1994, and many webmasters had developed their own extensions and bug
    fixes that were in need of a common distribution.  A small group of these
    webmasters, contacted via private e-mail, gathered together for the purpose
    of coordinating their changes (in the form of &quot;patches&quot;).
    Brian Behlendorf and Cliff Skolnick put together a mailing list,
    shared information space, and logins for the core developers on a
    machine in the California Bay Area, with bandwidth and diskspace
    donated by HotWired and Organic Online.  By the end of February, eight
    core contributors formed the foundation of the original Apache Group:
    </P>
    <DIV ALIGN="CENTER">
     <TABLE>
      <TR>
       <TD>Brian Behlendorf
       </TD>
       <TD>Roy T. Fielding
       </TD>
       <TD>Rob Hartill
       </TD>
      </TR>
      <TR>
       <TD>David Robinson&nbsp;&nbsp;
       </TD>
       <TD>Cliff Skolnick&nbsp;
       </TD>
       <TD>Randy Terbush
       </TD>
      </TR>
      <TR>
       <TD>Robert S. Thau&nbsp;&nbsp;
       </TD>
       <TD>Andrew Wilson&nbsp;&nbsp;
       </TD>
      </TR>
     </TABLE>
    </DIV>
    <P>
    with additional contributions from
    </P>
    <DIV ALIGN="CENTER">
     <TABLE>
      <TR>
       <TD>Eric Hagberg&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
       <TD>Frank Peters&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
       <TD>Nicolas Pioch
      </TR>
     </TABLE>
    </DIV>
    <P>
    Using NCSA httpd 1.3 as a base, we added all of the published bug fixes
    and worthwhile enhancements we could find, tested the result on our own
    servers, and made the first official public release (0.6.2) of the Apache
    server in April 1995.  By coincidence, NCSA restarted their own development
    during the same period, and Brandon Long and Beth Frank of the NCSA Server
    Development Team joined the list in March as honorary members so that the
    two projects could share ideas and fixes.
    </P>
    <P>
    The early Apache server was a big hit, but we all knew that the codebase
    needed a general overhaul and redesign.  During May-June 1995, while
    Rob Hartill and the rest of the group focused on implementing new features
    for 0.7.x (like pre-forked child processes) and supporting the rapidly growing
    Apache user community, Robert Thau designed a new server architecture
    (code-named Shambhala) which included a modular structure and API for better
    extensibility, pool-based memory allocation, and an adaptive pre-forking
    process model.  The group switched to this new server base in July and added
    the features from 0.7.x, resulting in Apache 0.8.8 (and its brethren)
    in August.
    </P>
    <P>
    After extensive beta testing, many ports to obscure platforms, a new set
    of documentation (by David Robinson), and the addition of many features
    in the form of our standard modules, Apache 1.0 was released on
    December 1, 1995.
    </P>
    <P>
    Less than a year after the group was formed, the Apache server passed
    NCSA's httpd as the #1 server on the Internet.
    </P>
    <HR SIZE="4">
    <H2>
     Current Apache Group, 1 June 1997
    </H2>
    <TABLE>
     <TR>
      <TD>Brian Behlendorf&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>Organic Online, California
      </TD>
     </TR>
     <TR>
      <TD>Ken Coar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>Process Software Corporation, New England, USA 
      </TD>
     </TR>
     <TR>
      <TD>Mark J. Cox&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>UKWeb, UK 
      </TD>
     </TR>
     <TR>
      <TD>Roy T. Fielding&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>UC Irvine, California 
      </TD>
     </TR>
     <TR>
      <TD>Dean Gaudet&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>Steam Tunnel Operations, California 
      </TD>
     </TR>
     <TR>
      <TD>Rob Hartill&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>Internet Movie DB, UK 
      </TD>
     </TR>
     <TR>
      <TD>Jim Jagielski&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>jaguNET ISP, Maryland 
      </TD>
     </TR>
     <TR>
      <TD>Alexei Kosut&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>Nueva High School, California 
      </TD>
     </TR>
     <TR>
      <TD>Ben Laurie&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>Freelance Consultant, UK 
      </TD>
     </TR>
     <TR>
      <TD>Chuck Murcko&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>The Topsail Group, Pennsylvania 
      </TD>
     </TR>
     <TR>
      <TD>Aram W. Mirzadeh&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>Qosina Corporation, New York 
      </TD>
     </TR>
     <TR>
      <TD>Sameer Parekh&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>C2Net, California 
      </TD>
     </TR>
     <TR>
      <TD>Paul Sutton&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>UKWeb, UK 
      </TD>
     </TR>
     <TR>
      <TD>Marc Slemko&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>Canada 
      </TD>
     </TR>
     <TR>
      <TD>Randy Terbush&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>Zyzzyva ISP, Nebraska 
      </TD>
     </TR>
     <TR>
      <TD>Dirk-Willem van Gulik
      </TD>
      <TD>Freelance Consultant, Italy 
      </TD>
     </TR>
     <TR>
      <TD>Andrew Wilson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>Freelance Consultant, UK 
      </TD>
     </TR>
    </TABLE>
    <P>
    Apache Emeritae (old group members now off doing other things)
    </P>
    <TABLE>
     <TR>
      <TD>Robert S. Thau&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>MIT, Massachusetts
      </TD>
     </TR>
     <TR>
      <TD>David Robinson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </TD>
      <TD>Cambridge University, UK
      </TD>
     </TR>
    </TABLE>
    <HR>
    <H3>
     Other Major Contributors
    </H3>
    <UL>
     <LI>Rob McCool (original author of the NCSA httpd),
     </LI>
     <LI>Brandon Long and Beth Frank (NCSA Server Development Team, post-1.3),
     </LI>
     <LI>Paul Richards (convinced the group to use remote CVS after 1.0),
     </LI>
     <LI>Kevin Hughes (creator of all those nifty icons),
     </LI>
     <LI>Henry Spencer (author of the regex library), Garey Smiley (OS/2 port),
     </LI>
     <LI>Ralf S. Engelschall (<SAMP>mod_rewrite</SAMP>),
     </LI>
     <LI>Howard Fear (<SAMP>mod_include</SAMP>),
     </LI>
     <LI>Florent Guillaume (language negotiation),
     </LI>
     <LI>Ambarish Malpani (NT port).
     </LI>
    </UL>
    <P>
    Many 3<SUP>rd</SUP>-party modules, frequently used and recommended, are also
    freely-available and linked from the related projects page:
    &lt;<A
         HREF="http://www.zyzzyva.com/module_registry/"
        ><SAMP>http://www.zyzzyva.com/module_registry/</SAMP></A>&gt;,
and
    their authors frequently 
    contribute ideas, patches, and testing.  In particular, Doug MacEachern
    (<SAMP>mod_perl</SAMP>) and Rasmus Lerdorf (<SAMP>mod_php</SAMP>).
    </P>
    <P>
    Hundreds of people have made individual contributions to the Apache
    project.  Patch contributors are listed in the src/CHANGES file.
    Frequent contributors have included Petr Lampa, Tom Tromey,
    James H. Cloos Jr., Ed Korthof, Nathan Neulinger, Jason S. Clary,
    Jason A. Dour, Michael Douglass, Tony Sanders, Martin Kraemer,
    Brian Tao, Michael Smith, Adam Sussman, Nathan Schrenk, Matthew Gray,
    and John Heidemann.
    </P>
    <HR SIZE="4">
    <H2>
     Getting Involved
    </H2>
    <P>
    If you just want to send in an occasional suggestion/fix, then you can
    just use the bug reporting form at
    &lt;<A
         HREF="http://www.apache.org/bugdb.cgi"
        ><SAMP>http://www.apache.org/bugdb.cgi</SAMP></A>&gt;.
    You can also subscribe to the
    announcements mailing list (<SAMP>apache-announce@apache.org</SAMP>)
    which we use to 
    broadcast information about new releases, bugfixes, and upcoming
    events.
    </P>
    <BLOCKQUOTE>
     <STRONG>NOTE:</STRONG>
     The developer mailing list 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
     to the USENET newsgroup
     &quot;<A
  	  HREF="news:comp.infosystems.www.servers.unix"
  	 ><SAMP>comp.infosystems.www.servers.unix</SAMP></A>&quot;.
    </BLOCKQUOTE>
    <HR>
    <H2>
     The Apache Development Process
    </H2>
    <P>
    The Apache Group is a meritocracy -- the more work you have done, the more
    you are allowed to do.  The group founders set the original rules, but
    they can be changed by vote of the active members.  There is a core group
    of people who have logins on our server and access to the
    CVS repository.  Everyone has access to the CVS snapshots.  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
    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.
    </P>
    <P>
    Our primary method of communication is our mailing list. Approximately 40
    messages a day flow over the list, and are typically very conversational in
    tone. We discuss new features to add, bug fixes, user problems, developments
    in the web server community, release dates, etc.  The actual code development
    takes place on the developers' local machines, with proposed changes
    communicated using a patch (output of a context "diff -c3 oldfile newfile"
    command), and committed to the source repository by one of the core
    developers using remote CVS.
    </P>
    <P>
    New members of the Apache Group are added when a frequent contributor is
    nominated by one member and unanimously approved by the voting members.
    In most cases, this &quot;new&quot; member has been actively
    contributing to the 
    group's work for over six months, so it's usually an easy decision.
    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
    explanation.
    </P>
    <P>
    The above describes our past and current (as of June 1997) guidelines,
    which will probably change over time as the membership of the group
    changes and our development/coordination tools improve.
    </P>
    <HR SIZE="4">
    <H2>
     Why Apache is Free
    </H2>
    <P>
    Apache exists to provide a robust and commercial-grade reference
    implementation of the HTTP protocol.  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
    such as specialized modules and support, amongst other things.  We realize
    that it is often seen as an economic advantage for one company to
    &quot;own&quot; a
    market - in the software industry that means to control tightly a
    particular conduit such that all others must pay.  This is typically done
    by &quot;owning&quot; 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 &quot;unowned&quot; by a single company, the
    Web will 
    remain a level playing field for companies large and small. Thus,
    &quot;ownership&quot; of the protocol must be prevented, and the
    existence of a 
    robust reference implementation of the protocol, available absolutely for
    free to all companies, is a tremendously good thing.
    </P>
    <P>
    Furthermore, Apache is an organic entity; those who benefit from it
    by using it often contribute back to it by providing feature enhancements,
    bug fixes, and support for others in public newsgroups.  The amount of
    effort expended by any particular individual is usually fairly light, but
    the resulting product is made very strong.  This kind of community can
    only happen with freeware -- 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 fact that it's free, and if it were made
    &quot;not free&quot; it would suffer tremendously, even if that money
    were spent on a real development team.
    </P>
    <P>
    We want to see Apache used very widely -- by large companies, small
    companies, research institutions, schools, individuals, in the intranet
    environment, everywhere -- even though this may mean that companies who
    could afford commercial software, and would pay for it without blinking,
    might get a &quot;free ride&quot; by using Apache.  We would even be
    happy if some 
    commercial software companies completely dropped their own HTTP server
    development plans and used Apache as a base, with the proper attributions
    as described in the LICENSE file.
    </P>
    <H3 ALIGN="CENTER">
     <EM>Thanks for using Apache!</EM>
    </H3>
    <HR>
    <P>
    <ADDRESS>Roy Fielding, June 1997</ADDRESS>
    </P>
    <P>
    If you are interested in other WWW history, see
    &lt;<A
         HREF="http://www.webhistory.org/"
        ><SAMP>http://www.webhistory.org/</SAMP></A>&gt;.
   </BODY>
  </HTML>
  
  
  

Mime
View raw message