To me:
* throwing away the collected work of the community
* building something rather different
* throwing away a strong brand
* leave all the users who has put a trust in us behind
seem like a rather strange way of "saving" Cocoon.
I will continue to be proud of our brand, our product and our community.
And I will continue the work on *Cocoon* towards the future in an
evolutionary way, so that those who have put their trust in us have a
reasonable migration path to follow.
IMO the most important step towards getting an uppwards spiral again is
by regaining our and our communities faith in Cocoon, by keeping our
promisses and do a 2.2 release. Instead of running like lemmlings
towards the next shiny thing.
We should focus on our core offerning and getting the parts of it
reusable outside Cocoon and of high quality, following the path outlined
by Marc.
For you attention seekers out there, OSGi based blocks will draw a lot
of attention towards Cocoon, and it is innovation, not immitation.
/Daniel
Ugo Cei wrote:
Il giorno 06/dic/05, alle ore 01:24, David Crossley ha scritto:
I started to draft here what the next-generation Cocoon should be. I
dubbed it "Racoon" (with Andrew's permission) as I really think that
from a marketing point of view, a new name should be used so that
people
don't see it as a publication engine, as too many people still see
Cocoon.
Please don't. Cocoon is the name.
I agree that we must keep the Cocoon name, but even if we decide to
change it in the end, please not "Racoon". From a marketing
standpoint, it will always be interpreted as meaning "almost like
Rails, but not the real thing".
