Sam Ruby wrote: > > Federico Barbieri wrote: > > > > My fear is that if you open the commiters group of a project, > > those in that project's tribe who feel "ownership" on the code > > will mainly be pissed of by "strangers that want to mess with > > my code" and will probally develop a very uncostructive > > attitude. To allow cross development trust is the key factor. > > You have cvs write access becouse we trust you. And we trust > > you becouse we know you since you've been around enough to > > prove your skills. > > I was very surprised the first time that somebody updated "my" code in PHP. > At first, I didn't know what to think. Then I realized that that person > had made an incompatible change to something I depended on, and fixed my > code to be in synch. Over time, I saw that the number of changes to "my" > code made by others approached the number of changes I made. Mostly these > changes were the correct ones, in a few circumstances I had to make a fix, > and in one case I even remember somebody making an incorrect fix with > somebody else fixing it. > > I very much like Peter's approach of incrementally addressing this. >
I totally agree that's the goal. I WANT people to share ideas and code and I'm just happy to see people working on the same code I work on. I don't feel any ownership on code... damn what's open source about? My point was ment to underline that in my personal experience if someone feels he "own" something the worst thing to do is to make him feel like his "propriety" is in danger. That will probally push him in a defensive attitude that is very unconstructive. I'm positive most jakarta developers are smart and will happily open their code to new commiters as well as I'm sure none will commit code to screw up others people work but I'm positive too there will be people very suspicious about such extension. Suspect is the oppisite of trust and can ruin the spirit of collaboration. That's why I'm saying: yes, the path is the right one but we should first create the need for collaboration and encourage it, then open doors. > BTW - I assume that you are using the term "you" in the generic sense. I > don't have cvs write access to avalon currently. I actually have authority > to give myself permission, but I don't intend to abuse that priviledge. absolutly. It was a genric "I" from someone that lives in a close tribe. You have not been around avalon so long... :-) > Again, I don't wish to impose my will upon anyone, I would rather have > everyone come around to my way of thinking on their own. ;-) That's my point... opening cvs write to everyone may feel like an imposition. The best way IMHO it to prove it can be done, prove it better the code, show the path to others who wants to follow. Fede
