Hi, I like the idea but can we let it incubate for a bit. There is large number of changes that are currently going on in Apache. I think we will find that large chunks of Avalon will move to either the incubator.apache.org or commons.apache.org projects. In both of these cases it will just take time.
In some of these cases the specific components when they move may also take some of the Avalon services. ie Currently Extension is void of references to Avalon, it may be that we migrate the service back from Phoenix into Extension toolkit when it moves to commons.apache.org. So in this case it may be best to instead have a registry of services for Avalon and allow people to pick them up from different places as they desire. There is also the problem of interoperability. Not all the components are interoperable. Some are restricted to Phoenix, some are restricted to Cocoons ECM/Fortress managers and some are generic. Some will also presumably be specific to Turbines container. One of the things that will hopefully fixed over the next year will be these interoperability problems. However until then it may be best to avoid such a global repository. However in the meantime if there is any Turbine committers who want to have access to any avalon repos then just say the word and we can try and work something out. On Thu, 24 Oct 2002 19:42, Nicola Ken Barozzi wrote: > 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. -- Cheers, Peter Donald -------------------------------- These aren't the droids you're looking for. Move along. -------------------------------- -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
