> Peter Donald wrote: > > > > A thought - someone (was it you???) was talking about having > > a flat permissions to access CVS across jakarta. ie if you
I was talking about something like that - but not across jakarta, but for shared code. I would be -1 for universal flat permissions at this moment - we need to try it first ( let's say for few experimental repositories ). What I think it would be very important is making a distinction between non-commiters who join a project and commiters from other jakarta projects. The current rules require a "significant contribution" or proof to be proposed as commiter. I think any jakarta commiter has alredy made a significant contribution and the bar should be lower - for example he can send a proposal with the intended changes ( for example fixes or better integration with the project he's working on ) and become a commiter if the proposal is aproved. That means someone can become commiter on tomcat if he is a commiter on a different project and propose to maintain the integration ( i.e make sure tomcat works fine with fooBar ) ( one example - some projects have special needs for reloading, or logging ). For example someone from log4j can become member if he wants to implement a logging module that will plug log4j ( of course, all changes are still subject to -1 votes and review by existing members ). > I do believe that if "bar" is meant to be a repository for common code, > then people working on project "foo" will be reluctant to refactor common > code into "bar" unless they continue to have commit rights to that code. Common code is a different issue - and making everyone feel involved with the common code is just one step ( in making more people write, maintain and use common code ). > I think it is a great idea, but I am not going to unilaterally impose my > will on any subproject. If the committers to any subproject vote to expand > their pool of commiters, I would be glad make it so. And reverse - alexandria/gump should be open to all subprojects - since it is shared by all projects :-) > > At each test stage we could expand the notion of tribe (ie I assume > > that velocity and turbine developers would intermix at next stage). > > Until there is only one tribe - Jakarta. Thoughts ? > > I do like the idea of incremental progress towards this goal. +1 Costin
