[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:14 nacin]:
 > > GPLv3 (and so Apache) is compatible with "GPLv2 or any later version".
 >
 > It's one-way compatibility. A GPLv2 or later project cannot use code
 that is GPLv3, as the code is not licensable under GPLv2.

 Let's put it like this - there is no '''licensing''' reasons WordPress
 plugin or theme cannot be licensed under GPLv3 or Apache License 2.0,
 correct?

 There is '''organizational''' reason that plugin or theme under
 GPLv2-compatible license are easier to assimilate in core. Which is
 currently put in writing as repository rule.

 My points are, that rule is:

  1. Inconsistent (theme repository allows GPLv3).
  2. Serves extreme edge case (amount of plugins ever assimilated in core
 seems to be put at two digits, total amount of plugin in repository at
 five digits).
  3. Detrimental for plugins quality by cutting off use of open source
 components.
  4. De-facto ignored by developers and repository personnel (my subjective
 impression that I will try to backup in near future by some numbers).

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