I have heard the name concern a couple of times now... When we picked the name Etch about 18 months ago, we knew about the Debian release, but frankly we were unconcerned. Debian etch is the name of a release of Debian, no different than "4" being a release of Fedora. Eventually Debian etch will fade into memory just as sarge and woody have.
Etch, in our line of thinking (if it could be said we were doing any thinking :-) ) was the name we were giving to the technology, not a release. There were no other technologies named Etch or similar, so we declared victory and moved on. So I guess my question back to everyone is this: What is the concern about the name Etch, really? 1. Is there a legal trademark issue or a formal Apache branding policy issue with using the name Etch such that the use of the name is simply not going to be allowed. - or - 2. Is there a concern that during incubation, we might have to be explicit in communication and always say "Apache Etch" rather than just "Etch" because of a fear that a reference to "Etch", taken out of context, could be confused with Debian 4.0? If "1" is true then, absolutely the name should be changed. But if only "2" is true, then I will need a bit more convincing. I am after all very, very lazy and changing the name of a working toolset is well... work :-) --- James Dixson Manager, Software Development CUAE Engineering, Cisco Systems Inc. Direct: 512-336-3305 Mobile: 512-968-2116 [EMAIL PROTECTED] -----Original Message----- From: Niklas Gustavsson [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 05, 2008 3:33 PM To: general@incubator.apache.org Subject: Re: [PROPOSAL] Etch On Thu, Jul 31, 2008 at 6:16 PM, James Dixson <[EMAIL PROTECTED]> wrote: > This a proposal to enter Etch in to the incubator. > > See http://wiki.apache.org/incubator/EtchProposal for updates. +1 for incubation (non-binding). While I find this area to be a bit overcrowded lately, having both Etch and Thrift at Apache and Protocol buffers under ASL 2.0 does offer some interesting opportunities for competition as well as cooperation. I do share the concerns about naming conflicts. Debian is by far more well known and trying to establish this project under a conflicting name would be hard. /niklas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]