[wp-trac] [WordPress Trac] #16898: Fix plugins about page license requirement

[WordPress Trac]

#16898: Fix plugins about page license requirement
--------------------------------+----------------------------
 Reporter:  scribu              |       Owner:
     Type:  feature request     |      Status:  new
 Priority:  normal              |   Milestone:  WordPress.org
Component:  WordPress.org site  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:                      |
--------------------------------+----------------------------

Comment (by WraithKenny):

 {{{
 "We're already in the situation where some plugin directory code is
 GPLv2-only
 instead of GPLv2+, so combining that plugin code with WordPress already
 requires care." ~ Mark Jaquith
 }}}

 This (the difficulty in integrating code) is the same case made against
 allowing GPLv3 code in the repos. For consistency sake, should we change
 the policy to disallow GPLv2-only plugins (or any containing GPLv2-only
 code) and purge those from the repos? (Rhetorical; I don't seriously
 suggest this.)

 OK, so a break down of the concerns are:
 {{{
 "I would also hate for me to pick up code or an idea from a plugin that
 is licensed in an incompatible way and then end up using that in core,
 thereby doing quite a bit of damage." ~ Nacin
 }}}
 and
 {{{
 "It makes integrating code/idea from plugins into core impossible if
 the plugin is GPLv3." ~ Otto
 }}}

 First, copyright doesn't apply to ideas (that's in the realm of patents),
 only copy (text, writing, code implementations etc). Having an idea
 inspired by GPLv3 code doesn't bar you from implementing that idea in
 GPLv2+ code.

 Next, "integrating" the code is problematic in that you can't wholesale
 copy the code in - that's correct, but you can re-implement the idea,
 which is usually what happens eventually anyway. (You can copy it though
 if the implementation is short and obvious; see below.) So it's merely
 less convenient perhaps.

 Lastly, you don't have to be concerned with incidentally or accidentally
 copying short or obvious code (such as `$var = '';` or maybe even longer
 codes) as short or obvious copy (subjective, I know) isn't copyright-able
 (or even patent-able).

 Basically, and in summary, your not going to "accidentally" remember
 enough of the code to re-implement it as originally "expressed" as to
 trigger the copyright. The only way to "infect" core with GPLv3 code is to
 copy it in on purpose.

 {{{
 "Copyright does not protect facts, ideas, systems, or methods of
 operation,
 although it may protect the way these things are expressed."
 ~ http://www.copyright.gov/help/faq/faq-protect.html
 }}}

 The other concern is:
 {{{
 "Some people will not use or work on GPLv3 code.
 It's incompatible with too many things. " ~ Otto
 }}}

 WordPress Core's code will still be GPLv2+ and those people can still work
 on it. The code in the plugins doesn't change this. Most plugins are also
 GPLv2+ and those people still can work on those plugins and incorporate
 them into their projects. No one is required to incorporate any plugin
 code into their own work if they don't want; it's all optional and
 voluntary.

 Now for the Pros: We can use libraries in our plugins that we can't under
 GPLv2 licenses and we avoid an unnecessary and somewhat arbitrary
 limitation on developer and user freedoms.

 This concludes my argument in favor of officially allowing GPLv3 plugins.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/16898#comment:48>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software