Hi everyone:
Following on fro the Avalon PMC thead, I spent a good part of last night reading through a bunch of the PMC chartering proposal in the board minutes (http://www.apache.org/foundation/board/calendar.html) and based on that content, I've put together a draft resolution for discussion. I think it is useful to circulate this draft as early as possible for two reasons - firstly, there is the subject of scope that is central to the Avalon community; and secondly, the Apache Board Meeting is on the 18 ... i.e. eight days from now.
Working forwards from today:
Sunday 10 November (today)
* Start discussion on a resolution
Wednesday 13 November
* Finalize a resolution
* Incorporate feedback from the Apache Board
* Close the list of named PMC members
* Naming of the Chair
Thursday 14 November
* Initiation of a [VOTE]
* Majority vote limited to Avalon comitters
* 72 hour vote (3 day) duration
Saturday 16 November
* Vote count and notification of results.
Sunday 17 November
* Formal submisssion to the resolution to the board.
Monday 18 November
* Apache Board Meeting
As you can see, we have basically four days to discuss and turn over a proposal. Within that time we need to sort out a nomination for proposed chair, and get the list of potential PMC member established.
To kick off this process I've prepared an initial draft of a resolution for the formation of an Avalon PMC. In the following text the formal resolutions are indented and proceeded by a non-legal summary outlining the purpose of each resolution. Where relevant I've attempted to indicate resolutions that are more administrative in nature as opposed to resolutions that are more directly relevant to the Avalon community.
====================================================================
DRAFT RESOLUTION FOR AN AVALON PMC
====================================================================
The draft resolution starts of with a boilerplate context statement.
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.
The first resolution handles the establishment of an Avalon PMC as a formally recognized entity within Apache.
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
This resolution declares the scope of the Avalon PMC. This resolution is directly relevant at an operational level because it restricts the scope of our activities. The key phrase is "component and service management".
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
This resolution creates a new board position of Avalon VP which ensures that Avalon is represented at the top-level of Apache, and that the board, through the VP, can assure accountability of the Avalon PMC and project.
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
The next resolution is the appointment of the Avalon PMC members. This resolution is important for a number of reasons - it provides a higher level of legal protection to members than available to a committer, and, it declares the set of people who will ultimately address the tasks handed down by the board (definition of structure, code migration, rationalization, etc). The intent is to include the spectrum of active committers on Avalon. Suffice to say, if your a committer and you want to get engeged in the future of Avalon, please include your name below. Based on posts on the Avalon PMC subject from yesterday, it is safe to assume that the list already includes Nicola and myself. I would also like to see representatives from both the Jakarta PMC and the Incubator PMC, at least during the initial transition period.
RESOLVED, that the persons listed immediately below be and hereby
are appointed to serve as the initial members of the Avalon PMC:
<list-of-people/>
This resolution is the appointment of PMC Chair, and the appointment of that individual to the post of Avalon VP.
NOW, THEREFORE, BE IT FURTHER RESOLVED, that <name-of-chair/> 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
The next three resolutions are directives from the board. Two of these resolutions concern the Avalon PMC and one resolution concerns the Jakarta PMC. The first of these directives is largely boilerplate content that covers the establishment of a functional structure. I would expect to see the policy/bylaws side of this largely driven by the work on-going within the Incubator project.
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
The secondary directive is based on an interpritation of the board requirements based on Greg's recommendations and Nicola's comments from yesterday concerning Jakarta Avalon content migration and rationalization.
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
The final directive releases the Jakarta PMC of its responsibilities related to the Jakarta Avalon sub-project.
RESOLVED, that all responsibility pertaining to the Jakarta
Avalon sub-project and encumbered upon the Jakarta PMC are
hereafter discharged.
Ok, fire away :-)
--
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>
- Re: [PROPOSAL] Avalon PMC Draft Resolution Stephen McConnell
- Re: [PROPOSAL] Avalon PMC Draft Resolution Peter Donald
- Re: [PROPOSAL] Avalon PMC Draft Resolution Stephen McConnell
- Re: [PROPOSAL] Avalon PMC Draft Resolution Leo Simons
- Re: [PROPOSAL] Avalon PMC Draft Resolution Stephen McConnell
- Re: [PROPOSAL] Avalon PMC Draft Resolution Nicola Ken Barozzi
- Re: [PROPOSAL] Avalon PMC Draft Resolution Leo Simons
- Re: [PROPOSAL] Avalon PMC Draft Resolu... Nicola Ken Barozzi
- Re: [PROPOSAL] Avalon PMC Draft Resolution Stephen McConnell
- Re: [PROPOSAL] Avalon PMC Chair Stephen McConnell