crossley 2003/10/19 05:55:57
Modified: src/documentation/content/xdocs guidelines.xml
Log:
- Merge duplicate stuff about binding votes.
- Other minor text tweaks and re-wording.
Revision Changes Path
1.10 +11 -15
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.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- guidelines.xml 19 Oct 2003 09:16:08 -0000 1.9
+++ guidelines.xml 19 Oct 2003 12:55:57 -0000 1.10
@@ -3,7 +3,7 @@
"document-v12.dtd">
<document>
<header>
- <title>Cocoon Project Guidelines - DRAFT</title>
+ <title>Apache Cocoon Project Guidelines - DRAFT</title>
</header>
<body>
@@ -90,7 +90,7 @@
<title>Project Management Committee (PMC)</title>
<p>Any Committers who desires to participate can join the PMC
- mailing list to become a member of 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.
@@ -118,9 +118,8 @@
you must be subscribed to post to a list.</p>
<p>To reduce the bandwidth demands on everyone, mail should not contain
- attachments. It is recommended that you place interesting material
(such
- as patches) either within the body of the message or provide a URL for
- retrieval.</p>
+ attachments. Please consider using the project's issue tracker or
+ provide a URL for retrieval.</p>
<p>To join the mailing lists, see our
<link href="site:mail-lists">Mailing List page</link>.</p>
@@ -201,7 +200,7 @@
<p>Long term plans are simply announcements that group members are
working on particular issues related to the Project. These are not
voted on, but Committers who do not agree with a particular plan, or
- think that an alternative plan would be better, are obligated to
+ think that an alternative plan would be better, are obliged to
inform the group of their feelings.</p>
</section>
@@ -272,7 +271,7 @@
<title>Action Item Votes</title>
<p>The act of voting on an action item carries certain obligations.
- Voting members are not only stating their opinion, they are also
+ Voters are not only stating their opinion, they are also
agreeing to help do the work.</p>
<p>Any Contributor or Committer ("member") may call for an
@@ -313,8 +312,11 @@
</tr>
</table>
- <p>Votes cast by the subproject's Committers are considered
- "binding". When needed, at least 3 binding +1 votes are
+ <p>Anyone may vote on any action item or related issue. Only votes
+ cast by the subproject's Committers are considered
+ "binding".
+ All binding vetos must also contain an explanation of why the
+ veto is appropriate. When needed, at least 3 binding +1 votes are
required for action-item approval.</p>
<p>An action item may need one of two types of approval:</p>
@@ -339,12 +341,6 @@
is posted. Once a -1 reply is posted, the vote must be tallied and
reported before the action item is considered approved. All
action-item votes are lazy except for a public release vote.</note>
-
- <p>Any member may vote on any action item or related issue. When
- voting on an action item, the subproject's Committers may also
- include the word "binding" next to their vote, to simplify
a
- tally if it is needed. All binding vetos must also contain an
- explanation of why the veto is appropriate.</p>
</section>
<section>
