On 3/3/06, Allen Gilliland <[EMAIL PROTECTED]> wrote: > > The Apache Roller project can certainly ship different modules or > > applications like Roller Admin Console, Roller Planet Server or even > > Roller Blog Client. > > Nope, that's not what I was suggesting. I am more than happy to keep it as > part of the > Apache Roller project and just keep it in its own place, like the way the > sandbox works. > > I suppose the one nice thing about it being its own project is that then it > would be easier > to recruit interest in it, but that's not what my original intentions were.
A common term for this idea is "subproject". Apache iBATIS, for example, has separate subprojects for the Java nd C# implementations. Each has its own release cycle, but both implement the same general set of features. Likewise, Apache Struts considers each of our products a separate subproject (Action, Shale, Action2, Tiles). The idea of being able to "take the banana without buying the gorilla" is very important. It''s why Jakarta Commons is so popular. The key is to remember that it is still one project with one PMC and one set of committers. If a person hooks up with Apache Roller because of an interest in Planet, that should make them a Roller committer too. They might not be interested in Roller now, but everyone should stll have the same karma. Just being able to deploy Planet sounds like a fine idea. I'm sure many people would like to setup a aggregator without going into the blog business. For example, I might have done that with Planet Struts, and then put the news blog somewhere else. * http://www.planetstruts.org/roller/ (Though, it seems that I still haven't got the aggregation feature setup right.) -Ted.
