--===============1274304423==
Content-type: multipart/signed; boundary=nextPart1351247.xB0ZczPc0O;
 protocol="application/pgp-signature"; micalg=pgp-sha1
Content-transfer-encoding: 7bit

--nextPart1351247.xB0ZczPc0O
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Saturday 23 June 2007 17:14, Tom Albers wrote:
> Hi Guys,
>
> Last time I send a mail regarding such a topic I  promised myself to
> never ever try a license change again.
>
> We are now faced with stalled development and frustration. In
> particular kpimidentities has the interest of both Mailody and for
> example Kopete. There is also interest in all the crypto things
> (kleo, kgpg & co), see the kde-commits thread of today.  I think one
> the strong things within KDE is the level of integration. The current
> situation is undermining that.
>
> So I would like to know how to proceed. I see a few options:
> 1) people agree with the GPL->LGPL requests
> 2) we lift the LGPL requirement for kdepimlibs
> 3) we create a kdepimlibs-gpl with gpl libraries
>
> Personally I don't need it to be LGPL so I would go for option 2 and
> let the parties who do require LGPL to worry about needed license
> changes.

I don't think 1) is an option for the crypto stuff (but you can of=20
course ask Marc :-) ). I am very much in favor of 3).

Regards,
Ingo

--nextPart1351247.xB0ZczPc0O
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBGfYJRGnR+RTDgudgRAnmhAJ9uX+4rrlhyNQoQurcKvECAQqF+QACgoB20
5j5s1jx8dK1bT0vVvCPpB24=
=AX0+
-----END PGP SIGNATURE-----

--nextPart1351247.xB0ZczPc0O--

--===============1274304423==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
--===============1274304423==--