mcconnell 2002/12/06 10:06:53
Added: . PMC-VOTING-PROCEDURES.txt AVALON-PMC-RESOLUTION.TXT
Log:
See email in thread Re: [Proposal] PMC Resolution Voting Process - 19:XX 06-12-02.
Revision Changes Path
1.1 jakarta-avalon/PMC-VOTING-PROCEDURES.txt
Index: PMC-VOTING-PROCEDURES.txt
===================================================================
APACHE AVALON PMC VOTING PROCEDURES - PROPOSAL
Definitions
----------
Definition 1. PMC
All references to the PMC within this document shall be deemed as
the Apache Avalon Project Management Committee, established in
accordance with the Apache Board resolution of the
20 November 2002 as detailed with the following document or
amendments adopted in accordance with the procedures herein
defined.
http://jakarta.apache.org/avalon/AVALON-PMC-RESOLUTION.TXT
Definition 2. PMC Membership
The PMC membership as established by the Apache Board
resolution as detailed under definition [1]:
Definition 3. PMC Chair
A member of the PCM, as defined in definition [2], duly elected
by the PMC Members to represent the interest of the PMC and the
broader Avalon Community towards the Apache Board as defined under
the PMC resolution and/or adopted amendments (definition [1]).
Definition 3. PMC Charter
The initial charter of the PMC is defined under the Apache Board
resolution as detailed under definition [1].
Definition 4. Normal Vote
Normal votes shall be deemed as any vote not falling within the scope
of a Qualified Majority Vote as defined by definition [5].
Definition 5. Qualified Majority Vote.
A Qualified Majority Vote is a vote applied to any of the following:
(a) Modification to and amendment of the PMC Charter as defined
by definition [3].
(b) modification to or amendment of the policies and procedures
established hereunder.
PMC Policies and Procedures (P&P)
---------------------------------
Article 1, PMC Voting Procedures
(a) Preconditions to Voting
A vote shall be proceeded by prior discussion, normally
initiated by a an email thread commencing by the "[PROPOSAL]"
tag with the message title. Proposal resulting in the
establishment of a vote shall be presented under a thread
commencing with the "[VOTE]" tag. The PMC Chair may disallow
a vote at his/her discretion, providing that justification is
provided. PMC chair decisions on vote integrity shall be
binding on the PMC members.
(b) Quorum Calculations
Quorum on all motions shall be at least three (3) and not
less than 50% of the elected members (rounded up to the
nearest non-fractional number).
(c) Normal Majority Vote
A vote undertaken within the scope of a Normal Vote as defined
by definition [4] shall require a 50% majority before the vote
may be considered as binding, shall be subject to the quorum
calculations as defined under Article 1 (b), vote duration
as defined by Article 1 (e), and validity shall be subject to
reasonable engagement towards actions as defined under the
voting preconditions of Article 1 (a), where the notion of
reasonable shall rest with the PMC Chair.
(d) Qualified Majority Vote
A vote undertaken within the scope of a Qualified Majority Vote
as defined by definition [5] shall require a 2/3 majority
(rounded to the nearest non-fractional number) before the vote
may be considered as binding upon the PMC members.
(e) Vote Duration
Any vote conducted by the PMC may be closed within 7 days of its
initiation providing that quorum has been met in accordance with
Article 1 (b). A vote not meeting quorum during the initial 7
day period shall default to a 14 day duration. On expiration of
a 14 day vote duration, if quorum has not been achieved, the
vote shall be consider as s failed vote.
(f) Post-conditions to Voting
A vote shall be concluded by a result announcement presented by
email under a thread commencing by the "[VOTE-RESULT]" tag with
the message title. The PMC Chair count shall stands as the
final authority on vote counts. Non announcement of a vote
result by the chair within 60 days of the initiation of a vote
shall render the vote null and void.
1.1 jakarta-avalon/AVALON-PMC-RESOLUTION.TXT
Index: AVALON-PMC-RESOLUTION.TXT
===================================================================
On the 20th November 2002, a recommendation based on a proposal placed before the
board by Stephen McConnell on behalf of the Jakarta Avalon Sub-Project community was
unanimously adapted under a vote of the Apache Board. The text of the adapter
proposal is as follows:
WHEREAS, the Board of Directors deems it to be in
the best interests of the Foundation and consistent with
the Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software related to component and service
management, for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Avalon PMC", be and
hereby is established pursuant to Bylaws of the Foundation;
and be it further
RESOLVED, that the Avalon PMC be and hereby is responsible
for the creation and maintenance of software related to
component and service management, based on software licensed
to the Foundation; and be it further
RESOLVED, that the office of "Vice President, Avalon" be and
hereby is created, the person holding such office to serve
at the direction of the Board of Directors as the chair of the
Avalon PMC, and to have primary responsibility for management
of the projects within the scope of responsibility of the
Avalon PMC; and be it further
RESOLVED, that the persons listed immediately below be and hereby
are appointed to serve as the initial members of the Avalon PMC:
* Nicola Ken Barozzi
* Stephen McConnell
* Leo Sutic
* Leo Simons
* Paul Hammant
* Marcus Crafter
* Carsten Ziegeler
* Pete Royal
* Berin Loritsch
* Jeff Turner
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Nicola Ken Barozzi
be and hereby is appointed to the office of Vice President, Avalon,
to serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until death,
resignation, retirement, removal or disqualification, or until a
successor is appointed; and be it further
RESOLVED, that the initial Avalon PMC be and hereby is tasked
with the creation of a set of bylaws intended to encourage open
development and increased participation in the Avalon Project;
and be it further
RESOLVED, that the initial Avalon PMC be and hereby is tasked
with the migration and rationalization of the Jakarta PMC
Avalon subproject; and be it further
RESOLVED, that all responsibility pertaining to the Jakarta
Avalon sub-project and encumbered upon the Jakarta PMC are
hereafter discharged.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
