Hi <skip/>
>Here's a concrete example to illustrate the issue: I've always been under >the assumption that at some point a few people in Jakarta land would take a >sustained interest in contributing code to Gump, at which point, I would >propose it to be a formal subproject. At the present time, it looks like >there is a greater possibility of interest of contributing by people in XML >land. This lead to a bit of soul searching, and I came to conclusion that >if that were to come to pass, I would follow the community. After all, >what does it really matter whether the code is jakarta-gump or >xml-whatever? Yep it matters because that's mixing of concerns. As an Avalon Committer I only say three words: Separation of Concerns :-)! Beside there is lot of "inoffical" co-operation. Look at Cocoon and Avalon. Devs in this project are working close together in technical issues though the project aim is completly different. I think you should leave the current diversification. Otherwise I see the danger that the xml-apache group is forced completely towards Java. But that's not the aim of XML! And when we soften Jakarta so that C++ (personally nothing against C) servers could be possible as subprojects or whatever then we even could put everything under www.apache.org and in one mailing list ;)! I know it's hard for us, but try to think as a guy from a entprise sales group ;-). Just thoughts! Gerhard -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
