Re: A new name for Corona (take 2)

2008-08-08 Thread Alfred Nathaniel
On Mon, 2008-08-04 at 08:24 +0200, Reinhard Pötz wrote: Let's summarize the proposed names (alphabetical order): Cocoon Chasse -1: Too carnivore; makes me think first of the French term la chasse meaning deer hunting or a dish of deer meat. Cocoon Merenque +0: How would you pronounce that?

Re: A new name for Corona (take 2)

2008-08-05 Thread Reinhard Pötz
Vadim Gritsenko wrote: On Aug 4, 2008, at 3:01 PM, Carsten Ziegeler wrote: [EMAIL PROTECTED] wrote: Pick a number that will never be production for the experimental branch e.g. 2.7. Skip a few numbers in case trunk needs another minor number (e.g. 2.3 and 2.4) and to avoid confusion that

Re: A new name for Corona (take 2)

2008-08-05 Thread Reinhard Pötz
Reinhard Pötz wrote: Vadim Gritsenko wrote: On Aug 4, 2008, at 3:01 PM, Carsten Ziegeler wrote: [EMAIL PROTECTED] wrote: Pick a number that will never be production for the experimental branch e.g. 2.7. Skip a few numbers in case trunk needs another minor number (e.g. 2.3 and 2.4) and to

Re: A new name for Corona (take 2)

2008-08-05 Thread Carsten Ziegeler
Reinhard Pötz wrote: You guys have finally convinced me. Let's use 3.0.x for Corona, clearly state that it is alpha software on the website in the README.txt of each release artifact and see what's happening. Then we only need to find a package name that isn't used in trunk because Corona

Re: A new name for Corona (take 2)

2008-08-05 Thread Reinhard Pötz
Carsten Ziegeler wrote: Reinhard Pötz wrote: You guys have finally convinced me. Let's use 3.0.x for Corona, clearly state that it is alpha software on the website in the README.txt of each release artifact and see what's happening. Then we only need to find a package name that isn't used in

Re: A new name for Corona (take 2)

2008-08-05 Thread Daniel Fagerstrom
Reinhard Pötz skrev: Carsten Ziegeler wrote: Reinhard Pötz wrote: You guys have finally convinced me. Let's use 3.0.x for Corona, clearly state that it is alpha software on the website in the README.txt of each release artifact and see what's happening. Then we only need to find a package

Re: A new name for Corona (take 2)

2008-08-05 Thread Reinhard Pötz
Daniel Fagerstrom wrote: it's great to see you here again! Reinhard Pötz skrev: Carsten Ziegeler wrote: Reinhard Pötz wrote: You guys have finally convinced me. Let's use 3.0.x for Corona, clearly state that it is alpha software on the website in the README.txt of each release artifact and

A new name for Corona (take 2)

2008-08-04 Thread Reinhard Pötz
Ralph Goers wrote: Reinhard Pötz wrote: Corona currently consists of 4 functional modules: cocoon-corona-pipeline, cocoon-corona-sitemap, cocoon-corona-controller and cocoon-corona-servlet. Using functional names isn't an appropriate solution for our problem. This would lead to a lot of

Re: A new name for Corona (take 2)

2008-08-04 Thread Reinhard Pötz
Reinhard Pötz wrote: Ralph Goers wrote: Reinhard Pötz wrote: Corona currently consists of 4 functional modules: cocoon-corona-pipeline, cocoon-corona-sitemap, cocoon-corona-controller and cocoon-corona-servlet. Using functional names isn't an appropriate solution for our problem. This would

Re: A new name for Corona (take 2)

2008-08-04 Thread Ralph Goers
Doing a quick Google I didn't find anything relevant on Merenque. For Chasse I found http://www.atomicmpc.com.au/download/chasse.aspx and http://www.chasseconsulting.com/. The first is some sort of shareware/freeware hunting game for Windows and the second is a sales consulting firm. I

Re: A new name for Corona (take 2)

