Peter Donald wrote:
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.
Yes.
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.ATM it's *definately* a good idea :-)
So, where do we set up the common page about all Avalon available components?
IMHO on the commons.apache.org site, along with the statement that collaboration is in place for a common repository to happen.
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.Hmmm, probably... or the problem wil always exist.
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.
I'm hesitant when having to wait because "the next big thing" will eventually happen...
Many problems will go away, but other problems will emerge, because each solution brings its own problems.
IMHO we should not be concerned about the interoperability problems on the common repository; assume that Phoenix wants to use a Cocoon component, and cannot because of interoperability.
It will try to work it out. So it will probably become interoperability from evolution, from the bottom.
A common page with references to the components is certainly a big first step, but interoperability should not stop us from planning the details of the project, the rules, the management.
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.:-D Cool! +1
Also, there is an Avalon Component done by the OBJ team, that has been proposed to me privately for the eventual Commons Avalon repository.
Now, what should be best:
1) let them keep it and reference it
2) accept it in Avalon
3) put it in Commons
I'd go for 1 for now, what do others think?
--
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>
