El sáb, 10-05-2008 a las 12:50 +0200, Chris Chabot escribió: > Note that we pinged the list a few times with the question if we are > able to have sub-projects right now while being in incubation, but > haven't heard back from our mentors yet.
I don't think there are hard rules. The main issue is one of oversight. There used to be a lot of discussions about subprojects and TLP (Top Level Projects) at Apache, mostly due to the fact that jakarta, and also xml, were big "umbrella" projects with lots of unrelated subprojects (the only commonality was java/xml resp.) and this fact was hampering oversight by the board of what was going on. Nowadays the only big umbrella project remaining is the incubator, and it is designed so as to have high visibility of podlings. I'd say that, while subprojects/submodules are well scoped and have the same core set of committers, they won't pose big trouble. Now, if the number of common committers starts to diminish it will start to be troublesome, and possibly a concern for graduation. Now, I don't really have big experience at the incubator and I'm speaking out of whatever common sense I have. I'd love to know if there are more specific "hard" rules. Regards Santiago > > For now, pending feedback on this, i've spun off the php db driven > sample container to its own code.google.com project, I'm not sure if > that would be the right thing to do with the html/xml driven > samplecontainer :) > > -- Chris > > On May 10, 2008, at 12:31 PM, Kevin Brown wrote: > > > It seems like a good thing to have as a sub project, much like > > the various DB-driven implementations that have been floating around. > > Thoughts? > -- Santiago Gala http://memojo.com/~sgala/blog/
