On Thu, 2002-12-05 at 14:34, Peter Donald wrote: > There some like me who can no longer contribute. I am still not really clear > on why my cvs access was removed - however it was and is unlikely to be > returned. It seems like Nicola has decided that I no longer have other rights > such as voting rights. So there is little chance of influence there. All in > all my ability to contribute has been mostly removed.
I count and respect your votes. I'm not sure what the idea is wrt how they should be counted "officially" and I hope it won't need to be an issue. I don't know what the best way is to clarify this issue; probably you contacting the board? I value your input (as I've said before) and I am happy to apply patches you send. Nicola hasn't decided anything wrt to your voting rights. He hasn't made any opinion on this matter public. Regardless, he won't be acting on such an opinion unless it's shared by the community. (or else..... ;)) > However by far the biggest problem is that many people are not here purely for > the benefit of Avalon as a whole. as long as those people are either here for the benefit of apache as a whole, or their actions are not detrimental to apache as a whole and/or avalon as a whole, I don't think that's a problem. I'm also here for my own benefit, definitely. I learn lots of stuff everyday here. I don't think this is a problem. > - how long have we needed to move to maven for our builds. we do? > I know of at least > three different committers who have expressed a desire to move towards it but > are reluctent to propose it because they will be jumped on by Nicola. if this is true, let someone contact me privately and I will propose it once I understand the need. I think it is very bad (and also unfounded) that anyone should be afraid of being "jumped on by Nicola" and we need to remedy that. Probably the best way is by example. > - look to how Stefano acts like a tool everytime someone mentions anakia or > says Cocoon is not the brightest star in the sky. whatever. Stefano's reaction I've seen, when someone mentions cocoon is not the brightest star in the sky, he responds along the lines of "perhaps not, but the community is real healthy and there's lots of potential". Good reaction. > - look at conflict between info/meta. Info is technically a far better choice I think there's disagreement in that area. Let's hold that discussion as part of the next-gen development and make a community decision. > but there is little chance of going wit it without massive conflict/FUD. > There are two people who have said to me that they will block it regardless > of technical merit (and neither was Stephen). I sincerely doubt that would or will happen. > Personally I think that *all* decisions should require the consensus of *all* > committers. ...to the maximum extend possible. Totally agreed. And non-committing interested parties too if possible, btw. > We have always gone out of our way to allow and encourage experimentation and > except for more recent times there has never been code ownership for these > experiments because it was always assumed that the group "owned" the code. > And the experiments always assumed that if successful they would be > reintegrated or built upon or whatever. When new people start to associate > these experiments with so heavily negative concepts (aka forks and code > ownership) does that not indicate to you that there is problems. yes. > Removing all one man code bases would effectively fix the problem in many > ways. If you have a better idea then please share. here's one: remove the code ownership perception. Go out of our way a little extra to make sure future development does not suffer from "code ownership" issues. Start with a fresh base developed together so all past notions of code ownership perception are completely removed. cheers, - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
