You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by cr...@apache.org on 2003/10/19 10:49:07 UTC
cvs commit: cocoon-site/src/documentation/content/xdocs guidelines.xml
crossley 2003/10/19 01:49:07
Modified: src/documentation/content/xdocs guidelines.xml
Log:
- Added section heading for "Developer". People ask what the terms means.
- Tweaked "Contributors" section to simply say that there are various ways
to be recognised (perhaps this "recognition" topic needs wider attention).
- Rewrote sections that mention "promotion".
- Removed phrase that said "Contributers can ask to become a Committer".
- Added the phrase "and demonstrate commitment" in a few places.
- Reworded the phrase "all of the Committers will vote" for a new Committer.
Surely we do not "all" need to. We may be away for a while.
- Mention Apache CLA.
- Reflect decision that Inactive committers are eventually listed as Emeritus.
- Change words describing how to become a PMC Member to reflect what we
are currently doing. Added some fixme notes.
Revision Changes Path
1.7 +56 -37 cocoon-site/src/documentation/content/xdocs/guidelines.xml
Index: guidelines.xml
===================================================================
RCS file: /home/cvs/cocoon-site/src/documentation/content/xdocs/guidelines.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- guidelines.xml 12 Aug 2003 22:26:09 -0000 1.6
+++ guidelines.xml 19 Oct 2003 08:49:07 -0000 1.7
@@ -17,75 +17,93 @@
of the Project. Each subproject may adopt additional guidelines, which may
extend but not supercede the Project guidelines.</p>
- <section>
- <title>Roles & Responsibilities</title>
+ <section id="roles">
+ <title>Roles and Responsibilities</title>
<p>The roles and responsibilities that people can assume in the project
- are based on merit. Everybody can help no matter what their role. Those
- who have been long term or valuable contributors to the project obtain
- the right to vote and commit directly to the source repository.</p>
+ are based on merit. Everybody can help, no matter what their role.
+ Those who have been long-term valuable contributors and demonstrate
+ commitment to the project, obtain the right to vote and commit directly
+ to the source repository.</p>
- <section>
+ <section id="users">
<title>Users</title>
<p>Users are the people who use the products of the Project. People in
- this role aren't contributing code, but they are using the
+ this role are not contributing code, but they are using the
products, reporting bugs, making feature requests, helping other
users, extending the online FAQ, and such. This is by far the most
important category of people as, without users, there is no reason for
the Project.</p>
+ </section>
+
+ <section id="developers">
+ <title>Developers</title>
<p>When a user starts to contribute code or documentation patches,
they become a developer.</p>
</section>
- <section>
+ <section id="Contributors">
<title>Contributors</title>
<p>Contributors are the people who write code or documentation patches
- or contribute positively to the project in other ways. A
- volunteer's contribution is always recognized. <code>In source
- code, all volunteers who contribute to a source file may add their
- name to the list of authors for that file.</code></p>
+ or contribute positively to the project in other ways. Such
+ volunteer contributions are recognized in various ways.
+ </p>
</section>
- <section>
+ <section id="committers">
<title>Committers</title>
<p>Contributors who give frequent and valuable contributions to a
- subproject of the Project can have their status promoted to that of a
- <em>"Committer"</em> for that subproject. A Committer has
- write access to the source code repository and gains voting rights
- allowing them to affect the future of the subproject.</p>
+ subproject of the Project and demonstrate commitment, may be asked
+ to become a <em>"Committer"</em> for that subproject.
+ A Committer has write access to the source code repository and
+ voting rights enabling them to affect the future of the subproject.
+ </p>
<p>In order for a Contributor to become a Committer, another Committer
- can nominate that Contributor or the Contributor can ask for it. Once
- a Contributor is nominated, all of the Committers for a subproject
+ can nominate that Contributor. Once
+ a Contributor is nominated, the Committers for a subproject
will vote. If there are at least 3 positive votes and no negative
- votes, the Contributor is converted into a Committer and given write
+ votes, the new Committer is asked to sign an Apache Contributor
+ License Agreement (CLA) and is provided with an Apache username and
+ account, and given write
access to the source code repository for that subproject. Before
receiving write access, a Committer must also affirm that they have
read and understood these guidelines, and agree to abide by their
terms, as they may be revised from time to time.</p>
+<!-- FIXME: How is this last bit enforced? Does the Apache CLA refer to
+our project "guidelines" -->
- <p>At times, Committers may go inactive for a variety of reasons. A
- Committer that has been inactive for 6 months or more may lose his or
- her status as a Committer.</p>
+ <p>At times, Committers may go inactive for a variety of reasons.
+ One that has been inactive for a while may be listed as Emeritus
+ Committer.</p>
- <p><code>A list of our current Committers can be found in our Project
- Credits.</code></p>
+ <p>A list of our current Committers can be found in our Project
+ Credits.</p>
</section>
- <section>
+ <section id="pmc">
<title>Project Management Committee (PMC)</title>
- <p>Committers who frequently participate with valuable contributions
- may have their status promoted to that of a <em>"Project
- Management Committee Member"</em>. This committee is the official
+ <p>Any Committers who desires to participate can join the PMC
+ mailing list to become a member of the PMC
+<!-- FIXME: Have we officially decided this? Also need to declare how
+subproject committers relate to the Cocoon PMC.
+See email pmc around 2003-06-18 and 2003-07-29.
+ -->
+ This committee is the official
managing body of the Apache Cocoon Project and is responsible for
- setting overall project direction. <code>For more about the Apache
+ setting overall project direction. For more about the Apache
Cocoon PMC, see the Project Management Committee bylaws. A list of our
- current PMC Members can be found in our Project Credits.</code></p>
+ current PMC Members can be found in our Project Credits.</p>
+<!-- FIXME: Need to find the email where we discussed the benefits and
+responsibilities of PMC, and add it to these documents. -->
+ <p>Most discussion happens in the open on the dev mailing list.
+ Only issues which absolutely must be discussed in private, are
+ held on the pmc list (such as some licensing issues).</p>
</section>
</section>
@@ -95,7 +113,7 @@
<p>The Project obtains its strength from the communication of its
members. In order for members to easily communicate with each other, the
Project has a variety of mailing lists. These lists are not moderated
- based on content and anybody is more than welcome to join them. However,
+ based on content, and anybody is more than welcome to join them. However,
you must be subscribed to post to a list.</p>
<p>To reduce the bandwidth demands on everyone, mail should not contain
@@ -103,8 +121,8 @@
as patches) either within the body of the message or provide a URL for
retrieval.</p>
- <p>To join the mailing lists, see our <link
- href="community/mail-lists.html">Mailing List page</link>.</p>
+ <p>To join the mailing lists, see our
+ <link href="site:mail-lists">Mailing List page</link>.</p>
<p>The Project's list fall into the following categories:</p>
@@ -126,9 +144,10 @@
</section>
<section>
- <title>Commit Lists</title>
+ <title>CVS Commit Lists</title>
- <p>The commit lists are where all CVS code commit messages are sent.
+ <p>The cvs list is where all CVS code commit messages are
+ automatically sent.
All committers are required to subscribe to this list so that they can
stay aware of changes to the repository.</p>
</section>
@@ -742,4 +761,4 @@
</section>
</section>
</body>
-</document>
\ No newline at end of file
+</document>