commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mart...@apache.org
Subject cvs commit: jakarta-commons/xdocs charter.xml
Date Fri, 23 Aug 2002 04:53:46 GMT
martinc     2002/08/22 21:53:46

  Modified:    docs     charter.html
               xdocs    charter.xml
  Log:
  Update the Commons charter, per the recent vote on commons-dev, to clarify
  the use of coding conventions in Commons components.
  
  Revision  Changes    Path
  1.45      +17 -2     jakarta-commons/docs/charter.html
  
  Index: charter.html
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/docs/charter.html,v
  retrieving revision 1.44
  retrieving revision 1.45
  diff -u -r1.44 -r1.45
  --- charter.html	22 Aug 2002 05:35:59 -0000	1.44
  +++ charter.html	23 Aug 2002 04:53:46 -0000	1.45
  @@ -357,8 +357,14 @@
     <li>Volunteers become committers to this subproject in the same way they are entered
to any Jakarta subproject. Being a committer in another Jakarta subproject is not a prerequisite.</li>
     <li>Each committer has karma to all the packages, but committers are required to
add their name to a package's status file before their first commit to that package.</li>
     <li>The committers shall elect a committee of three committers to provide general
oversight, in the style of the Jakarta PMC.</li>
  -  <li>New packages may be proposed to the Jakarta Commons mailing list. To be accepted,
a package proposal must receive majority approval of the subproject committers. Proposals
are to identify the rationale
  -    for the package, its scope, its interaction with other packages and products, the Commons
resources, if any, to be created, the initial source from which the package is to be created,
and the initial set of committers.
  +  <li>New packages may be proposed to the Jakarta Commons mailing list. To be
  +      accepted, a package proposal must receive majority approval of the
  +      subproject committers. Proposals are to identify the rationale for the
  +      package, its scope, its interaction with other packages and products, the
  +      Commons resources, if any, to be created, the initial source from which
  +      the package is to be created, the coding conventions used for the package
  +      (if different from the Sun coding conventions), and the initial set of
  +      committers.
       <ul>
         <li>As stated in the Jakarta guidelines, an action requiring majority approval
must receive at least 3 binding +1 votes and more +1 votes than -1 votes.</li>
       </ul>
  @@ -370,6 +376,13 @@
    code or documentation developed here must be sponsored by Jakarta subproject.
    The sponsoring subproject(s) will distribute the code or documentation along with the
       rest of their codebase.</li>
  +  <li>Each Commons component should use an internally consistent and documented
  +      coding style. When the source code for a component originates in a
  +      pre-existing code base outside of Commons, the coding style of that code
  +      base may be retained at the discretion of the initial committers. If a
  +      component does not specify its coding style, the Sun Coding Convention
  +      guidelines are assumed.
  +  </li>
     <li>The subproject catalog will also list packages and resources available to the
public related to other Jakarta subprojects and ASF projects.</li>
     <li>As a Jakarta subproject, the Commons adopts all other guidelines and procedures
of Jakarta and the Apache Software Foundation, as they may be amended from time to time.</li>
   </ol>
  @@ -412,6 +425,8 @@
                                                   <p>The initial codebase was contributed
by Rodney Waldhoff from a working project and can be distributed under the Apache license.
The source is available as dbpool.jar from &lt; <a href="http://www.webappcabaret.com/rwald/dbcp/">http://www.webappcabaret.com/rwald/dbcp/</a>
&gt;</p>
                                                   <p>(2.1) identify the base name for
the package</p>
                                                   <p>org.apache.commons.dbcp</p>
  +                                                <p>(2.2) identify the coding conventions
for this package</p>
  +                                                <p>The code uses the conventions
from the Jakarta Turbine package.</p>
                                                   <p>(3) identify any Jakarta-Commons
resources to be created</p>
                                                   <p>(3.1) mailing list</p>
                                                   <p>Until traffic justifies, the package
will use the Jakarta-Commons list for communications.</p>
  
  
  
  1.6       +17 -2     jakarta-commons/xdocs/charter.xml
  
  Index: charter.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/xdocs/charter.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- charter.xml	13 Jan 2002 19:53:43 -0000	1.5
  +++ charter.xml	23 Aug 2002 04:53:46 -0000	1.6
  @@ -232,8 +232,14 @@
     <li>Volunteers become committers to this subproject in the same way they are entered
to any Jakarta subproject. Being a committer in another Jakarta subproject is not a prerequisite.</li>
     <li>Each committer has karma to all the packages, but committers are required to
add their name to a package's status file before their first commit to that package.</li>
     <li>The committers shall elect a committee of three committers to provide general
oversight, in the style of the Jakarta PMC.</li>
  -  <li>New packages may be proposed to the Jakarta Commons mailing list. To be accepted,
a package proposal must receive majority approval of the subproject committers. Proposals
are to identify the rationale
  -    for the package, its scope, its interaction with other packages and products, the Commons
resources, if any, to be created, the initial source from which the package is to be created,
and the initial set of committers.
  +  <li>New packages may be proposed to the Jakarta Commons mailing list. To be
  +      accepted, a package proposal must receive majority approval of the
  +      subproject committers. Proposals are to identify the rationale for the
  +      package, its scope, its interaction with other packages and products, the
  +      Commons resources, if any, to be created, the initial source from which
  +      the package is to be created, the coding conventions used for the package
  +      (if different from the Sun coding conventions), and the initial set of
  +      committers.
       <ul>
         <li>As stated in the Jakarta guidelines, an action requiring majority approval
must receive at least 3 binding +1 votes and more +1 votes than -1 votes.</li>
       </ul>
  @@ -245,6 +251,13 @@
    code or documentation developed here must be sponsored by Jakarta subproject.
    The sponsoring subproject(s) will distribute the code or documentation along with the
       rest of their codebase.</li>
  +  <li>Each Commons component should use an internally consistent and documented
  +      coding style. When the source code for a component originates in a
  +      pre-existing code base outside of Commons, the coding style of that code
  +      base may be retained at the discretion of the initial committers. If a
  +      component does not specify its coding style, the Sun Coding Convention
  +      guidelines are assumed.
  +  </li>
     <li>The subproject catalog will also list packages and resources available to the
public related to other Jakarta subprojects and ASF projects.</li>
     <li>As a Jakarta subproject, the Commons adopts all other guidelines and procedures
of Jakarta and the Apache Software Foundation, as they may be amended from time to time.</li>
   </ol>
  @@ -283,6 +296,8 @@
   <p>The initial codebase was contributed by Rodney Waldhoff from a working project
and can be distributed under the Apache license. The source is available as dbpool.jar from
&lt; <a href="http://www.webappcabaret.com/rwald/dbcp/">http://www.webappcabaret.com/rwald/dbcp/</a>
&gt;</p>
   <p>(2.1) identify the base name for the package</p>
   <p>org.apache.commons.dbcp</p>
  +<p>(2.2) identify the coding conventions for this package</p>
  +<p>The code uses the conventions from the Jakarta Turbine package.</p>
   <p>(3) identify any Jakarta-Commons resources to be created</p>
   <p>(3.1) mailing list</p>
   <p>Until traffic justifies, the package will use the Jakarta-Commons list for communications.</p>
  
  
  

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message