From kde-core-devel Tue Nov 02 09:50:04 2010 From: Chani Date: Tue, 02 Nov 2010 09:50:04 +0000 To: kde-core-devel Subject: Re: "Cornelius's grand plan" - Merging KDElibs into Qt Message-Id: <201011021050.04740.chanika () gmail ! com> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=128869137301414 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart1361268.mlbn5BaaKT" --nextPart1361268.mlbn5BaaKT Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On November 1, 2010 09:39:56 Michael Jansen wrote: > > it could work out great, it could be a disaster, it could be a lot of > > work for a little gain ... we just can't tell right now because it's > > nothing more than a vague idea. > >=20 > > you really can't plan the future of core assets like that. >=20 > But preparing our our assets in a way that would make identifiying and > merging stuff into qt easy would benefit our visibility even if the > merging never happens. >=20 +1 - this has been a great brainstorming exercise. :) there are certainly obstacles to the "merger" idea, and a fair chance of it= =20 turning out to be infeasible or unwanted (while I hope the open governance= =20 thing keeps improving, I'm not going to put blind faith in it) but it got u= s=20 thinking, didn't it? :) modularizing and promoting kdelibs looks like something we can all agree=20 should be done. separating it into generally-useful features vs. workspace= =20 integration features, allowing people to use just some of it, *telling* the= m=20 what we have and how easy it is to use it and why it'll make their applicat= ion=20 shoot magical rainbow lasers ;) =2E..so now I suppose it's time to start doing it. Not the actual modulariz= ation=20 right away, of course, but planning what can be done and documenting what w= e=20 have and advertising to people outside kde that yes, we have these features= =20 and they're great and you want to use them even if it does mean linking to= =20 some other stuff right now. :) =2D-=20 Chani http://chani.ca --nextPart1361268.mlbn5BaaKT Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEABECAAYFAkzP3swACgkQeGbAwpIS3GynLgCgoupKTl68erTcLMWn47ldJoab lnQAn2Fizbfh/xlSvOJ0h9lanpP2SrZU =SECb -----END PGP SIGNATURE----- --nextPart1361268.mlbn5BaaKT--