On Sat, Apr 11, 2009 at 10:22, Niclas Hedhman <nic...@hedhman.org> wrote: > On Fri, Apr 10, 2009 at 6:32 PM, Torsten Curdt <tcu...@apache.org> wrote: >> Well, the point is: we are talking about small libraries. >> >> Imagine there is library X which was developed by only 2 developers. >> They want to bring this code to Commons. What to do? IP clearance is >> one thing. But what about the 2 developers? Just make them committers >> while they have no clue about Apache? Doesn't sound like a good idea. >> Just accepting their code and make them send patches until we feel >> they are ready? Feels not appropriate since they are the authors of >> the code. On the other hand going through the "normal" incubator is a >> bit over the top for a project that is so small that it is not >> targeting to become it's own project. Building a community is not >> really that applicable in this case. It's rather about integrating it >> into an existing community. > > Careful now, you are sinking your own proposal with your arguments.
Not at all. You are mixing things up :) > 1. The proposal says that there is no need to build a community, since > the entire Commons community is there to make sure everything is Ok. Indeed that is the case. > 2. You say that you can't just make them committers, insinuating that > the Commons community will NOT be there to make sure everything is Ok. No - that is just you saying that :) There is a difference between having oversight and training people in the Apache way. This is not the same thing. If other projects get new committers through bulk contributions and train them later... Well, then that is suboptimal from my perspective. Any future committer has to learn the Apache way "the hard way". Just throwing some code at us doesn't make them understand. And this is were this approach falls down for us. I personally have not experience with such contributions "thanks for the code *magic wand* now you are also a committer". Either the new people have been around long enough so making them a committer soon after the code contribution was a non-problem or they sent patches until we felt they are ready. But hey - might have been differently for other projects ...not that I would be very happy about it. The incubator approach just doesn't work well for projects that have a very small scope and user base IMO. The current incubator is about establishing a project. We rather would to like to have something that helps integration into an existing project. cheers -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
