>> >> I know that you are busy, but I have another idea that came to me reading >> the Matt Benson's post. In fact the guys are >> dealing with a project that seems to be inspired the jakarta commons >> Convert >> project and so it would be possible to >> accept the code without passing through the incubator. So why isnt' this >> situation possible for Cactus (I mean I have refactored existing code and >> added the maven xml files - it is not a new project). >> >> I also agree that passing through the incubator is the best solution >> in the >> great majority of cases, but in my opinion there are still some cases >> (like >> Cactus for instance) that are threatened of stalling even more. > > Martin or others may answer this better - but AIUI one of the two > primary goals of the incubator is building community around code > bases. This is not just a "nice thing" at Apache - its an absolute > necessity. As an example under Apache rules without 3 votes from the > PMC (project management committee) responsible for a project you can't > release anything. Once a project falls below that critical level of > involved people its basically dead in the water as far as releasing > any software goes. In the case of a project like Cactus the main > reason for going back to the incubator would be to re-create a viable > community. >
>From what I understood from current people that have cactus on their radar and >have sufficient "power" to vote, Cactus will be able to get a release out the door. An another note : After incubation it could still be that you cannot get a release out the door if you end up at Jakarta, depending on the fact if you actually make it on the Jakarta PMC. This is also one of the reasons an Incubator project should have 3 mentors, so they can actually release, without depending on the time of people not directly involved. Mvgr, Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
