You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-cvs@jakarta.apache.org by du...@hyperreal.org on 1999/10/07 02:27:48 UTC

cvs commit: jakarta-site/subprojects tomcatcheckindex.html tomcatcheckindex.htsrc

duncan      99/10/06 17:27:43

  Modified:    .        contact.html index.html legal.html
               credits  whoweare.html whoweare.htsrc
               downloads binrelease.html binrelease.htsrc sourceindex.html
                        sourceindex.htsrc
               getinvolved getinvolvedindex.html getinvolvedindex.htsrc
                        library.html library.htsrc
               guidelines management.html management.htsrc roles.html
                        roles.htsrc
               subprojects tomcatcheckindex.html tomcatcheckindex.htsrc
  Log:
  Edits / additions. A bit of work tonight from home and we'll be ready
  to review.
  
  Revision  Changes    Path
  1.7       +2 -2      jakarta-site/contact.html
  
  Index: contact.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site/contact.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- contact.html	1999/10/06 01:49:19	1.6
  +++ contact.html	1999/10/07 00:26:54	1.7
  @@ -1,10 +1,10 @@
   <html>
   <head>
  -<!-- $Id: contact.html,v 1.6 1999/10/06 01:49:19 duncan Exp $ -->
  +<!-- $Id: contact.html,v 1.7 1999/10/07 00:26:54 duncan Exp $ -->
   <!-- Copyright 1999, Apache Software Foundation -->
   <!-- Content head element begins -->
   
  -<!-- $Id: contact.html,v 1.6 1999/10/06 01:49:19 duncan Exp $ -->
  +<!-- $Id: contact.html,v 1.7 1999/10/07 00:26:54 duncan Exp $ -->
   <title>Contact Information</title>
   
   
  
  
  
  1.7       +1 -1      jakarta-site/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site/index.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- index.html	1999/10/06 01:49:20	1.6
  +++ index.html	1999/10/07 00:26:55	1.7
  @@ -1,6 +1,6 @@
   <html>
   <head>
  -<!-- $Id: index.html,v 1.6 1999/10/06 01:49:20 duncan Exp $ -->
  +<!-- $Id: index.html,v 1.7 1999/10/07 00:26:55 duncan Exp $ -->
   <!-- Copyright 1999, Apache Software Foundation -->
   <!-- Content head element begins -->
   
  
  
  
  1.7       +1 -1      jakarta-site/legal.html
  
  Index: legal.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site/legal.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- legal.html	1999/10/06 01:49:20	1.6
  +++ legal.html	1999/10/07 00:26:56	1.7
  @@ -1,6 +1,6 @@
   <html>
   <head>
  -<!-- $Id: legal.html,v 1.6 1999/10/06 01:49:20 duncan Exp $ -->
  +<!-- $Id: legal.html,v 1.7 1999/10/07 00:26:56 duncan Exp $ -->
   <!-- Copyright 1999, Apache Software Foundation -->
   <!-- Content head element begins -->
   
  
  
  
  1.2       +37 -30    jakarta-site/credits/whoweare.html
  
  Index: whoweare.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site/credits/whoweare.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- whoweare.html	1999/10/06 01:49:24	1.1
  +++ whoweare.html	1999/10/07 00:26:58	1.2
  @@ -1,6 +1,6 @@
   <html>
   <head>
  -<!-- $Id: whoweare.html,v 1.1 1999/10/06 01:49:24 duncan Exp $ -->
  +<!-- $Id: whoweare.html,v 1.2 1999/10/07 00:26:58 duncan Exp $ -->
   <!-- Copyright 1999, Apache Software Foundation -->
   <!-- Content head element begins -->
   
  @@ -98,59 +98,66 @@
   
   <p>
   
  -The Jakarta Project operates on a meritocracy: The more you do, the more 
  +The Jakarta Project operates on a meritocracy: the more you do, the more 
   responsibility you will obtain. The people listed here (in no particular 
   order except alphabetically) are those that have already gone that extra 
   mile and who form the early core of the Project. These are the folks that have
   set up the initial working groups for the Servlet and JSP projects. 
  -If you would like to get involved, the first step is to join the <b>MAILING LISTS</B>. 
  -
  +If you would like to get involved, the first step is to join the 
  +<a href=../getinvolved/mail.html>mailing lists</a>.
   <p>
   <b>Brian Behlendorf</b><br>
   brian@behlendorf.com<br>
  -Brian is a co-founder of the Apache HTTP Server Project. He is currently as CTO of New Ventures
  -at O'Reilly and Associates. 
  -</p>
  +Brian is a co-founder of the Apache html>
  +<head>
  +<title>The Jakarta Project: Binary Release Builds</title>
  +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  +</head>
  +<body>
  +
  +<h1>Acknowledgements</h1>
   
   <p>
  -<b>James Duncan Davidson</b><br>
  -duncan@eng.sun.com<br>
  -James a rabble rouser that helped convince Sun that it was a "Good Thing(tm)" to support the Jakarta
  -Project with code and engineers. During the day, he is responsible for the Servlet API.
  +
  +
  +A collaborative project like this doesn't exist in a vacuum. In order to keep project like this running,
  +you need support and help. Project Jakarta has been fortunate to have the support of the following:
   </p>
   
   <p>
  -<b>Pierpaolo Fumagalli</b><br>
  -pier@apache.org<br>
  -Pier is an open source developer who got involved with the Apache JServ project a few years ago. He
  -is currently working for IBM on XML technologies and (of course) on the Jakarta Project.
  +<a href=http://www.apache.org/><b>The Apache Group</b></a><br>
  +Project Jakarta operates as a project under the Apache umbrella. It abides by the same principles and
  +operating procedures as the parent organization.
   </p>
   
   <p>
  -<b>Stefano Mazzocchi</b><br>
  -stefano@apache.org<br>
  -Stefano is a college student addicted to Java programming and open development. He is the author of
  -the Cocoon Publishing Framework and an active contributor of many other projects hosted under the
  -Apache umbrella.
  +<a href=http://www.sun.com/><b>Sun Microsystems, Inc.</b></a><br>
  +Sun is in the process of releasing the code for the JSDK and JSP reference implementations to the
  +Project and provides many engineers to support this project.
   </p>
   
   <p>
  -<b>Craig McClanahan</b><br>
  -cmcclanahan@mytownnet.com<br>
  -Craig is an Information Systems Architect for DAT Services. He joined the Apache JServ project in
  -January 1999, focused on implementing a next generation architecture and feature set in the core
  -servlet engine. 
  +<a href=http://www.ibm.com/><b>IBM</b></a><br>
  +IBM is one of the first corporations to pledge support and engineering resources to The Jakarta
  +Project.
   </p>
   
   <p>
  -<b>Jon Stevens</b><br>
  -jon@clearink.com<br>
  -Jon is a Co-Founder and a Web Engineer at Clear Ink Corp. He is an active developer of the Jserv
  -Servlet Engine for the Apache Web Server and Co-Author of the Element Construction Set.
  -/p>
  +<a href=http://www.clearink.com/><b>Clear Ink</b></a><br>
  +ClearInk hosts all of the mailing lists for this project. As well ClearInk has donated freely of their time
  +and resources to help the Project.
  +</p>
   
  +<p>
  +<a href=http://www.hyperreal.org/><b>Hyperreal</b></a><br>
  +Hyperreal is the server that this site is served from.
  +</p>
   
  +<p>
  +<a href=http://www.above.net/><b>Above.Net</b></a><br>
  +Above.Net provides the network bandwidth for the Apache websites.
   </p>
  +
   
   
   
  
  
  
  1.2       +59 -4     jakarta-site/credits/whoweare.htsrc
  
  Index: whoweare.htsrc
  ===================================================================
  RCS file: /home/cvs/jakarta-site/credits/whoweare.htsrc,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- whoweare.htsrc	1999/10/06 01:49:24	1.1
  +++ whoweare.htsrc	1999/10/07 00:26:58	1.2
  @@ -9,17 +9,72 @@
   
   <p>
   
  -The Jakarta Project operates on a meritocracy: The more you do, the more 
  +The Jakarta Project operates on a meritocracy: the more you do, the more 
   responsibility you will obtain. The people listed here (in no particular 
   order except alphabetically) are those that have already gone that extra 
   mile and who form the early core of the Project. These are the folks that have
   set up the initial working groups for the Servlet and JSP projects. 
  -If you would like to get involved, the first step is to join the <b>MAILING LISTS</B>. 
  -
  +If you would like to get involved, the first step is to join the 
  +<a href=../getinvolved/mail.html>mailing lists</a>.
   <p>
   <b>Brian Behlendorf</b><br>
   brian@behlendorf.com<br>
  -Brian is a co-founder of the Apache HTTP Server Project. He is currently as CTO of New Ventures
  +Brian is a co-founder of the Apache html>
  +<head>
  +<title>The Jakarta Project: Binary Release Builds</title>
  +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  +</head>
  +<body>
  +
  +<h1>Acknowledgements</h1>
  +
  +<p>
  +
  +
  +A collaborative project like this doesn't exist in a vacuum. In order to keep project like this running,
  +you need support and help. Project Jakarta has been fortunate to have the support of the following:
  +</p>
  +
  +<p>
  +<a href=http://www.apache.org/><b>The Apache Group</b></a><br>
  +Project Jakarta operates as a project under the Apache umbrella. It abides by the same principles and
  +operating procedures as the parent organization.
  +</p>
  +
  +<p>
  +<a href=http://www.sun.com/><b>Sun Microsystems, Inc.</b></a><br>
  +Sun is in the process of releasing the code for the JSDK and JSP reference implementations to the
  +Project and provides many engineers to support this project.
  +</p>
  +
  +<p>
  +<a href=http://www.ibm.com/><b>IBM</b></a><br>
  +IBM is one of the first corporations to pledge support and engineering resources to The Jakarta
  +Project.
  +</p>
  +
  +<p>
  +<a href=http://www.clearink.com/><b>Clear Ink</b></a><br>
  +ClearInk hosts all of the mailing lists for this project. As well ClearInk has donated freely of their time
  +and resources to help the Project.
  +</p>
  +
  +<p>
  +<a href=http://www.hyperreal.org/><b>Hyperreal</b></a><br>
  +Hyperreal is the server that this site is served from.
  +</p>
  +
  +<p>
  +<a href=http://www.above.net/><b>Above.Net</b></a><br>
  +Above.Net provides the network bandwidth for the Apache websites.
  +</p>
  +
  +
  +
  +</body>
  +</html>
  +
  +HTTP Server Project. He is currently as CTO of New Ventures
   at O'Reilly and Associates. 
   </p>
   
  
  
  
  1.2       +41 -8     jakarta-site/downloads/binrelease.html
  
  Index: binrelease.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site/downloads/binrelease.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- binrelease.html	1999/10/06 01:49:26	1.1
  +++ binrelease.html	1999/10/07 00:26:59	1.2
  @@ -1,6 +1,6 @@
   <html>
   <head>
  -<!-- $Id: binrelease.html,v 1.1 1999/10/06 01:49:26 duncan Exp $ -->
  +<!-- $Id: binrelease.html,v 1.2 1999/10/07 00:26:59 duncan Exp $ -->
   <!-- Copyright 1999, Apache Software Foundation -->
   <!-- Content head element begins -->
   
  @@ -93,22 +93,55 @@
   contents get inserted by Tac. -->
   
   
  +<html>
  +<head>
  +<title>The Jakarta Project: Downloads</title>
  +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  +</head>
  +<body>
  +
  +<h1>Source Downloads</h1>
  +
  +<p>
  +We make the actual source code available for anyone to use. 
  +In general, the source code is meant for developers who want to  
  +"hack" in order to integrate Servlets and JSP into other products. 
  +
  +Depending on where you are in the development cycle, you'll want to use a
  +particular type of build. We divide our available source code into the
  +following categories:
  +</p>
   
  -<h1>Binary: Release Builds</h1>
  +<ul>
  +<li><a href=sourcerelease.html>Source Code: Release Builds</a>
  +<li><a href=sourcemilestone.html>Source Code: Milestone Builds</a>
  +<li><a href=sourcenightly.html>Source Code: Nightly Builds</a>
  +</ul>
   
   <p>
   <b>Release Builds</b> are those that are ready for Prime Time. These releases
   have been reviewed by Sun's QA Team to ensure compatability with the Servlets
  -and JavaServer Pages Specifications.  
  +and JavaServer Pages Specification. This build is "as good as it gets" and
  +represents the version that should be used for all commercial-grade products.
   </p>
  -We anticipate our first Final Release (corresponding with Java Servlets 2.2 
  -and JavaServer Pages 1.1) to be available by the end of the year. Meanwhile, 
  -the most recent <a href=http://java.sun.com/products/jsp>release build</a> 
  -is available directly from Sun. This version corresponds with JavaServlets 2.1 
  -and JavaServer Pages 1.0. 
  +
  +<p>
  +<b>Milestone Builds</b> are those that are somewhat stable but not crystal-clean.
  +We have some confidence in them, but they are buggy and should only be used by 
  +advanced users who want to explore future product direction or take advantage of
  +new features. This build should not be used for commercial-grade products going to
  +market.
   </p>
   
  +<p>
  +<b>Nightly Builds</b> are those that are very unstable (a.k.a. dynamite!). We have 
  +no confidence in them. They are for developers who are helping to develop the 
  +technology and want "the latest bits." Use at your own risk!
  +</p>
   
  +<p>
  +To get a binary version, <a href=binindex.html>click here</a>.
  +</p>
   
   
   
  
  
  
  1.2       +51 -1     jakarta-site/downloads/binrelease.htsrc
  
  Index: binrelease.htsrc
  ===================================================================
  RCS file: /home/cvs/jakarta-site/downloads/binrelease.htsrc,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- binrelease.htsrc	1999/10/06 01:49:26	1.1
  +++ binrelease.htsrc	1999/10/07 00:26:59	1.2
  @@ -4,7 +4,57 @@
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
   </head>
   <body>
  +<html>
  +<head>
  +<title>The Jakarta Project: Downloads</title>
  +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  +</head>
  +<body>
   
  +<h1>Source Downloads</h1>
  +
  +<p>
  +We make the actual source code available for anyone to use. 
  +In general, the source code is meant for developers who want to  
  +"hack" in order to integrate Servlets and JSP into other products. 
  +
  +Depending on where you are in the development cycle, you'll want to use a
  +particular type of build. We divide our available source code into the
  +following categories:
  +</p>
  +
  +<ul>
  +<li><a href=sourcerelease.html>Source Code: Release Builds</a>
  +<li><a href=sourcemilestone.html>Source Code: Milestone Builds</a>
  +<li><a href=sourcenightly.html>Source Code: Nightly Builds</a>
  +</ul>
  +
  +<p>
  +<b>Release Builds</b> are those that are ready for Prime Time. These releases
  +have been reviewed by Sun's QA Team to ensure compatability with the Servlets
  +and JavaServer Pages Specification. This build is "as good as it gets" and
  +represents the version that should be used for all commercial-grade products.
  +</p>
  +
  +<p>
  +<b>Milestone Builds</b> are those that are somewhat stable but not crystal-clean.
  +We have some confidence in them, but they are buggy and should only be used by 
  +advanced users who want to explore future product direction or take advantage of
  +new features. This build should not be used for commercial-grade products going to
  +market.
  +</p>
  +
  +<p>
  +<b>Nightly Builds</b> are those that are very unstable (a.k.a. dynamite!). We have 
  +no confidence in them. They are for developers who are helping to develop the 
  +technology and want "the latest bits." Use at your own risk!
  +</p>
  +
  +<p>
  +To get a binary version, <a href=binindex.html>click here</a>.
  +</p>
  +</body>
  +</html>
   <h1>Binary: Release Builds</h1>
   
   <p>
  @@ -14,7 +64,7 @@
   </p>
   We anticipate our first Final Release (corresponding with Java Servlets 2.2 
   and JavaServer Pages 1.1) to be available by the end of the year. Meanwhile, 
  -the most recent <a href=http://java.sun.com/products/jsp>release build</a> 
  +the most recent <a href=http://java.sun.com/products/jsp/download.html>release build</a> 
   is available directly from Sun. This version corresponds with JavaServlets 2.1 
   and JavaServer Pages 1.0. 
   </p>
  
  
  
  1.2       +4 -4      jakarta-site/downloads/sourceindex.html
  
  Index: sourceindex.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site/downloads/sourceindex.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- sourceindex.html	1999/10/06 01:49:26	1.1
  +++ sourceindex.html	1999/10/07 00:27:00	1.2
  @@ -1,6 +1,6 @@
   <html>
   <head>
  -<!-- $Id: sourceindex.html,v 1.1 1999/10/06 01:49:26 duncan Exp $ -->
  +<!-- $Id: sourceindex.html,v 1.2 1999/10/07 00:27:00 duncan Exp $ -->
   <!-- Copyright 1999, Apache Software Foundation -->
   <!-- Content head element begins -->
   
  @@ -107,9 +107,9 @@
   </p>
   
   <ul>
  -<li><a href="srcrelease.html">Source Code: Release Builds</a>
  -<li><a href="srcmilestone.html">Source Code: Milestone Builds</a>
  -<li><a href="srcnightly.html">Source Code: Nightly Builds</a>
  +<li><a href="sourcerelease.html">Source Code: Release Builds</a>
  +<li><a href="sourcemilestone.html">Source Code: Milestone Builds</a>
  +<li><a href="sourcenightly.html">Source Code: Nightly Builds</a>
   </ul>
   
   <p>
  
  
  
  1.2       +3 -3      jakarta-site/downloads/sourceindex.htsrc
  
  Index: sourceindex.htsrc
  ===================================================================
  RCS file: /home/cvs/jakarta-site/downloads/sourceindex.htsrc,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- sourceindex.htsrc	1999/10/06 01:49:26	1.1
  +++ sourceindex.htsrc	1999/10/07 00:27:00	1.2
  @@ -18,9 +18,9 @@
   </p>
   
   <ul>
  -<li><a href="srcrelease.html">Source Code: Release Builds</a>
  -<li><a href="srcmilestone.html">Source Code: Milestone Builds</a>
  -<li><a href="srcnightly.html">Source Code: Nightly Builds</a>
  +<li><a href="sourcerelease.html">Source Code: Release Builds</a>
  +<li><a href="sourcemilestone.html">Source Code: Milestone Builds</a>
  +<li><a href="sourcenightly.html">Source Code: Nightly Builds</a>
   </ul>
   
   <p>
  
  
  
  1.2       +2 -2      jakarta-site/getinvolved/getinvolvedindex.html
  
  Index: getinvolvedindex.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site/getinvolved/getinvolvedindex.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- getinvolvedindex.html	1999/10/06 01:49:36	1.1
  +++ getinvolvedindex.html	1999/10/07 00:27:08	1.2
  @@ -1,6 +1,6 @@
   <html>
   <head>
  -<!-- $Id: getinvolvedindex.html,v 1.1 1999/10/06 01:49:36 duncan Exp $ -->
  +<!-- $Id: getinvolvedindex.html,v 1.2 1999/10/07 00:27:08 duncan Exp $ -->
   <!-- Copyright 1999, Apache Software Foundation -->
   <!-- Content head element begins -->
   
  @@ -122,7 +122,7 @@
   In this role, you participate in the actual development of the code. 
   If this is the type of role you'd like to play, here are some steps 
   (in addition to the ones above) to get you started:
  -<li> <a href=../guidelines/guidelines.html>Read Guidelines</a>
  +<li> <a href=../guidelines/index.html>Read Guidelines</a>
   <li> <a href=../getinvolved/library.html>Review Reference Library</a>
   <li> <a href=../getinvolved/cvsindex.html>Access CVS Repository</a>
   
  
  
  
  1.2       +1 -1      jakarta-site/getinvolved/getinvolvedindex.htsrc
  
  Index: getinvolvedindex.htsrc
  ===================================================================
  RCS file: /home/cvs/jakarta-site/getinvolved/getinvolvedindex.htsrc,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- getinvolvedindex.htsrc	1999/10/06 01:49:36	1.1
  +++ getinvolvedindex.htsrc	1999/10/07 00:27:10	1.2
  @@ -33,7 +33,7 @@
   In this role, you participate in the actual development of the code. 
   If this is the type of role you'd like to play, here are some steps 
   (in addition to the ones above) to get you started:
  -<li> <a href=../guidelines/guidelines.html>Read Guidelines</a>
  +<li> <a href=../guidelines/index.html>Read Guidelines</a>
   <li> <a href=../getinvolved/library.html>Review Reference Library</a>
   <li> <a href=../getinvolved/cvsindex.html>Access CVS Repository</a>
   
  
  
  
  1.2       +3 -3      jakarta-site/getinvolved/library.html
  
  Index: library.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site/getinvolved/library.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- library.html	1999/10/06 01:49:36	1.1
  +++ library.html	1999/10/07 00:27:11	1.2
  @@ -1,6 +1,6 @@
   <html>
   <head>
  -<!-- $Id: library.html,v 1.1 1999/10/06 01:49:36 duncan Exp $ -->
  +<!-- $Id: library.html,v 1.2 1999/10/07 00:27:11 duncan Exp $ -->
   <!-- Copyright 1999, Apache Software Foundation -->
   <!-- Content head element begins -->
   
  @@ -105,7 +105,7 @@
   </p>
   
   <p>
  -<h3>Technical Resources</h3><br>
  +<h3>Technical Resources</h3>
   These resources are required reading for anybody contributing source code to the project. 
   </p>
   
  @@ -140,7 +140,7 @@
   </p>
   
   <p>
  -<h3>Source Code Philosophy Resources </h3><br>
  +<h3>Source Code Philosophy Resources </h3>
   The following are a set of articles written about the recent source code movements that help
   illustrate some of the attributes of a collaborative project such as this. You may not agree with all of
   the points of these articles, but an understanding of them will help in communicating with everyone
  
  
  
  1.2       +2 -2      jakarta-site/getinvolved/library.htsrc
  
  Index: library.htsrc
  ===================================================================
  RCS file: /home/cvs/jakarta-site/getinvolved/library.htsrc,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- library.htsrc	1999/10/06 01:49:37	1.1
  +++ library.htsrc	1999/10/07 00:27:13	1.2
  @@ -16,7 +16,7 @@
   </p>
   
   <p>
  -<h3>Technical Resources</h3><br>
  +<h3>Technical Resources</h3>
   These resources are required reading for anybody contributing source code to the project. 
   </p>
   
  @@ -51,7 +51,7 @@
   </p>
   
   <p>
  -<h3>Source Code Philosophy Resources </h3><br>
  +<h3>Source Code Philosophy Resources </h3>
   The following are a set of articles written about the recent source code movements that help
   illustrate some of the attributes of a collaborative project such as this. You may not agree with all of
   the points of these articles, but an understanding of them will help in communicating with everyone
  
  
  
  1.6       +45 -3     jakarta-site/guidelines/management.html
  
  Index: management.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site/guidelines/management.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- management.html	1999/10/06 01:49:41	1.5
  +++ management.html	1999/10/07 00:27:19	1.6
  @@ -1,6 +1,6 @@
   <html>
   <head>
  -<!-- $Id: management.html,v 1.5 1999/10/06 01:49:41 duncan Exp $ -->
  +<!-- $Id: management.html,v 1.6 1999/10/07 00:27:19 duncan Exp $ -->
   <!-- Copyright 1999, Apache Software Foundation -->
   <!-- Content head element begins -->
   
  @@ -94,11 +94,53 @@
   
   
   
  -  <h1>Project Mangement Committee</h1>
  +  <h1>Project Mangement Committee Bylaws</h1>
   
   <p>
     
  -to be written tomorrow...
  +The Project Management Committee (PMC) was formed by the Apache Board in September 1999.
  +This Committee consists of 9 founding members, one of whom is the founding
  +Chairman. The term of the Chairman is one year. There is no term limit for members.
  +</p>
  +
  +<p>
  +<b>Roles</b><br>
  +The PMC is responsible for the strategic direction and 
  +success of the Jakarta Project. This governing body is expected to ensure the
  +project's welfare and guide its overall direction. The PMC may not necessarily
  +participate in the day-to-day coding but is involved in the overall development
  +plans, the alleviation of any bottlenecks, the resolution of conflicts, and 
  +the overall technical success of the project.
  +
  +<p>
  +The PMC is answerable to the Apache Board with its Chairman serving as  
  +primary liaison.
  +</p>
  +
  +<p>
  +<b>Meetings</b><br>
  +The PMC meets monthly with a majority of its members to discuss issues, determine
  +strategic direction, and forward progress. These meetings may take place online,
  +via teleconference, or via other means deemed effective by the PMC. 
  +
  +The PMC has an annual meeting at which time a new Chairman is elected. The old
  +Chairman maintains membership status. 
  +</p>
  +
  +<p>
  +<b>Membership</b><br>
  +PMC members may resign at any time. The Chairman may resign as Chairman at 
  +any time without resigning membership to the PMC. The Chairman or any member 
  +may be removed from the PMC by a 3/4 vote of the PMC.
  +</p>
  +
  +<p>
  +New members may be elected to the PMC. In order to be elected, a person must
  +have served as a <a href=roles.html>Committer</a> and be nominated by a PMC 
  +Member. Once nominated, all of the PMC will vote and those receiving a 3/4 
  +positive vote will become a member.
  +</p>
  +
   
   
   
  
  
  
  1.3       +44 -2     jakarta-site/guidelines/management.htsrc
  
  Index: management.htsrc
  ===================================================================
  RCS file: /home/cvs/jakarta-site/guidelines/management.htsrc,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- management.htsrc	1999/10/06 01:49:41	1.2
  +++ management.htsrc	1999/10/07 00:27:21	1.3
  @@ -5,11 +5,53 @@
   </head>
   <body>
   
  -  <h1>Project Mangement Committee</h1>
  +  <h1>Project Mangement Committee Bylaws</h1>
   
   <p>
     
  -to be written tomorrow...
  +The Project Management Committee (PMC) was formed by the Apache Board in September 1999.
  +This Committee consists of 9 founding members, one of whom is the founding
  +Chairman. The term of the Chairman is one year. There is no term limit for members.
  +</p>
  +
  +<p>
  +<b>Roles</b><br>
  +The PMC is responsible for the strategic direction and 
  +success of the Jakarta Project. This governing body is expected to ensure the
  +project's welfare and guide its overall direction. The PMC may not necessarily
  +participate in the day-to-day coding but is involved in the overall development
  +plans, the alleviation of any bottlenecks, the resolution of conflicts, and 
  +the overall technical success of the project.
  +
  +<p>
  +The PMC is answerable to the Apache Board with its Chairman serving as  
  +primary liaison.
  +</p>
  +
  +<p>
  +<b>Meetings</b><br>
  +The PMC meets monthly with a majority of its members to discuss issues, determine
  +strategic direction, and forward progress. These meetings may take place online,
  +via teleconference, or via other means deemed effective by the PMC. 
  +
  +The PMC has an annual meeting at which time a new Chairman is elected. The old
  +Chairman maintains membership status. 
  +</p>
  +
  +<p>
  +<b>Membership</b><br>
  +PMC members may resign at any time. The Chairman may resign as Chairman at 
  +any time without resigning membership to the PMC. The Chairman or any member 
  +may be removed from the PMC by a 3/4 vote of the PMC.
  +</p>
  +
  +<p>
  +New members may be elected to the PMC. In order to be elected, a person must
  +have served as a <a href=roles.html>Committer</a> and be nominated by a PMC 
  +Member. Once nominated, all of the PMC will vote and those receiving a 3/4 
  +positive vote will become a member.
  +</p>
  +
   
   </body>
   </html>
  
  
  
  1.6       +20 -5     jakarta-site/guidelines/roles.html
  
  Index: roles.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site/guidelines/roles.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- roles.html	1999/10/06 01:49:41	1.5
  +++ roles.html	1999/10/07 00:27:22	1.6
  @@ -1,6 +1,6 @@
   <html>
   <head>
  -<!-- $Id: roles.html,v 1.5 1999/10/06 01:49:41 duncan Exp $ -->
  +<!-- $Id: roles.html,v 1.6 1999/10/07 00:27:22 duncan Exp $ -->
   <!-- Copyright 1999, Apache Software Foundation -->
   <!-- Content head element begins -->
   
  @@ -133,7 +133,7 @@
     authors for that file.
     </p>
   
  -  <h2>Committer</h2>
  +  <h2>Committers</h2>
   
     <p>
     Developers who give frequent and valuable contributions to a
  @@ -147,9 +147,9 @@
     In order for a Developer to become a Committer, another Committer
     can nominate that Developer or the Developer can ask for it. Once a
     Developer is nominated, all of the Committers for a subproject will
  -  vote. If there are no negative votes, the Developer is converted
  -  into a Committer and given write access to the source code
  -  repository for that subproject.
  +  vote. If there are at least 3 positive votes and no negative votes, 
  +  the Developer is converted into a Committer and given write access 
  +  to the source code repository for that subproject.
     </p>
   
     <p>
  @@ -157,6 +157,21 @@
     Committer that has been inactive for 6 months or more may lose his
     or her status as a Committer.
     </p>
  +  
  +  <p>
  +  <h2>Project Management Committee (PMC)</h2>
  +  Committers who frequently participate with valuable contributions may
  +  have their status promoted to that of a &quot;<em>Project Management
  +  Committee Member</em>&quot;. This committee is the official managing
  +  body of the Jakarta Project and is responsible for setting overall 
  +  project direction. In order to become a Member, someone on 
  +  the PMC must nominate the Committer. The individual may then be
  +  approved with a 3/4 majority of the PMC.
  +  </p>
  +  
  +  <p>
  +  To view the Project Management Committee bylaws, <a href=management.html>
  +  click here</a>.
       
   
   
  
  
  
  1.3       +19 -4     jakarta-site/guidelines/roles.htsrc
  
  Index: roles.htsrc
  ===================================================================
  RCS file: /home/cvs/jakarta-site/guidelines/roles.htsrc,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- roles.htsrc	1999/10/06 01:49:41	1.2
  +++ roles.htsrc	1999/10/07 00:27:23	1.3
  @@ -44,7 +44,7 @@
     authors for that file.
     </p>
   
  -  <h2>Committer</h2>
  +  <h2>Committers</h2>
   
     <p>
     Developers who give frequent and valuable contributions to a
  @@ -58,9 +58,9 @@
     In order for a Developer to become a Committer, another Committer
     can nominate that Developer or the Developer can ask for it. Once a
     Developer is nominated, all of the Committers for a subproject will
  -  vote. If there are no negative votes, the Developer is converted
  -  into a Committer and given write access to the source code
  -  repository for that subproject.
  +  vote. If there are at least 3 positive votes and no negative votes, 
  +  the Developer is converted into a Committer and given write access 
  +  to the source code repository for that subproject.
     </p>
   
     <p>
  @@ -68,6 +68,21 @@
     Committer that has been inactive for 6 months or more may lose his
     or her status as a Committer.
     </p>
  +  
  +  <p>
  +  <h2>Project Management Committee (PMC)</h2>
  +  Committers who frequently participate with valuable contributions may
  +  have their status promoted to that of a &quot;<em>Project Management
  +  Committee Member</em>&quot;. This committee is the official managing
  +  body of the Jakarta Project and is responsible for setting overall 
  +  project direction. In order to become a Member, someone on 
  +  the PMC must nominate the Committer. The individual may then be
  +  approved with a 3/4 majority of the PMC.
  +  </p>
  +  
  +  <p>
  +  To view the Project Management Committee bylaws, <a href=management.html>
  +  click here</a>.
       
   </body>
   </html>
  
  
  
  1.2       +2 -2      jakarta-site/subprojects/tomcatcheckindex.html
  
  Index: tomcatcheckindex.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site/subprojects/tomcatcheckindex.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- tomcatcheckindex.html	1999/10/06 01:49:52	1.1
  +++ tomcatcheckindex.html	1999/10/07 00:27:32	1.2
  @@ -1,6 +1,6 @@
   <html>
   <head>
  -<!-- $Id: tomcatcheckindex.html,v 1.1 1999/10/06 01:49:52 duncan Exp $ -->
  +<!-- $Id: tomcatcheckindex.html,v 1.2 1999/10/07 00:27:32 duncan Exp $ -->
   <!-- Copyright 1999, Apache Software Foundation -->
   <!-- Content head element begins -->
   
  @@ -101,7 +101,7 @@
   and JavaServer Pages specifications, is currently under development and
   is expected to be completed along with the final release of Tomcat at year's
   end. Tomcat Check is available in beta form. To download a beta version, 
  -<a href=../xyz>click here</a>.
  +<a href=../getinvolved/getinvolvedindex.html>click here</a>.
   
   To learn more about getting involved in the development of Tomcat Check,
   <a href=../getinvolved/getinvolvedindex.html> click here</a>.
  
  
  
  1.2       +1 -1      jakarta-site/subprojects/tomcatcheckindex.htsrc
  
  Index: tomcatcheckindex.htsrc
  ===================================================================
  RCS file: /home/cvs/jakarta-site/subprojects/tomcatcheckindex.htsrc,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- tomcatcheckindex.htsrc	1999/10/06 01:49:53	1.1
  +++ tomcatcheckindex.htsrc	1999/10/07 00:27:34	1.2
  @@ -12,7 +12,7 @@
   and JavaServer Pages specifications, is currently under development and
   is expected to be completed along with the final release of Tomcat at year's
   end. Tomcat Check is available in beta form. To download a beta version, 
  -<a href=../xyz>click here</a>.
  +<a href=../getinvolved/getinvolvedindex.html>click here</a>.
   
   To learn more about getting involved in the development of Tomcat Check,
   <a href=../getinvolved/getinvolvedindex.html> click here</a>.