[wp-hackers] WordPress and GPLv3
r at schestowitz.com
Sat Dec 29 12:28:06 GMT 2007
-----BEGIN PGP SIGNED MESSAGE-----
> I tend to be of the opinion that "if it ain't broke, don't fix it".
> Otto, Roy, whomever:
> Can anyone give us a _specific_, _concrete_, and _compelling_ reason why
> remaining with GPL2 is BAD, or why moving to GPL3 is GOOD.
> _Specifically_, as relates to WordPress: How is WordPress _harmed_ by
> remaining with v2, or how is it _improved_ by moving to v3.
> Beyond those questions, this is really all academic and mostly off-topic.
> P.S. -- I do actually find this discussion interesting when it doesn't
> degenerate into "who's being offensive"; but let's bring it back to
> Earth, and back to practicalities related to _our specific software_.
There are several hypothetical scenarios which come to mind:
1. Patent intimidation and settlements can be used to divide
and separate 'licensed' WP from 'unlicensed' WP.
2. Closing of the code -- however partial it might be -- can be
achieved through loopholes. Some examples have been mentioned in
3. Developer affinity. I am aware of various developers to whom
GPLv3 has a special appeal. It represent a step forward rather than
complacence. Drupal can use this as a competitive advantage that
attracts programmers and software-savvy bloggers. MT is one to
watch out for as well.
4. Compatibility (long-term sight). I don't know where pertinent
packages like TinyMCE are headed, but it's worth finding out.
~~ 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)
-----END PGP SIGNATURE-----
More information about the wp-hackers