You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Reinhard Pötz <re...@apache.org> on 2008/07/17 07:55:23 UTC
[proposal] Corona: A Cocoon subproject
Dear Cocoon PMC,
as I said in a separate thread recently, it's time for Corona to move
out of the whiteboard of Cocoon in order to increase its visibility and
to allow releases. Corona has reached a state where it is already useful
but there is a lot of room for others to enhance and improve it.
So far Corona has been developed by Steven and me (+ some additions by
Carsten recently) which doesn't qualify for being a diverse community.
In order to change this I want to propose Corona to become a subproject
of Cocoon under the oversight of the Cocoon PMC.
For that purpose I think that it would be a good idea to follow the
procedure of the Incubator and nominate at least 2 additional PMC
members who help us to grow the community and do all the legal checks
when Corona is released (I'd love to see a alpha-1 release this summer.)
Therefore I kindly want to ask two other Cocoon PMC members to
become mentors for Corona and help to get it going.
I also propose that Corona is being moved to
https://svn.apache.org/repos/asf/cocoon/corona. The initial set of
committers should consist of Carsten, Steven and me - every Cocoon
committer can get write access by simply asking for it on this list.
Additionally I'd also like to see a separate Jira project for Corona.
Are there any objections if ask infra in behalf of the Cocoon PMC to
create one for us?
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?
--
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
________________________________________________________________________
Re: [proposal] Corona: A Cocoon subproject
Posted by Reinhard Pötz <re...@apache.org>.
Joerg Heinicke wrote:
> On 20.07.2008 14:17, Reinhard Pötz wrote:
>>> First we should define the mission of this subproject.
>>
>> 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.
>>
>>> We will need a one-sentence description anyway.
>>> Then the appropriate name should fall out.
>>>
>>> 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).
>>
>> I don't know if we should add "Cocoon" to the name and have no strong
>> opinion.
>
> Is it THAT different that you don't consider calling it Cocoon 3.0 at all?
The main concepts are the same (component based pipelines, sitemaps) but
we didn't bother to implement them in a backwards-compatible way.
Corona, as it is today, is more focused (see the list of main goals
above that we had when we created Corona) and won't become a complete
replacement for Cocoon 2.x in a foreseeable future.
- o -
Before we make the decision if Corona should become Cocoon 3.0 we should
learn more what other people think about it. (Currently it's only 3
people who are using it!) IMO the best way to find this out is by
shipping alpha releases under a codename. This gives us the freedom to
decide later without spoiling version numbers.
--
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
________________________________________________________________________
Re: [proposal] Corona: A Cocoon subproject
Posted by Joerg Heinicke <jo...@gmx.de>.
On 20.07.2008 14:17, Reinhard Pötz wrote:
>> First we should define the mission of this subproject.
>
> 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.
>
>> We will need a one-sentence description anyway.
>> Then the appropriate name should fall out.
>>
>> 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).
>
> I don't know if we should add "Cocoon" to the name and have no strong
> opinion.
Is it THAT different that you don't consider calling it Cocoon 3.0 at all?
Joerg
Re: [proposal] Corona: A Cocoon subproject
Posted by David Crossley <cr...@apache.org>.
Reinhard P?tz wrote:
> David Crossley wrote:
> >
> >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.
>
> What does it mean to establish a procedure? Could you help me with that?
A guideline or FAQ that can go at http://apache.org/legal/
Start with some words to define the issue and how to
resolve it. Ensuing discussion should then finanlise it.
The issue arises for new projects at the Incubator and
for existing projects with their sub-projects.
Probably need to research discussion on general @ incubator too.
I am busy at the moment, but will try next week if you
have not got to it.
-David
Re: [proposal] Corona: A Cocoon subproject
Posted by Reinhard Pötz <re...@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.
What does it mean to establish a procedure? Could you help me with that?
>>> 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".
>> I don't know if we should add "Cocoon" to the name and have no strong
>> opinion.
>
> I thought that we needed to, as it is a sub-project
> of Apache Cocoon. One of us should clarify that on
> the legal-discuss list.
I don't think that it is needed: The Lucene project has several
subprojects like "Solr", "Tika", "Mahut" etc. But I will ask on
legal-discuss@apache to clarify this question.
--
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
________________________________________________________________________
Re: Find a new name for Corona
Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
Bertrand Delacretaz pisze:
> On Wed, Jul 30, 2008 at 7:46 AM, Reinhard Pötz <re...@apache.org> wrote:
>
>> ... . Apache Cocoon Silk
>
> My favorite - usually known as "Cocoon Silk"
>
>> ... . Apache Silk...
>
> Omitting Cocoon in the name would be a bad idea IMO, as the Cocoon
> "brand" is well-known.
+1
--
Grzegorz Kossakowski
Re: Find a new name for Corona (was: [proposal] Corona: A Cocoon subproject)
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Wed, Jul 30, 2008 at 7:46 AM, Reinhard Pötz <re...@apache.org> wrote:
> ... . Apache Cocoon Silk
My favorite - usually known as "Cocoon Silk"
> ... . Apache Silk...
Omitting Cocoon in the name would be a bad idea IMO, as the Cocoon
"brand" is well-known.
-Bertrand
Re: Find a new name for Corona (was: [proposal] Corona: A Cocoon subproject)
Posted by Andrew Savory <as...@apache.org>.
Hi,
2008/7/30 Reinhard Pötz <re...@apache.org>:
> 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?
I'd argue strongly in favour of the original spelling, Fibre, and not Fiber.
Andrew.
--
asavory@apache.org / contact@andrewsavory.com
http://www.andrewsavory.com/
RE: Find a new name for Corona (was: [proposal] Corona: A Cocoon subproject)
Posted by Jasha Joachimsthal <j....@onehippo.com>.
> -----Original Message-----
> From: Reinhard Pötz [mailto:reinhard@apache.org]
> Sent: woensdag 30 juli 2008 7:46
> To: dev@cocoon.apache.org
> Subject: Find a new name for Corona (was: [proposal] Corona:
> A Cocoon subproject)
>
> > 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?
Fiber returns many IT related hits in search engines. While Silk gives almost none (except [1], who did that graphical design?). So if you're developing with/for "Corona" and you're looking for information or help, Silk may be better. You may get lost in all results for Fiber which are unrelated to this project.
Just my €0.02.
[1] http://www.silkproject.org/
Jasha Joachimsthal
www.onehippo.com
Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1 (707) 773-4646
Re: Find a new name for Corona
Posted by Luca Morandini <lm...@ieee.org>.
Bertrand Delacretaz wrote:
>
> If that's the plan (and I like it), why not keep the "project Corona"
> name for now?
>
> That would be just a project name, not a product name, so we don't
> need to care about conflicts, the full name would be "Apache Cocoon -
> project Corona".
In my, very humble, opinion, this makes a lot of sense.
Moreover, I like the Corona name: it was the codename for the first
family of spy satellites (actually, it was spelled "project CORONA", in
uppercase)... quite an endeavor at the time [1].
Regards,
[1] http://en.wikipedia.org/wiki/Corona_(satellite)
--------------------
Luca Morandini
www.lucamorandini.it
--------------------
Re: Find a new name for Corona
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Wed, Jul 30, 2008 at 6:04 PM, Reinhard Pötz <re...@apache.org> wrote:
> ...I'm still not convinced that we should name it Cocoon 3.0 _now_ (quoting
> myself from a few days ago):..
I knew someone had said something about that, couldn't find that thread ;-)
> ...When Corona is able to attract a stable community proves itself useable to a
> wider audience, we can start to ship it as Cocoon 3.0....
If that's the plan (and I like it), why not keep the "project Corona"
name for now?
That would be just a project name, not a product name, so we don't
need to care about conflicts, the full name would be "Apache Cocoon -
project Corona".
-Bertrand
Re: Find a new name for Corona
Posted by Rainer Pruy <Ra...@Acrys.COM>.
Just my 0,02 cents...
I always considered "Cocoon" to mean more than pipelines, sitemap and alike....
Thus I don't think using Cocoon 3.0 being an apropriate name.
What about
Cocoon Pipe (ok, not exaktly)
or
Cocoon Bones
Rainer
Reinhard Pötz schrieb:
> Bertrand Delacretaz wrote:
>> On Wed, Jul 30, 2008 at 5:28 PM, Reinhard Pötz <re...@apache.org>
>> wrote:
>>> :-( that's bad. Any other suggestions?
>>
>> I still think that Cocoon 3.0 could be the name, if people are going
>> to invest a significant effort in what's Corona today. For Sling we'd
>> like to use the pipelines implementation, so some of us Sling folks
>> are planning to contribute and help maintain that. I am not interested
>> in the other parts at the moment.
>>
>> We already have 2.1 and 2.2 which are fairly different products,
>> Cocoon 3.0 would be a lightweight embeddable thing that captures the
>> essence of Cocoon in a way that's better suited to many of today's
>> environments. Clearly an evolution, even though some parts will be
>> missing, as those new environments provide them.
>
> I'm still not convinced that we should name it Cocoon 3.0 _now_ (quoting
> myself from a few days ago):
>
> [...] Before we make the decision if Corona should become Cocoon 3.0 we
> should learn more what other people think about it. (Currently it's only
> 3 people who use it!) IMO the best way to find this out is by shipping
> alpha releases under a codename. This gives us the freedom to decide
> later without spoiling version numbers. [...]
>
> When Corona is able to attract a stable community proves itself useable
> to a wider audience, we can start to ship it as Cocoon 3.0.
>
> Or is it only me who needs to be convinced of shipping Corona as Cocoon
> 3.0?
>
Re: Find a new name for Corona
Posted by Reinhard Pötz <re...@apache.org>.
Bertrand Delacretaz wrote:
> On Wed, Jul 30, 2008 at 5:28 PM, Reinhard Pötz <re...@apache.org> wrote:
>> :-( that's bad. Any other suggestions?
>
> I still think that Cocoon 3.0 could be the name, if people are going
> to invest a significant effort in what's Corona today. For Sling we'd
> like to use the pipelines implementation, so some of us Sling folks
> are planning to contribute and help maintain that. I am not interested
> in the other parts at the moment.
>
> We already have 2.1 and 2.2 which are fairly different products,
> Cocoon 3.0 would be a lightweight embeddable thing that captures the
> essence of Cocoon in a way that's better suited to many of today's
> environments. Clearly an evolution, even though some parts will be
> missing, as those new environments provide them.
I'm still not convinced that we should name it Cocoon 3.0 _now_ (quoting
myself from a few days ago):
[...] Before we make the decision if Corona should become Cocoon 3.0 we
should learn more what other people think about it. (Currently it's only
3 people who use it!) IMO the best way to find this out is by shipping
alpha releases under a codename. This gives us the freedom to decide
later without spoiling version numbers. [...]
When Corona is able to attract a stable community proves itself useable
to a wider audience, we can start to ship it as Cocoon 3.0.
Or is it only me who needs to be convinced of shipping Corona as Cocoon 3.0?
--
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
________________________________________________________________________
Re: Find a new name for Corona
Posted by Thorsten Scherler <th...@apache.org>.
On Thu, 2008-07-31 at 07:21 -0700, Ralph Goers wrote:
>
> Thorsten Scherler wrote:
> >
> >> Just to say another name: ;)
> >>
> >> Apache Kokon
> >>
> >> which is cocoon in German.
> >>
> >
> > jeje this one is for Antonio:
> >
> > Apache Capullo
> >
> > which is cocoon in Spanish (but in Spain it has a slightly double
> > meaning).
> >
> > salu2
> >
> Should I ask?
>
> I actually like both those names - depending on the secondary meaning.
hehehe, the second meaning in Spain (not in south America) is somehow
like "asshole" but in a more friendly way and is really an Andalusia
thing. ;) Good laughs I had with Antonio about that.
In Nicaragua it has the double meaning of "darling" "sweetheart".
salu2
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
Re: Find a new name for Corona
Posted by Ralph Goers <Ra...@dslextreme.com>.
Thorsten Scherler wrote:
>
>> Just to say another name: ;)
>>
>> Apache Kokon
>>
>> which is cocoon in German.
>>
>
> jeje this one is for Antonio:
>
> Apache Capullo
>
> which is cocoon in Spanish (but in Spain it has a slightly double
> meaning).
>
> salu2
>
Should I ask?
I actually like both those names - depending on the secondary meaning.
Re: Find a new name for Corona
Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
On Thu, 2008-07-31 at 14:03 +0200, Thorsten Scherler wrote:
> On Thu, 2008-07-31 at 09:54 +0200, Bertrand Delacretaz wrote:
> > On Thu, Jul 31, 2008 at 9:50 AM, Reinhard Pötz <re...@apache.org> wrote:
> > > Bertrand Delacretaz wrote:
> > >> ....just put up all the suggested names for a
> > >> majority vote of our committers, and be done with it.
> > >
> > > What would be the options that we vote on?
> > >
> > > a) keep the name Apache Cocoon Corona
> > > b) rename to Apache Cocoon Silk
> > > c) we need to find some other name...
> >
> > There's also Apache Cocoon Weedle that I proposed this morning in this thread.
>
> Just to say another name: ;)
>
> Apache Kokon
>
> which is cocoon in German.
jeje this one is for Antonio:
Apache Capullo
which is cocoon in Spanish (but in Spain it has a slightly double
meaning).
salu2
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
Re: Find a new name for Corona
Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
On Thu, 2008-07-31 at 09:54 +0200, Bertrand Delacretaz wrote:
> On Thu, Jul 31, 2008 at 9:50 AM, Reinhard Pötz <re...@apache.org> wrote:
> > Bertrand Delacretaz wrote:
> >> ....just put up all the suggested names for a
> >> majority vote of our committers, and be done with it.
> >
> > What would be the options that we vote on?
> >
> > a) keep the name Apache Cocoon Corona
> > b) rename to Apache Cocoon Silk
> > c) we need to find some other name...
>
> There's also Apache Cocoon Weedle that I proposed this morning in this thread.
Just to say another name: ;)
Apache Kokon
which is cocoon in German.
salu2
>
> -Bertrand
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
Re: Find a new name for Corona
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Thu, Jul 31, 2008 at 9:50 AM, Reinhard Pötz <re...@apache.org> wrote:
> Bertrand Delacretaz wrote:
>> ....just put up all the suggested names for a
>> majority vote of our committers, and be done with it.
>
> What would be the options that we vote on?
>
> a) keep the name Apache Cocoon Corona
> b) rename to Apache Cocoon Silk
> c) we need to find some other name...
There's also Apache Cocoon Weedle that I proposed this morning in this thread.
-Bertrand
Re: Find a new name for Corona
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Thu, Jul 31, 2008 at 9:59 AM, Ralph Goers <Ra...@dslextreme.com> wrote:
>
>
> Reinhard Pötz wrote:
>>
>> What would be the options that we vote on?
>>
>> a) keep the name Apache Cocoon Corona
>> b) rename to Apache Cocoon Silk
>> c) we need to find some other name
>>
>> Any other options?
>
> I sent a message to legal internal to get their opinion on options a and b.
> I suggest waiting for an answer....
We could also vote and, if one of the names is vetoed by the legal
team (which I doubt very much - it's "Apache Cocoon foo" anyway), take
the next one.
-Bertrand
Re: Find a new name for Corona
Posted by Ralph Goers <Ra...@dslextreme.com>.
Sorry, I didn't do reply-all. I usually just do reply on all my Apache
email.
Reinhard Pötz wrote:
> Ralph Goers wrote:
>>
>>
>> Reinhard Pötz wrote:
>>>
>>> What would be the options that we vote on?
>>>
>>> a) keep the name Apache Cocoon Corona
>>> b) rename to Apache Cocoon Silk
>>> c) we need to find some other name
>>>
>>> Any other options?
>> I sent a message to legal internal to get their opinion on options a
>> and b. I suggest waiting for an answer.
>
> Any reason not to cc dev@ or at least private@?
>
Re: Find a new name for Corona
Posted by Reinhard Pötz <re...@apache.org>.
Ralph Goers wrote:
>
>
> Reinhard Pötz wrote:
>>
>> What would be the options that we vote on?
>>
>> a) keep the name Apache Cocoon Corona
>> b) rename to Apache Cocoon Silk
>> c) we need to find some other name
>>
>> Any other options?
> I sent a message to legal internal to get their opinion on options a and
> b. I suggest waiting for an answer.
Any reason not to cc dev@ or at least private@?
--
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
________________________________________________________________________
Re: Find a new name for Corona
Posted by Ralph Goers <Ra...@dslextreme.com>.
Reinhard Pötz wrote:
>
> What would be the options that we vote on?
>
> a) keep the name Apache Cocoon Corona
> b) rename to Apache Cocoon Silk
> c) we need to find some other name
>
> Any other options?
I sent a message to legal internal to get their opinion on options a and
b. I suggest waiting for an answer.
Ralph
Re: Find a new name for Corona
Posted by Reinhard Pötz <re...@apache.org>.
Bertrand Delacretaz wrote:
> On Thu, Jul 31, 2008 at 9:17 AM, Torsten Curdt <tc...@apache.org> wrote:
>> ...We had this renaming game with CForms IIRC. And it was more confusing than
>> it helped.
yes, it took years until Woody was gone. But the situation was different
because Woody had a large user base which Corona hasn't (yet).
> I guess that was so long ago that some people don't remember...
>
> I do remember - finding names for products today is the nightmare ;-)
yes, I really get tired of this discussion. Since it will probably be me
who has to do the actual renaming work, I'm strongly in favor of leaving
things as they are (= keeping the name Corona, do some alpha/beta
releases and then we still can decide if we have to change something ...)
>> ...I think Corona is a great name. Everyone uses it. People already know it by
>> now. Let's officially call it Apache Cocoon (Project) Corona. Everyone will
>> call it Corona anyway. Will that really be a problem? (Sorry if I missed
>> that thread/post)...
>
> I would agree with that - or just put up all the suggested names for a
> majority vote of our committers, and be done with it.
What would be the options that we vote on?
a) keep the name Apache Cocoon Corona
b) rename to Apache Cocoon Silk
c) we need to find some other name
Any other options?
--
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
________________________________________________________________________
Re: Find a new name for Corona
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Thu, Jul 31, 2008 at 9:17 AM, Torsten Curdt <tc...@apache.org> wrote:
> ...We had this renaming game with CForms IIRC. And it was more confusing than
> it helped. I guess that was so long ago that some people don't remember...
I do remember - finding names for products today is the nightmare ;-)
> ...I think Corona is a great name. Everyone uses it. People already know it by
> now. Let's officially call it Apache Cocoon (Project) Corona. Everyone will
> call it Corona anyway. Will that really be a problem? (Sorry if I missed
> that thread/post)...
I would agree with that - or just put up all the suggested names for a
majority vote of our committers, and be done with it.
-Bertrand
Re: Find a new name for Corona
Posted by Joerg Heinicke <jo...@gmx.de>.
Torsten Curdt <tcurdt <at> apache.org> writes:
> I think Corona is a great name. Everyone uses it. People already know
> it by now. Let's officially call it Apache Cocoon (Project) Corona.
> Everyone will call it Corona anyway. Will that really be a problem?
> (Sorry if I missed that thread/post)
>
> And once things are there we can think of a migration strategy and
> migrate it to Cocoon 3.0. But that is still a long way.
I tend to agree with Torsten. Renaming it now and potentially again in a year
sounds like a lot of confusion. Of course tagging it with the final name as
early as possible would be good but it seems we can't agree on calling it Cocoon
3.0 right now. So I prefer to leave it as it is (or just change it to the
official name Apache Cocoon Corona).
Joerg
Re: Find a new name for Corona
Posted by Torsten Curdt <tc...@apache.org>.
Guy, just my 2 cents.
We had this renaming game with CForms IIRC. And it was more confusing
than it helped. I guess that was so long ago that some people don't
remember.
I think Corona is a great name. Everyone uses it. People already know
it by now. Let's officially call it Apache Cocoon (Project) Corona.
Everyone will call it Corona anyway. Will that really be a problem?
(Sorry if I missed that thread/post)
And once things are there we can think of a migration strategy and
migrate it to Cocoon 3.0. But that is still a long way.
cheers
--
Torsten
Re: Find a new name for Corona
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Thu, Jul 31, 2008 at 8:40 AM, Ralph Goers <Ra...@dslextreme.com> wrote:
> Reinhard Pötz wrote:
>> ...The name that we would use is "Cocoon Silk". So I tend to think that it
>> isn't a problem....
> ...Trademark or not, when people in software talk about Silk these products are
> what they mean. Using a name that is already highly branded would be a
> mistake....
I have a new proposal: Weedle.
According to http://en.wikipedia.org/wiki/Kakuna#Weedle, Weedle are
"very weak Pokémon that are captured to be evolved into their
cocoon-like Kakuna form". Suits Corona well, as that might or might
not become the next Cocoon.
And they look cute: http://bulbapedia.bulbagarden.net/wiki/Weedle_(Pok%C3%A9mon)
I'm not a Pokemon fan by any means but it looks like the name is not
associated with software yet, so it might work.
-Bertrand
Re: Find a new name for Corona
Posted by Reinhard Pötz <re...@apache.org>.
Ralph Goers wrote:
> Reinhard Pötz wrote:
>>
>> Borland hasn't trademarked "silk" but only some variants of it. See
>> http://tinyurl.com/5bkw9d
>>
>> "Silk" was trademarked by a company called mentis:
>> http://tess2.uspto.gov/bin/showfield?f=doc&state=pgshps.20.117
>>
>> The name that we would use is "Cocoon Silk". So I tend to think that
>> it isn't a problem.
>>
>> WDOT?
>>
> Trademark or not, when people in software talk about Silk these products
> are what they mean. Using a name that is already highly branded would be
> a mistake. Maybe most of you are too young to get this but what would
> you think of a project named Apache SideKick? If it wasn't a Personal
> Information Manager people would be confused. If it was people would be
> even more confused. (If you don't know what SideKick was see
> http://en.wikipedia.org/wiki/SideKick).
>
> The point is, people would expect Cocoon Silk to be some sort of
> performance measurement tool, probably with the expectation that it
> hooks into Silk Test or Silk Performer somehow. (Which actually isn't a
> bad idea).
I don't know neither SideKick nor Borland's Silk. I can't say if people
immediately start to think of test tools when they hear the world silk
somehow related to software. Silk is also used over 700! times in US
trademarks only so people probably have many different first ideas.
IIUC Borland didn't care themselves that another company has already
registered Silk and if other companies like Microsoft used Avalon for
software years after the Apache Avalon project was started. I can't
believe that they didn't know before ;-)
--
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
________________________________________________________________________
Re: Find a new name for Corona
Posted by Ralph Goers <Ra...@dslextreme.com>.
Reinhard Pötz wrote:
>
> Borland hasn't trademarked "silk" but only some variants of it. See
> http://tinyurl.com/5bkw9d
>
> "Silk" was trademarked by a company called mentis:
> http://tess2.uspto.gov/bin/showfield?f=doc&state=pgshps.20.117
>
> The name that we would use is "Cocoon Silk". So I tend to think that
> it isn't a problem.
>
> WDOT?
>
Trademark or not, when people in software talk about Silk these products
are what they mean. Using a name that is already highly branded would be
a mistake. Maybe most of you are too young to get this but what would
you think of a project named Apache SideKick? If it wasn't a Personal
Information Manager people would be confused. If it was people would be
even more confused. (If you don't know what SideKick was see
http://en.wikipedia.org/wiki/SideKick).
The point is, people would expect Cocoon Silk to be some sort of
performance measurement tool, probably with the expectation that it
hooks into Silk Test or Silk Performer somehow. (Which actually isn't a
bad idea).
Ralph
Re: Find a new name for Corona
Posted by Reinhard Pötz <re...@apache.org>.
Peter Hunsberger wrote:
> On Wed, Jul 30, 2008 at 10:53 AM, Bertrand Delacretaz
> <bdelacretaz@apache.org <ma...@apache.org>> wrote:
>
> On Wed, Jul 30, 2008 at 5:28 PM, Reinhard Pötz <reinhard@apache.org
> <ma...@apache.org>> wrote:
> > :-( that's bad. Any other suggestions?
>
> I still think that Cocoon 3.0 could be the name, if people are going
> to invest a significant effort in what's Corona today. For Sling we'd
> like to use the pipelines implementation, so some of us Sling folks
> are planning to contribute and help maintain that. I am not interested
> in the other parts at the moment.
>
>
> I think that at the moment Corona is far too much of an experiment to be
> considered 3.0. Parts of it or all may become 3.0 but who knows?
>
> Almost any name we choose will overlap with an existing product to some
> extent. If it's not trademarked I'm ok with the overlap. As such I
> think "Silk" is still one of the best options I've seen suggested..
Borland hasn't trademarked "silk" but only some variants of it. See
http://tinyurl.com/5bkw9d
"Silk" was trademarked by a company called mentis:
http://tess2.uspto.gov/bin/showfield?f=doc&state=pgshps.20.117
The name that we would use is "Cocoon Silk". So I tend to think that it
isn't a problem.
WDOT?
--
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
________________________________________________________________________
Re: Find a new name for Corona
Posted by Peter Hunsberger <pe...@gmail.com>.
On Wed, Jul 30, 2008 at 10:53 AM, Bertrand Delacretaz <
bdelacretaz@apache.org> wrote:
> On Wed, Jul 30, 2008 at 5:28 PM, Reinhard Pötz <re...@apache.org>
> wrote:
> > :-( that's bad. Any other suggestions?
>
> I still think that Cocoon 3.0 could be the name, if people are going
> to invest a significant effort in what's Corona today. For Sling we'd
> like to use the pipelines implementation, so some of us Sling folks
> are planning to contribute and help maintain that. I am not interested
> in the other parts at the moment.
>
I think that at the moment Corona is far too much of an experiment to be
considered 3.0. Parts of it or all may become 3.0 but who knows?
Almost any name we choose will overlap with an existing product to some
extent. If it's not trademarked I'm ok with the overlap. As such I think
"Silk" is still one of the best options I've seen suggested..
--
Peter Hunsberger
Re: Find a new name for Corona
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Wed, Jul 30, 2008 at 5:28 PM, Reinhard Pötz <re...@apache.org> wrote:
> :-( that's bad. Any other suggestions?
I still think that Cocoon 3.0 could be the name, if people are going
to invest a significant effort in what's Corona today. For Sling we'd
like to use the pipelines implementation, so some of us Sling folks
are planning to contribute and help maintain that. I am not interested
in the other parts at the moment.
We already have 2.1 and 2.2 which are fairly different products,
Cocoon 3.0 would be a lightweight embeddable thing that captures the
essence of Cocoon in a way that's better suited to many of today's
environments. Clearly an evolution, even though some parts will be
missing, as those new environments provide them.
-Bertrand
Re: Find a new name for Corona
Posted by Reinhard Pötz <re...@apache.org>.
:-( that's bad. Any other suggestions?
Ralph Goers wrote:
> Silk is the shorthand name for SilkTest and SilkPerformer.
> http://www.borland.com/us/products/silk/index.html.
>
> Carsten Ziegeler wrote:
>> Reinhard Pötz wrote:
>>>
>>> . Apache Cocoon Fiber
>>> . Apache Cocoon Silk
>>> . Apache Fiber
>>> . Apache Silk
>>>
>>> Any other suggestions?
>>>
>> I agree with the others that we should leave "Cocoon" in the name. We
>> have a very strong brand which we should use.
>>
>> I don't like "Fiber" - it reminds me of the German word (Fieber) for
>> fever - and I can imagine many lame jokes on that one. :)
>>
>> Between the original spelling Fibre and Silk I prefer Silk.
>>
>> So +1 for Cocoon Silk.
>>
>> Carsten
--
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
________________________________________________________________________
Re: Find a new name for Corona
Posted by Ralph Goers <Ra...@dslextreme.com>.
Silk is the shorthand name for SilkTest and SilkPerformer.
http://www.borland.com/us/products/silk/index.html.
Carsten Ziegeler wrote:
> Reinhard Pötz wrote:
>>
>> . Apache Cocoon Fiber
>> . Apache Cocoon Silk
>> . Apache Fiber
>> . Apache Silk
>>
>> Any other suggestions?
>>
> I agree with the others that we should leave "Cocoon" in the name. We
> have a very strong brand which we should use.
>
> I don't like "Fiber" - it reminds me of the German word (Fieber) for
> fever - and I can imagine many lame jokes on that one. :)
>
> Between the original spelling Fibre and Silk I prefer Silk.
>
> So +1 for Cocoon Silk.
>
> Carsten
Re: Find a new name for Corona
Posted by Carsten Ziegeler <cz...@apache.org>.
Reinhard Pötz wrote:
>
> . Apache Cocoon Fiber
> . Apache Cocoon Silk
> . Apache Fiber
> . Apache Silk
>
> Any other suggestions?
>
I agree with the others that we should leave "Cocoon" in the name. We
have a very strong brand which we should use.
I don't like "Fiber" - it reminds me of the German word (Fieber) for
fever - and I can imagine many lame jokes on that one. :)
Between the original spelling Fibre and Silk I prefer Silk.
So +1 for Cocoon Silk.
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Find a new name for Corona (was: [proposal] Corona: A Cocoon subproject)
Posted by Reinhard Pötz <re...@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
________________________________________________________________________
Re: [proposal] Corona: A Cocoon subproject
Posted by David Crossley <cr...@apache.org>.
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".
> I don't know if we should add "Cocoon" to the name and have no strong
> opinion.
I thought that we needed to, as it is a sub-project
of Apache Cocoon. One of us should clarify that on
the legal-discuss list.
-David
Re: [proposal] Corona: A Cocoon subproject
Posted by Reinhard Pötz <re...@apache.org>.
David Crossley wrote:
> Reinhard P?tz wrote:
>> Dear Cocoon PMC,
>>
>> as I said in a separate thread recently, it's time for Corona to move
>> out of the whiteboard of Cocoon in order to increase its visibility and
>> to allow releases. Corona has reached a state where it is already useful
>> but there is a lot of room for others to enhance and improve it.
>>
>> So far Corona has been developed by Steven and me (+ some additions by
>> Carsten recently) which doesn't qualify for being a diverse community.
>
> By my standards, all the people who have helped to
> discuss it are part of the community.
>
>> In order to change this I want to propose Corona to become a subproject
>> of Cocoon under the oversight of the Cocoon PMC.
>>
>> For that purpose I think that it would be a good idea to follow the
>> procedure of the Incubator and nominate at least 2 additional PMC
>> members who help us to grow the community and do all the legal checks
>> when Corona is released (I'd love to see a alpha-1 release this summer.)
>>
>> Therefore I kindly want to ask two other Cocoon PMC members to
>> become mentors for Corona and help to get it going.
>
> I don't see the need. Cocoon PMC are the mentors
> and have oversight. Anyone, including non-PMC,
> can speak up at any time.
The two problems that my proposal tries to solve is that if nobody
speaks up and if nobody feels responsible.
>> I also propose that Corona is being moved to
>> https://svn.apache.org/repos/asf/cocoon/corona. The initial set of
>> committers should consist of Carsten, Steven and me - every Cocoon
>> committer can get write access by simply asking for it on this list.
>
> I would prefer that all Cocoon committers have
> default commit ability.
When I look at an opensource project it's important for me to find out
the number of _active_ committers. By implication that means that I want
to be honest with all (potential) users and also be clear about the
number of people who have contributed code and about their affiliations.
This could be easily achieved by starting with a fresh list of
committers. And for all the existing Cocoon committers it shouldn't be
too hard to write an email to this list.
OTOH it would be good enough if the list of developers in the main
pom.xml of Corona only contains the names of committers that already
have contributed to Corona instead of listing all committers there that
have technical write access to the repository.
>> Additionally I'd also like to see a separate Jira project for Corona.
>> Are there any objections if ask infra in behalf of the Cocoon PMC to
>> create one for us?
>
> That can happen independently, as soon as the name
> is decided. Would it be COCOON-SOMETHING ?
This will depend whether we want to call it Apache Something or Apache
Cocoon Something. See below.
>> 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?
>
> 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.
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.
> We will need a one-sentence description anyway.
> Then the appropriate name should fall out.
>
> 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).
I don't know if we should add "Cocoon" to the name and have no strong
opinion.
> We should consider another possibility. If it
> does not have any hope of being the/a pipeline
> API for Cocoon, then perhaps it should go
> completely to Apache Incubator to become its
> own project. I would prefer that it stay here.
I don't see why it should have to go through the incubator. There is no
external project that wants to join Apache and all the work that has
gone into Corona so far was done under the eyes of the Cocoon PMC.
I prefer that Corona stays here.
--
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
________________________________________________________________________
Re: [proposal] Corona: A Cocoon subproject
Posted by David Crossley <cr...@apache.org>.
Reinhard P?tz wrote:
> Dear Cocoon PMC,
>
> as I said in a separate thread recently, it's time for Corona to move
> out of the whiteboard of Cocoon in order to increase its visibility and
> to allow releases. Corona has reached a state where it is already useful
> but there is a lot of room for others to enhance and improve it.
>
> So far Corona has been developed by Steven and me (+ some additions by
> Carsten recently) which doesn't qualify for being a diverse community.
By my standards, all the people who have helped to
discuss it are part of the community.
> In order to change this I want to propose Corona to become a subproject
> of Cocoon under the oversight of the Cocoon PMC.
>
> For that purpose I think that it would be a good idea to follow the
> procedure of the Incubator and nominate at least 2 additional PMC
> members who help us to grow the community and do all the legal checks
> when Corona is released (I'd love to see a alpha-1 release this summer.)
>
> Therefore I kindly want to ask two other Cocoon PMC members to
> become mentors for Corona and help to get it going.
I don't see the need. Cocoon PMC are the mentors
and have oversight. Anyone, including non-PMC,
can speak up at any time.
> I also propose that Corona is being moved to
> https://svn.apache.org/repos/asf/cocoon/corona. The initial set of
> committers should consist of Carsten, Steven and me - every Cocoon
> committer can get write access by simply asking for it on this list.
I would prefer that all Cocoon committers have
default commit ability.
> Additionally I'd also like to see a separate Jira project for Corona.
> Are there any objections if ask infra in behalf of the Cocoon PMC to
> create one for us?
That can happen independently, as soon as the name
is decided. Would it be COCOON-SOMETHING ?
> 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."
A quick search for "corona software java" shows some
high profile software products.
First we should define the mission of this subproject.
We will need a one-sentence description anyway.
Then the appropriate name should fall out.
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
We should consider another possibility. If it
does not have any hope of being the/a pipeline
API for Cocoon, then perhaps it should go
completely to Apache Incubator to become its
own project. I would prefer that it stay here.
-David