Leo Simons wrote:
Hi Leo: Some in-line comments relating to scope and the question of PMC Chair ...
PROJECT SCOPE
-------------
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
here, the wording is very important I think. loose comments: - there is no mentioning of Java; which is good IMO: it allows for the C# impl for example
That was the intent.
The putting in-place of a charter is a post resolution action. I.e. once the Avalon PMC exists, it can work on definition of the charter.- there is no mentioning of the project being about design and documentation (which is in the current charter); I dunno whether there should be
- what constitutes a component or a service is vague and will be more vague in the future; can't think of an alternative right now - what does 'management' mean? MX4J is about one kind of 'component management'....
A charter can further qualify that defintion.
In my opinion its a correct assessment of the implications of the scope statement.Things going out-of-scope ------------------------- There is no longer any kind of mention of a shared module repository. This means that all current avalon-hosted 'shared modules' should be eventually placed under the control of a different PMC. Likely candidates for this are - the Apache Commons PMC - the Incubator PMC - the Jakarta PMC - a to-be-created PMC when code is to remain under control of the Jakarta PMC, it is likely to be placed in the Jakarta Commons subproject; alternatively, a new Jakarta subproject could be created to host it. Given current restructuring taking place apache-wide and the attempts at slimming down Jakarta, I think the last option is unlikely. how the code will exactly end up when donated to and accepted by Incubator and/or Commons is not quite clear yet. Both projects have an active avalon committer on the PMC (Nicola resp. Peter) and are amendable to taking in some of the stuff currently in the Avalon subproject IIUC, so things should go as smoothly as possible :) A to-be-created PMC could be the best way to manage some of the biggest and mature largely avalon-independent codebases we currently have or some of the full-fledged applications we currently host (ie a Logkit PMC). Note the code that will go 'out of scope' under the current wording is _a lot_, which I think might roughly include: - all of jakarta-avalon-apps, save the demos - all of jakarta-avalon-cornerstone - all of jakarta-avalon-logkit - a lot of jakarta-avalon-excalibur thus leaving just - jakarta-avalon - jakarta-avalon-phoenix - parts of jakarta-avalon-excalibur This is not neccessarily bad (I think it's a real good idea :), but an important implication of the current wording to point out.
MEMBERSThe resolution requires that a chair be named. Towards this end, I would suggest that committers who want to include themselves on the PMC, also make it know if they are willing to serve as chair. If nobody wants to take this on, I will voluntee for the job, however, I think that there are better candidates on this list. In the longer term (post establishment), I think it would be an interesting idea to rotate the chair - i.e. a three month duration, then over to someone else from the PMC (could be benefital in building awarness and contacts with the Board, and greater sence of community).
-------
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.I think we should have an opt-in list for current avalon committers. I
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/>
believe the defacto emeritus committers or the not 'active' committers
will be responsible enough to not opt in, and furthermore believe having
a PMC composed of the committers is a good idea.
I think that should a committer wish to challenge the opting-in of
anyone on this list, such challenge should be made via private e-mail
between all committers, and not on avalon-dev.
Current proposed <list-of-people/> (in no particular order) based on
opt-in:
* Nicola Ken Barozzi
* Stephen McConnell
* Leo Sutic
* Leo Simons
* Paul Hammant
An alternative is opt-out, but we then place an obligation on people
like Fede and Jon to respond...whom I am guessing don't want to be on an
Avalon PMC.
CHAIR
-----
This resolution is the appointment of PMC Chair, and the appointment of that individual to the post of Avalon VP.How to decide who we would like to be the Chair/VP is not clear to me.
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
Should we even make a recommendation or is this something the board will
figure out on its own?
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>
