Leo Simons wrote:
Yes, this last sentence is a very important point.Nicola Ken Barozzi wrote:I think that we should now decide where to put the Avalon components, if in Apache Commons or Avalon Components.
I'm (still) strongly in favour of a _common_ repository for _common_ components, in that all of Jakarta Commons, and Apache Commons, and Avalon Commons, and Turbine Commons, and <whatever> Commons is the same common repository. It Just Makes Sense(tm).
CVS access is not the issue (if it works @ apache as it works for me at work, it is the simple editing of one file). What we need is community unification (to the extend feasible).
<mumble>
My "fear" is that moving these in Apache Commons now is going to destabilize the community.
Now that I write it, it seems probably silly... it could do the opposite.
I was always pro-common-common, but now I have a bit of fear in "relinquishing control" of the components.
</mumble>
Ok, we have explored a bit the possibility of having an Apache Avalon Components project.
What would you guys think about the real possibility of moving our components to Apache Commons?
The proposal would be the same, but under the Avalon Commons project:
"
I think it is important to separate container/framework and
components. I also think that we should use Scratchpad/Components
like Jakarta Commons. I.e.: Any Apache committer should have
Karma for the Scratchpad CVS. The ones actively maintaining
the component code shoul be granted karma to Component.
* That means that *anyone* can do scratchpad stuff.
* It also means that someone who is maintaining components is not
necessarily an Avalon committer.
* It also means that not just *anyone* can alter the released
components--they have to demonstrate the ability to maintain it.
"
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
