Federico Barbieri wrote:
IMNHO no. There was a discussion on [EMAIL PROTECTED] that told us that we need to be PMC members to have legal protection from the ASF.Nicola Ken Barozzi wrote:Federico Barbieri wrote:Berin Loritsch wrote:I am glad we are finally considering a true Avalon PMC. I have long thought that we would be a good candidate for a top level project, maybe even more than one. Other than standard legalese for all PMC charters, we should look at what we explicitly desire for the Avalon PMC.
I see you all agree on this and I'm happy the Avalon community is strong and united but...
IMHO there is not *one* single reason why creating an Avalon PMC and moving discussions from here to there would make things *any* better. It's Yet Another Mailing List.
It's about direct accountability to the board. This is what we *have* to agree on in any case, the PMC is just a tool. " ... RESOLVED, that the initial Avalon PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Avalon Project; and be it further RESOLVED, that the initial Avalon PMC be and hereby is tasked with the migration and rationalization of the Jakarta PMC Avalon subproject; ..."
So, if I'm getting this right, you want more control, more indipendence over the rules governing the avalon (at large) community right?
This would also make us be accountable directly, and report directly to the board.
I quite agree on that thou I would prefer to see a proposal to improve the community sent to the Jakarta PMC to be voted and adopted by the whole jakarta (or apache) community.It has nothing to do about us wanting more freedom or our own pet rules.
The ability to set up new cvs modules like [jakarta-avalon-*] could (I'm not saying it is) be a good thing for all projects.
If you want to modify commiter access rules just do it. None will ever complain if you are more efficient and productive.
Facts have shown that we have already fragmented stuff (too much?) and created non-written rules.
My guts tells me there is too much burocracy and politics in this... damn it it's open source! It's self determination by definition! There is no need for institutionalisation.
Then why "Apache" at all? <dizzy>
Ok I sound like ranting now... it's just that I'm sorry to see weeks of (code wise) unproductive discussion.
Two weeks? How long have you been away? ;-)
The feelings are correct, but there is some background you're probably not aware of. This PMC formation is completely different from what it would have meant only one month ago.hope I'm making sense...
I would have agreed with you at that time, the reasons currently are different and based on the reorg discussions.
--
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>
