Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <48970D1E.1090304@apache.org>
Date: Mon, 04 Aug 2008 16:07:26 +0200
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; de;
 rv:1.8.1.16) Gecko/20080707 Lightning/0.8 Thunderbird/2.0.0.16
 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: A new name for Corona (take 2)
References: <4895CC7D.80406@dslextreme.com> <48963071.2040107@apache.org>
 <489655B3.6000706@dslextreme.com> <48969B55.3010205@apache.org>
 <4896A080.90806@apache.org> <4897071A.9020507@apache.org>
 <48970847.9020508@apache.org>
In-Reply-To: <48970847.9020508@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Reinhard P�tz wrote:
> 
> What would Spring do if the have a rewrite that _might_ become Spring 
> 4.0 but they don't know yet?
> 
Ok, I can't read their minds, but it's easier for them as they already 
have functional names, So a 4.0 for them is just re-using the right 
functional names, adding some, dropping others perhaps. (Just speculating)

>> Atm we have only a small set of modules in the Corona code, but 
>> perhaps this might crow and the more it crows, the more difficult it 
>> will be to tell people what Corona is.
> 
> Can you give an example for such descriptive names?
> 
> I like the idea of functional names but I just fail to see how this can 
> work in our case :-/
> 
One of them could be "Cocoon Pipeline API", "Cocoon Sitemap API" (I 
don't like this very much - but it's just an example).


Carsten

-- 
Carsten Ziegeler
cziegeler@apache.org