From dev-return-99955-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Wed Jul 30 05:48:11 2008 Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 11420 invoked from network); 30 Jul 2008 05:48:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Jul 2008 05:48:10 -0000 Received: (qmail 25458 invoked by uid 500); 30 Jul 2008 05:48:08 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 25367 invoked by uid 500); 30 Jul 2008 05:48:08 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 25356 invoked by uid 99); 30 Jul 2008 05:48:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jul 2008 22:48:08 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [88.198.46.98] (HELO indoqa.com) (88.198.46.98) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jul 2008 05:47:11 +0000 Received: from [192.168.0.193] (chello062178239020.5.15.vie.surfer.at [62.178.239.20]) by indoqa.com (Postfix) with ESMTP id 7CDE4255CB9 for ; Wed, 30 Jul 2008 07:47:06 +0200 (CEST) Message-ID: <48900032.5010401@apache.org> Date: Wed, 30 Jul 2008 07:46:26 +0200 From: =?ISO-8859-1?Q?Reinhard_P=F6tz?= User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Find a new name for Corona (was: [proposal] Corona: A Cocoon subproject) References: <487EDECB.2000909@apache.org> <20080718031245.GA17478@igg.indexgeo.com.au> <48832CD2.30204@apache.org> <20080730044816.GB10862@igg.indexgeo.com.au> In-Reply-To: <20080730044816.GB10862@igg.indexgeo.com.au> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org David Crossley wrote: > Reinhard P?tz wrote: >> David Crossley wrote: >>> Reinhard P?tz wrote: >>>> Finally this brings me to my last question: Do we want or do we have to >>>> change the name "Corona"? For the legal part of this question, who can I >>>> ask to get a final yes or no? >>> The Apache Incubator docs should have some guidelines >>> about this topic, since this issue often arises there. >>> The Incubator general mail list would have lots of >>> examples of people struggling with this issue, and hence >>> guidance from ASF members. >>> >>> A quick search found these docs: >>> >>> http://incubator.apache.org/guides/releasemanagement.html#naming >>> >>> See any project's "Status report" >>> http://incubator.apache.org/projects/ >>> The first item on their "Incubation work items" >>> is to be sure that the name is okay. e.g. >>> http://incubator.apache.org/projects/sanselan.html >>> The instruction says: >>> "Make sure that the requested project name does not >>> already exist and check www.nameprotect.com to be sure >>> that the name is not already trademarked for an >>> existing software product." >> Does the ASF have an account? > > I don't know. > > This would generally be a good topic to raise on the ASF > legal-discuss mail list. If it was framed in terms of > establishing a well-defined procedure, then it would get > better response. > >>> A quick search for "corona software java" shows some >>> high profile software products. >> Ok, this means that we have to find a better name. >> >>> First we should define the mission of this subproject. >>> We will need a one-sentence description anyway. >>> Then the appropriate name should fall out. >> Corona has two main goals: >> >> 1. Become the best platform for RESTful services and >> RESTful web applications based on the concept >> of pipelines. >> >> 2. Provide a generic pipeline Java API with SAX >> and STaX based default implementations. >> >>> I lean towards "Fibre" or "Silk". However because it >>> might not be the pipeline API that Cocoon uses, then >>> perhaps some other type of fibre. For example, >>> "Kapok" - "a fine fibrous cotton-like substance >>> found surrounding the seeds of a tropical tree". >>> (Australian Oxford English Dictionary). The term >>> "Java Kapok" is used, but from my quick search >>> not in the software industry. >>> http://en.wikipedia.org/wiki/Ceiba_pentandra >>> >>> So my proposals are: >>> Apache Cocoon Kapok >>> Apache Cocoon Fibre >> I tend towards Apache (Cocoon) Silk because it is short and easily >> pronounceable (in contrast to Fibre) and doesn't sound like Klingon >> (Kapok). > > The USA spelling might be better: "Fiber". ok, that's much better IMO. Provided that we are allowed to have a subproject without "Cocoon" in the name, the current list of suggested names includes: . Apache Cocoon Fiber . Apache Cocoon Silk . Apache Fiber . Apache Silk Any other suggestions? -- Reinhard Pötz Managing Director, {Indoqa} GmbH http://www.indoqa.com/en/people/reinhard.poetz/ Member of the Apache Software Foundation Apache Cocoon Committer, PMC member reinhard@apache.org ________________________________________________________________________