We are centered around the concept of components, and I would not
like that to get lost.

Using the comments from Jason, perhaps something like this:

"Avalon Component System"

Simple, to the point, and allows for a broad range of sub projects.

> -----Original Message-----
> From: Berin Loritsch [mailto:[EMAIL PROTECTED]] 
> Sent: Tuesday, April 02, 2002 11:10 AM
> To: 'Avalon Developers List'
> Subject: RE: [Vote] Logo & banding
> 
> 
> Good points, Jason.
> 
> > -----Original Message-----
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, April 02, 2002 11:01 AM
> > To: Avalon Developers List
> > Subject: RE: [Vote] Logo & banding
> > 
> > 
> > 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....
> > 
> > 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.
> > 
> > Turbine has been used for more the webapps and could be
> > called an application framework, and the commons will more 
> > than likely evolve into a component framework. I don't think 
> > you can fairly use a name like "Apache Foo Bar" without the 
> > buy in from the rest of Apache.
> > 
> > If Struts evolved into an application framework, Turbine did
> > the same and the commons became a component framework and the 
> > former used "Apache Application Framework" and the latter 
> > used "Apache Component Framework" it would get pretty 
> > confusing pretty fast.
> > 
> > I think it is most fair to all projects here to use your
> > project name when promoting your project and not the Apache name.
> >  
> > > > -----Original Message-----
> > > > From: Leo Sutic [mailto:[EMAIL PROTECTED]]
> > > > Sent: Tuesday, April 02, 2002 10:24 AM
> > > > To: Avalon Developers List
> > > > Subject: RE: [Vote] Logo & banding
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > From: Paul Hammant [mailto:[EMAIL PROTECTED]]
> > > > > 
> > > > > Peter, Leo, Berin,
> > > > > 
> > > > > >On Wed, 3 Apr 2002 00:34, Leo Simons wrote:
> > > > > >
> > > > > >>What about "Apache Application Architecture"
> > > > > >>or "Common Application Architecture"?
> > > > > >>
> > > > > >
> > > > > >I like
> > > > > >
> > > > > Me too, despite the recent service 'offences' against the
> > > > > component
> > > > > name.
> > > > > 
> > > > > Having said that CAA is already used with the same
> > meaning in the
> > > > > world
> > > > > of IBM minicomputers.  We should be careful to use
> > Avalon Common
> > > > > Application Architecture (ACAA).
> > > > 
> > > > "Apache Common Architecture" ? Just trying to fit "Apache" in 
> > > > there without making it too long.
> > > > 
> > > > /LS
> > > > 
> > > > 
> > > > --
> > > > To unsubscribe, e-mail:   
> > > > <mailto:avalon-dev-> [EMAIL PROTECTED]>
> > > > For
> > > > additional commands,
> > > > e-mail: <mailto:[EMAIL PROTECTED]>
> > > > 
> > > 
> > > 
> > > --
> > > To unsubscribe, e-mail:   
> > <mailto:avalon-dev-> [EMAIL PROTECTED]>
> > > For
> > additional commands,
> > e-mail: 
> > > <mailto:[EMAIL PROTECTED]>
> > --
> > jvz.
> > 
> > Jason van Zyl
> > [EMAIL PROTECTED]
> > 
> http://tambora.zenplex.org
> 
> 
> --
> To unsubscribe, e-mail: 
> <mailto:avalon-dev-> [EMAIL PROTECTED]>
> For 
> additional commands, 
> e-mail: <mailto:[EMAIL PROTECTED]>
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:avalon-dev-> [EMAIL PROTECTED]>
> For 
> additional commands, 
> e-mail: <mailto:[EMAIL PROTECTED]>
> 


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to