The barrier is the policy and procedures that are put in place.
I've mentioned before (on the PMC list) that I would like to see a soft zone here in Avalon supporting and facililitating component development and experimentation.
<snip/>
My own opinion is that we need a new CVS repository - avalon-playground.
What's the difference between avalon-playground and avalon-sandbox - simple - things in playground are not destined for Avalon - its simply an infrastructure to support and enable people who want to do new things. What is the exit criteria for playground content? Its the development of the individuals who come to play.
I.e. Avalonia - the center for component developer development.
It seems you've nailed down the root of the difference in opinion -- you want all these things to happen inside the scope of avalon (and under responsibility of the Avalon PMC), whereas I think that's not a good idea.
The rest of the argument seems mostly about quantity (in its most general sense), which is not very productive.
Perhaps we should just do a vote on avalon-playground. If it goes through, no avalonia. If not, you'll have to recognize the next best thing is something hosted at SF.
There's no point in doing this avalonia thing if the whole of avalon is not on board. In fact, there may not be a point in doing this at all; I just read my [EMAIL PROTECTED] backlog, and it seems there's half a dozen similar efforts underway atm. I'm going to wait out what spice-repository, [EMAIL PROTECTED], avalon-sandbox/repository, ruper, maven, etc, amounts to.
Just goes to show how badly a component repository really is needed :D
- LSD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
