I think we should be rigid with the six months of patched contributions before granting commit/vote rights to Avalon. It may appear rude to Stephen Colebourne and Dmitri Plotniko, but we have no idea who they are, their character etc. A normal get to know you period with a normal script leading up to invite is appropriate I think.
- Paul
I would like to move forward with a joint initative between the Avalon Dev. Team and the Jakarta Commons [clazz] guys to work up an implementation of an Avalon meta model for component and service defintions. I've already spoken to Stephen Colebourne and Dmitri Plotnikov (committers on the [clazz] project) and there both keen to work with us on this. From their point of view is about validation of the [clazz] package against real requirements, and from our point of view is about validation of the [clazz] package and delivery of a standard Avalon meta solution.
To kick things off I have in mind the following:
* granting commit access to Stephen and Dmitri so they can work on a sandbox project
* reciprical commit rights for concerned avalon committers to the [clazz] project
so we can work on clazz (doc enhancement, unit test, debugging, etc)
Enabling co-development on a meta model implementation, leading to:
* validation and grounding of the [clazz] package based on our requirements
* consolidation of current meta solutions under a single unified object model
* capable of supporting mixed loading strategies
* capable of supporting model extension
Before moving forward on this, I wanted to get feedback from people concerning the commit access exchange which doesn't follow the normal model. However - there is plenty of evidence in the clazz project itself that these guys know what they are doing. Secondly, this also means voting here and there, so first of all I'll like get an idea of who here are sufficiently interested in this to actually contribute.
Cheers, Steve.
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
