[discuss] Limewire license compatible with GPL3?
Matthew Toseland <[email protected]> Fri, 7 Sep 2007 18:27:01 +0100
| Newsgroups | gmane.network.gnutella.limewire.general |
|---|---|
| Message-ID | <[email protected]> |
--===============8646642095426848394== Content-Type: multipart/signed; boundary="nextPart1886179.ZMJNoH6DJM"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1886179.ZMJNoH6DJM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline We have reused some of Limewire's code (related to Universal Plug and Play= =20 support) in Freenet (actually in a freenet plugin). Is Limewire=20 GPL3-compatible? It's not clear in Freenet, for example, because we didn't= =20 have explicit license headers in most of our files and just included=20 COPYING ... so it could be read as GPL2-only rather than GPL2-or-later. The= =20 file in question is com.limegroup.gnutella.UPnPManager. Thanks. Matthew Toseland, Freenet Project chief developer. --nextPart1886179.ZMJNoH6DJM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBG4YnmA9rUluQ9pFARAuvYAKC8d2AUH/8bUDh3qjAulAhpWWjDiACfZ0A3 bNAodFMAjS5lUlgfpSF5Lcg= =SiRK -----END PGP SIGNATURE----- --nextPart1886179.ZMJNoH6DJM-- --===============8646642095426848394== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ discuss mailing list [email protected] http://lists.limewire.org/mailman/listinfo/discuss --===============8646642095426848394==--