I agree with Berin, good points. I have some comments to add, though. > On Tue, 2002-04-02 at 10:45, Berin Loritsch wrote: > > So I take it you guys didn't like > > > > "Apache Component Architecture"? > > > > I received no comment, so I don't know if you all saw it yet.... > Jason: > I certainly don't mean to be rude, and I don't want to start a fight but > I think it's somewhat unjustified in using the Apache name instead of > your project name to promote your project specific solutions. I never > call Turbine the "Apache Webapplication Framework" because that would be > unfair to both Struts and Cocoon.
Avalon was started way back, in the first project of the predecessor of jakarta (ie JServ @ java.apache) as the base to build all the other server projects on. I think the terms/thought of "common apache server framework" probably first appeared there. So there could be some justification in saying we 'can' use the name because that is the basis of avalon, it is why avalon was created and it has 'always been so'. I'm not sure if this is true though, and I don't really care. The situation is different now. (on another note, I hate the 'politics' associated with all this. It would be much more fun if there actually _was_ a common framework (and I'm not saying it should be avalon, or turbine, or whatever).) Jason: > I don't think you can fairly use a name like > "Apache Foo Bar" without the buy in from the rest of Apache. See above. 'the rest of apache' at one point probably did 'buy in'. 'at one point' is probably 'many years ago, when there was but one mailing list for all the java stuff at apache'. Also, getting a project accepted means a 'buy in' as well, I guess, as far as the rules go about this stuff. Jason: > I think it is most fair to all projects here to use your project name > when promoting your project and not the Apache name. I think it is smart to point out we're part of Apache. Apache stands for a community, for a certain guaranteed quality. People know that. However, all the current proposals create a mess because there is a large overlap in use case between projects. (yet another note: maybe it would be good for Avalon and Turbine to point to each other on the web page, explaining when to use the other project instead. That would add some clarity.) If we can come up with a decent 'tag' for Avalon that includes the word 'apache' yet doesn't conflict with other projects, I'm for it. - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
