IMHO Avalon could benefit from a common place where it can store common
Avalon components, and share their development with the component users
without having to involve them in discussions about the core on the
avalon-dev list.
We now have a sub-project called Cornerstone and one called Excalibur,
but the impression I'm having is that other projects, like James or even
Cocoon for example, /sometimes/ don't feel involved in helping the
original Avalon developers making them better, and I can understand the
frustration of feeling more than two steps away from the code.
Moreover, now Turbine is slowly but steadily AFAIK moving towards using
the Avalon framework, and they will end up with a repository of Avalon
components.
A quick mail sent to the Turbine mailing list some time ago about a
possible common Avalon Component repository got good reception, and IMHO
it could really be a *concrete* common code repository.
In essence, it creates more cooperation between projects that create the
components, between the creators and the ones that use them, and be a
comprehensive repository where users can pick.
I have not a concrete proposal to these projects yet (note: I'm also an
Avalon developer but i speak for myself); wanted to know what you others
think of this.
Thanks.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
