Peter Donald wrote:
On Thu, 24 Oct 2002 11:20, Morgan Delagrange wrote:
Someone who edits a single javadoc shouldn't vote, but
someone who cleans up all the documentation should.
Someone who fixes a typo in an excecption shouldn't,
someone who fixes exception handling should. Someone
who fixes a single significant bug should, shouldn't,
who knows?
It is up to the components maintainers/developers.
Yes, now I agree. It's not up to the committers.
They are the people who are in the best position to judge whether a candidate should be given voting rights. Some may choose to be more exclusive and some may be a free for all - however it will always be the develoeprs who decide where their component evolves.
Yes, developers of the component, and mind me *not* the _original_ developers, but the ones active on it ATM and the ones that have more heavily been involved in it.
For example, Stefano's -1s and committs in Cocoon are never seen as intrusion even if lately he hasen't touched the code much, because of the *massive* effort that he has put in it in all these years, not just because he designed it.
Likewise, Peter rightly didn't like my stupid -1 on his code.
I dodn't help make it, I didn't even know it as he does, what right did I have to stop him, *even* if I has what I *thought* was a better technical alternative?
After all, it's not only about better technical stuff, it's also about legacy, history of failed tried, and most important of who makes those damn fixes and *maintains* them.
Before coming into Avalon
I had never worked in a multi-component project; the others I had been in are mostly monolithic or I know them all for some time.
For the first time I found myself not knowing parts of the codebase in a multi-component community, and got confused.
But gee, I think I got it well now! :-D
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------