[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 Rarst):

 Replying to [comment:31 Ipstenu]:

 > Per this: http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility you
 can go from GPLv2 to GPLv3 ''because'' you're permitted to go from GPLv2
 to GPLv2 or later without issues.

 Thanks, missed that mattrix... Note that there is following footnote for
 incorporating GPLv2 code in GPLv2+ project (emphasis mine):

 > While you may release your project (either your original work and/or
 work that you received and modified) under GPLv2-or-later in this case,
 note that **the other code you're using must remain under GPLv2 only**. As
 long as your project depends on that code, you won't be able to upgrade
 the license of your project to GPLv3-or-later, and **the work as a whole
 (any combination of both your project and the other code) can only be
 conveyed under the terms of GPLv2**.

 So you cannot use GPLv2 strict code and call combined work GPLv2+. In my
 opinion this completely kills the idea that GPLv2 is effortless to
 assimilate by core.

 As I see it right now - the only GPL versions, that are effortless to
 combine with GPLv2+, are unversioned GPL or GPLv2+. Or any license that is
 compatible with **all** GPL versions, not just v2.

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