2008-08-04 Thread Reinhard Pötz
Ralph Goers wrote: Reinhard Pötz wrote: Let's summarize the proposed names (alphabetical order): Cocoon Chasse Cocoon Merenque Cocoon Morus Cocoon Weedle Could others please check these names too? Any general comments? Any other suggestions? I would agree except to suggest that perhaps the

Re: A new name for Corona (take 2)

2008-08-04 Thread Ralph Goers
Reinhard Pötz wrote: Ralph Goers wrote: Reinhard Pötz wrote: Let's summarize the proposed names (alphabetical order): Cocoon Chasse Cocoon Merenque Cocoon Morus Cocoon Weedle Could others please check these names too? Any general comments? Any other suggestions? I would agree except to

Re: A new name for Corona (take 2)

2008-08-04 Thread Carsten Ziegeler
Reinhard Pötz wrote: I still think that we shouldn't use a descriptive name in order to not confuse our users (and ourselves). The more I think about it, the more I come to the conclusion that we should use descriptive names :) The current Corona code is a collection of various modules that

Re: A new name for Corona (take 2)

2008-08-04 Thread Reinhard Pötz
Carsten Ziegeler wrote: Reinhard Pötz wrote: I still think that we shouldn't use a descriptive name in order to not confuse our users (and ourselves). The more I think about it, the more I come to the conclusion that we should use descriptive names :) The current Corona code is a collection

Re: A new name for Corona (take 2)

2008-08-04 Thread Jeremy Quinn
Has anyone suggested PAPI (Pipeline API) ? sorry have not been following the thread regards Jeremy On 4 Aug 2008, at 07:24, Reinhard Pötz wrote: Any general comments? Any other suggestions?

Re: A new name for Corona (take 2)

2008-08-04 Thread Carsten Ziegeler
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,

Re: A new name for Corona (take 2)

2008-08-04 Thread Reinhard Pötz
Carsten Ziegeler wrote: 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

Re: A new name for Corona (take 2)

2008-08-04 Thread Carsten Ziegeler
Reinhard Pötz wrote: Cocoon 2.2 already uses cocoon-pipeline-api-1.0.0, cocoon-sitemap-api-1.0.0., etc. Yes, I know - this complicates things a little bit. What concrete name and version number should we use for what we call corona-pipeline now? cocoon-pipeline-1.0.0 or

Re: A new name for Corona (take 2)

2008-08-04 Thread solprovider
Pick a number that will never be production for the experimental branch e.g. 2.7. Skip a few numbers in case trunk needs another minor number (e.g. 2.3 and 2.4) and to avoid confusion that this branch is not the immediate successor to 2.2. Do not use 2.9 in case a non-Corona pre-release branch

Re: A new name for Corona (take 2)

2008-08-04 Thread Carsten Ziegeler
[EMAIL PROTECTED] wrote: Pick a number that will never be production for the experimental branch e.g. 2.7. Skip a few numbers in case trunk needs another minor number (e.g. 2.3 and 2.4) and to avoid confusion that this branch is not the immediate successor to 2.2. Do not use 2.9 in case a

Re: A new name for Corona (take 2)

2008-08-04 Thread Vadim Gritsenko
On Aug 4, 2008, at 3:01 PM, Carsten Ziegeler wrote: [EMAIL PROTECTED] wrote: Pick a number that will never be production for the experimental branch e.g. 2.7. Skip a few numbers in case trunk needs another minor number (e.g. 2.3 and 2.4) and to avoid confusion that this branch is not the

Re: A new name for Corona (take 2)

2008-08-04 Thread Vadim Gritsenko
On Aug 4, 2008, at 3:49 AM, Ralph Goers wrote: I've never really liked the word pipeline because I tend to think of surfing when I hear it. That isn't altogether bad I suppose, but it isn't altogether accurate either. I tend to think of what Cocoon does more as a pipetree rather than a

Re: A new name for Corona (take 2)

2008-08-04 Thread Ralph Goers
Vadim Gritsenko wrote: On Aug 4, 2008, at 3:49 AM, Ralph Goers wrote: I've never really liked the word pipeline because I tend to think of surfing when I hear it. That isn't altogether bad I suppose, but it isn't altogether accurate either. I tend to think of what Cocoon does more as a