Stephen McConnell wrote:


Federico Barbieri wrote:

That is a group of people 1) legally responsable for the avalon code 2) directly in contact with the board and the community 3) lead and manage the decision making process in the Avalon community. This could not be done by the current Jakarta PMC 'cause 1) they don't want/can't be legally responsable for all the Jakarta code 2) live 2 levels away for the community 3) do not have time and resource to lead and manage every community.

I like that.


Me too - and something I really like is that this happening in conjunction with the Incubator, Apache commons, etc. This makes it much easier for the Avalon PMC to pull in support from other places and deal constructively will the migration and reorganization process .
The only concern left you shold define first the set of projects under the avalon pmc umbrella so you're going to be legally binded only to those projects. If you sign in for projects that will be moved to different pmcs things could get slightly more complicated, not impossible but...

would it be possible to have a PMC without moving URL? I know you don't probally care so much for the domain name but stating that would quite help at least for the infostructure guys.
Its already been made clear that we can maintain all of the existing URLs (comments from Jakarta and Board members) . We don't want to break anything (code or web links) used by our user community - but there is somethinig new emerging - but that's about a "united avalon" identity - which comes back to the PMCs initatial work on charter etc.
what I meant is things should stay in jakarta.apache.org and *only* there. I don't think different domain is a good idea. Mainly because what you're doing here should apply to *all* apache projects and that's just too many names.

On the infrastructure side - are you involved in that at all ?
I have friends... :-)

Cheers, Steve.


--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>

Reply via email to