[PROPOSAL] Avalon Component repository in Apache Commons

[Nicola Ken Barozzi]

Dear Avalon and Turbine Community,

following prior discussions I had with you, I'm writing here to make a proposal about a common codespace.

Turbine services will most probably become Avalon Components/Services (C/S), and Avalon already has a lot of them too: currently they are in Cornerstone and Excalibur.

Using a common framework will bring us closer, and will make it possible for us to _finally_ share code in terms of C/S.

As history has showed me, external projects that use Avalon Components are happy to be able to offload their maintainance, but this is only when all works well... I'm sure that many users of these components would be happy to be involved more directly in the management of their code.

I think that if Turbine devs could interact more directly with the code of existing Avalon C/S they would use _them_ instead of making another version. Likewise for Avalon devs.

Thus I propose that we create our dev-space about Avalon-based C/S inside the new Apache Commons Project, and be able to share commit privileges between our committers on a per-component basis.
This is to enable collaboration without the fear that yet-unknown committers will step all over our code.

This has been already proposed on the Apache Commons list and seems ok.

If you want to partecipate in a common discussion about this:

[EMAIL PROTECTED]

Thank you.

--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------


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