I tend to agree with both of you somehow :) Now, I totally agree with Ralph that it would make sense to move this to a more "common" place, but as Reinhard I'm very hesitant against such a move. I proposed several years ago to move some common stuff (parser, source resolver etc.) to excalibur which was back then a great idea. Today it turned out that this move brings us more problems than it did help us over time.
So today I think we should host the first versions as a sub project at Cocoon and do some marketing for it. This should buy us some users from outside of Cocoon. If it is a separate project, I guess people do not really care if it has a "cocoon" or a "commons" namespace. One advantage could be that people start to look at Cocoon as they're interested in this common stuff and perhaps we can over more interesting pieces so Cocoon as a whole gets more interest again. Carsten Ralph Goers wrote: > I think you are comparing apples and oranges. Personally, I think there > would be a lot of interest in anything related to Spring. I know I do > for what I am doing at work. However, it would be much easier, > politically as well as practically, to leverage it if was outside of Cocoon. > > As for Excalibur, I'm not sure if you are really referring to the Avalon > problems or if you consider the current Excalibur to have failed - even > though it isn't quite dead as I still get emails from time to time. If > it is really Excalibur you are referring to then I would suggest that > that is just a case of the Java world finding a better alternative. > That isn't a "failure" - after all Cocoon has successfully leveraged it > for years. It is just normal software evolution. > > So what if Cocoon ends up being the only user of this? The point is > that it will probably never be leveraged outside of Cocoon until it is > split off. > > Ralph > > Reinhard Poetz wrote: >> Ralph Goers wrote: >>> Would it make sense to move this out of Cocoon entirely, similar to >>> the javaflow stuff? That might make it easier for it to be reused. >> After seeing Excalibur fail, I'm hesitating whenever ideas of moving >> things out of our codebase come up. As long as there are no people >> outside of our community, who show their interest, I don't think it >> makes sense. >> > -- Carsten Ziegeler - Chief Architect http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
