Re: [PROPOSAL] Avalon PMC Draft Resolution

[Stephen McConnell]

Afternoon everyone!

Based on traffic over the list from yesterday, here is the updated draft Avalon PMC proposal included at the end of this email. The proposed PMC members that have declared themselves as willing to serve as chair are marked as chair-candidates.

A draft version of the resolution was submitted yesterday to Greg for verification. I received confirmation early this morning that the resolution in its current form is satisfactory. Greg requested that I include a note to the board concerning the project charter on submission of the proposal given the "mushy" nature of the scope statement. Given that no alternative scope proposals have been made and based on Greg's feedback, I am confident we will be able to undertake the further refinement and qualification of this under a formal project charter as we proceed. Thereby addressing the points raised by Pete on this subject earlier today, and addressing Greg's comments on the same topic.

There is an open point raised by Pete's suggestion that we modify the resolution text to the restriction the software base managed by the PMC to that owned by Apache as opposed to the software licensed to Apache. This particular section is boilerplate text as such I'm hesitant to propose and re-validate a change without first establishing consensus on the necessity for this. I would appreciate your opinions on this point.

On the subject of timing, it appears that we have managed to capture the attention and engagement of the active committers within the Avalon community, as evidenced by the proposed member list. Issues raised appear to focussed more towards the subject of approaches to rationalization and thoughts pertaining to a more complete charter. Responsibilities to address both of these concerns are explicitly addressed within the proposed resolution. Fortunately, the details of these topics are outside of the immediate scope of the proposal but are nether-the-less important subjects that I expect will engage everyone in a lively debate as we move forward.

Based on Leo's email concerning our obligations (or more correctly non-obligation) on chair selection, I have eliminated the action from the schedule. With this item out of the way, with verification complete, broad engagement of the community as evidenced by the list of proposed members, I do not see any justification for delaying the process.
As such, actions that would need to be concluded between now and tomorrow midnight GMT are listed below:

* Any additional finalize of the resolution
* Incorporate any additional feedback from the Board
* Close the list of named PMC members

Based on the proposed schedule, the vote on submission of the Avalon PMC proposal to the Apache Board would be initiated at midnight (GMT) Wednesday 13 November, closing midnight Saturday 16 November. It is a majority vote restricted to committers. A vote count based on yes (+1), no (-1), or abstain (+-0) for submission of the proposal will be based on responses to this list and a count notification should be issued to the list on Sunday. If the vote is successful, the proposal would be submitted to the Apache Board as early as possible Sunday.

The complete proposal is detailed below:


====================================================================
DRAFT RESOLUTION FOR AN AVALON PMC
====================================================================

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 (chair-candidate)
* Stephen McConnell (chair-candidate)
* Leo Sutic
* Leo Simons (chair-candidate)
* Paul Hammant
* Marcus Crafter
* Carsten Ziegeler
* Pete Royal
* Berin Loritsch (chair-candidate)
* Peter Donald (chair-candidate)
* Jeff Turner


NOW, THEREFORE, BE IT FURTHER RESOLVED, that <candidate> 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.


Cheers, Steve.

--

Stephen J. McConnell

OSM SARL
digital products for a global economy
mailto:mcconnell@;osm.net
http://www.osm.net




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