jmcnally 2005/08/02 09:15:20
Modified: xdocs management.xml
Log:
bylaw changes voted on Oct 2004
Revision Changes Path
1.6 +34 -29 db-site/xdocs/management.xml
Index: management.xml
===================================================================
RCS file: /home/cvs/db-site/xdocs/management.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- management.xml 4 Feb 2003 17:29:33 -0000 1.5
+++ management.xml 2 Aug 2005 16:15:20 -0000 1.6
@@ -12,14 +12,12 @@
<section name="Project Management Committee Bylaws">
<p>
The Project Management Committee (PMC) was formed by the Apache Board
- on 17 July 2002. The number of PMC seats is set at 5. Annually,
- all five seats will be up for renewal. The ASF board will be asked
to
- provide a person or persons to administer the nominations and a
- subsequent ballot. The administrator(s) will determine the mechanics
of
- the voting procedures. Any committer to any DB code base will be
- eligible to vote. Once the new PMC is in place, the first order of
- business will be to determine a chairperson from amongst their ranks.
- The list of current members can be found in our
+ on 17 July 2002. The bylaws were last amended on __ September 2004.
+ There is no preset number of seats on the PMC. The PMC will strive
to
+ add every committer within DB that, in the opinion of the PMC as
+ determined by a vote, displays the capability and desire to help
guide
+ the DB project. The PMC will select a chairperson from amongst their
+ ranks. The list of current members can be found in our
<a href="./whoweare.html"> Project Credits</a>.
</p>
@@ -41,44 +39,51 @@
</subsection>
<subsection name="Meetings">
- <p>
- The PMC
- <a href="pmc/index.html">meets monthly</a>
- 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.
+ <p>The PMC discusses issues and determines strategic direction via
mail
+ list. All binding votes happen on the PMC list.
</p>
</subsection>
<subsection name="Membership">
<p>
- 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
+ PMC members may resign at any time. A committer will remain on the
DB
+ PMC until removed by desire of the committer, action of the board,
or
+ vote by the PMC. The Chairman may resign as Chairman at any time
+ without resigning membership to the PMC. The chairperson will
serve
+ until voluntary resignation, action of the board, or vote by the
PMC.
+ The Chairman or any member may be removed from the PMC by a 3/4
vote of the PMC.
</p>
<p>
- In the event that the number of members drops below 5, the
remaining PMC
- members may choose to elect a new member to serve out the
remainder of
- the annual term. In order to be elected, a
- person must have served as a
+ In order to be elected to the PMC, 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.
+ nominated by a PMC Member. The nominee must receive 3/4 positive
vote
+ with a minimum of 3 positive votes. Abstaining PMC voters do not
+ affect the result.
</p>
</subsection>
<subsection name="Creation of Subprojects">
<p>
- PMC members may propose the creation
- of new subprojects. Proposals are to contain the scope of the
project,
- identify the initial source from which the project is to be
populated,
- identify the mailing list(s) if any which are to be created, and
- identify the initial set of committers. Creation of a new
subproject
- requires approval by 3/4 vote of the PMC.
+ PMC members may propose the creation of new subprojects. Creation
of
+ a new subproject requires approval by 3/4 positve vote with a
minimum
+ of 3 positive votes of the PMC. Abstaining PMC voters do not
+ affect the result. New code enters the DB project in accordance
with
+ ASF policy.
+ </p>
+ </subsection>
+
+ <subsection name="Voting">
+ <p>The call for a vote on issues not detailed here may specify
+ requirements for passage. The minimum and default requirement for a
+ passing vote is simple majority of PMC members casting ballots.
+ The default voting period is 10 days and the minimum is 7 days unless
+ the success or failure is arithmetically known.
</p>
</subsection>
+
+
</section>
</body>
