Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Mime-Version: 1.0 (Apple Message framework v746.2)
In-Reply-To: <20060104085502.52218.qmail@web26812.mail.ukl.yahoo.com>
References: <20060104085502.52218.qmail@web26812.mail.ukl.yahoo.com>
Content-Type: multipart/signed; protocol="application/pgp-signature";
 micalg=pgp-sha1; boundary="Apple-Mail-1--854627571"
Message-Id: <FCE83B20-417E-490F-81BA-54136FCB4578@apache.org>
Content-Transfer-Encoding: 7bit
From: Torsten Curdt <tcurdt@apache.org>
Subject: Re: The Apple-Intel analogy
Date: Wed, 4 Jan 2006 10:19:22 +0100
To: dev@cocoon.apache.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-1--854627571
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII; format=flowed

> I think the Apple move to Intel processors is a good
> example.

Same here!

> Apple is changing its fundaments but the
> building above, the operating systems, remains the
> same and all your applications won't stop to work.

That's not true ...you have to port applications to
the new platform. But Apple has prepared developers
very well on how to do the migration. Of course we
would have to that too.

> The
> average user won't even notice that the processor has
> changed.

Let's hope they will ;)

> IMO Cocoon should go the same way. The recent thread
> about a complete rewrite of Cocoon *really* scares me
> and a lot of people I've talked to as it will break
> compatibility for sure.

Fear has always been the main blocker for new technologies.

I thought it was already clear that what (I think) most
people want is not necessarily to really rewrite from
scratch but the freedom to reevaluate and change every-
thing if they think it's a good change ...without the
"no, we cannot do that to our existing customers"

There is no doubt we need migration strategies ...but
there is also no doubt we are currently locked into
some not even so clear and old contracts.

THIS is what people (or at least I) want to change.

<snip/>

> I also consider it as dangerous as it might
> lead to fractions within the community and we start
> again to split our limited time that we can dedicate
> to the devleopment of Cocoon into two projects for
> years (again).

I am sure it will also create fraction if we don't
move on with some innovations that are just too much
for the current codebase.

cheers
--
Torsten


--Apple-Mail-1--854627571
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFDu5MfBGM6V3wgCUERAn6/AJ90kJjdYa41U+ZLgssgzeA9LbXF7ACdEWZx
dwTEcN6couwDe6G+Yso3uj4=
=Sg8b
-----END PGP SIGNATURE-----

--Apple-Mail-1--854627571--