-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> On 12/29/07, Roy Schestowitz <r@xxxxxxxxxxxxxxx> wrote:
>> 2. Closing of the code -- however partial it might be -- can be
>> achieved through loopholes. Some examples have been mentioned in
>> this thread.
>
> Please explain this in more detail. The GPLv2 has no loopholes that I
> am aware of. There is no way to close the code.
By closing of the code I was actually referring to:
1. Binary bridges/shims, a la Novell.
2. Exclusive permission to run code, 'thanks' to software patents.
3. To an extent -- Tivoization. It's not closing of the code (similar
to (2)), but it's a restriction on execution, so openness has its
purpose beaten.
- --
~~ Best of wishes
Roy S. Schestowitz
http://Schestowitz.com | GNU/Linux | PGP-Key: 0x74572E8E
Freelance journalist @ http://itmanagement.earthweb.com/
GPL-licensed 3-D Othello @ http://othellomaster.com
Open Source, non-profit search engine proposal @ http://iuron.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHdvP+U4xAY3RXLo4RApbJAJ4nlu4wWCXTCkwWEvCdbsFgFBvaJQCgigtD
UEWCJ2veLkfjUHYf87NrF1w=
=tXVl
-----END PGP SIGNATURE-----
_______________________________________________
wp-hackers mailing list
wp-hackers@xxxxxxxxxxxxxxxxxxxx
http://lists.automattic.com/mailman/listinfo/wp-hackers
|
|
