I received two responses from legal-internal regarding choosing a name.
Both are below. To summarize, Sam doesn't state an opinion one way or
the other on the name, just the basis for choosing one. Henri recommends
against both Corona and Silk and would prefer that the name for
subprojects as this be based on their function rather than a codename.
For example, he would prefer something like Apache Cocoon Pipeline -
which is more or less what we've been doing for blocks.
Ralph
-------- Original Message --------
Subject: Re: project names
Date: Sat, 2 Aug 2008 09:20:15 -0400
From: Sam Ruby <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Most of the expertise in name-choosing is in the incubator.
My understanding is that trademark law is based on the notion of
"likelihood of confusion", a standard that does not easily enable
binary and final determinations short of litigation.
TESS <http://tess2.uspto.gov/bin/gate.exe?f=tess&state=879qc0.1.1> may
be used to search for registered trademarks.
- Sam Ruby
On Sat, Aug 2, 2008 at 9:10 AM, Ralph Goers <[EMAIL PROTECTED]> wrote:
Any advice on this?
Ralph Goers wrote:
The Cocoon community is in the process of creating a sub-project. We are
having trouble coming up with a name that isn't already in use somewhere.
The preferred name is Apache Cocoon Corona. However, Eclipse already has a
Corona project. An alternative name is Apache Cocoon Silk. In this case
Borland has products named Silk Test and Silk Performer. It doesn't appear
to have a trademark on Silk yet I am aware that Silk is commonly used to
refer to this group of products.
What basis should the PMC use when choosing a name? It has basically been
proposed that we just go ahead and use one under the assumption that no one
will complain.
FWIW, I have my opinion on this but am purposely not stating it here.
Ralph
- Sam Ruby
-------- Original Message --------
Subject: Re: project names
Date: Sat, 2 Aug 2008 07:41:18 -0700
From: Henri Yandell <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
I would consider both of these bad names.
Silk has come up before in the Incubator and we chose not to use it
(or maybe it was in Commons). Corona hasn't, but I think we should
avoid any confusion with Eclipse.
Personally I think you shouldn't have too many codenames. ie) it should be:
Apache Cocoon Configuration Editor
Apache Cocoon Magic Server
etc. We get a bit silly with all the project names we seek to have.
You only need the codename when you want it to live separately from
Cocoon.
Hen
