[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:                      |
--------------------------------+----------------------------
Changes (by wpsmith):

 * cc: travis@… (added)


Comment:

 While licensing, etc., is not a joke, should be heavily considered, and a
 stance taken with its reasons, I do hope that along with the stance there
 is a known and published process of steps taken against violations (for
 violators and those who wish to report violators) along with a FAQ (e.g.,
 Will my slug be reserved until I am able to change my licensing? Is there
 a probation period (even just a day) where I have the opportunity to
 change my license before any action (delisting, removal, etc.) is taken
 (with explanation)? etc.) and an appeal process (for re-listing/re-
 instating) that is quick and painless.

 I say this because I know a few plugin authors who have created plugins
 using GPLv3 (purely accidentally) because:
  (1) they 'knew' that WP requires plugins to be GPL (but didn't know the
 specifics for whatever reason),
  (2) they may have also seen that WP requires a "GPLv2 or later" statement
 and have confused that statement to mean that GPLv3 is ok,
  (3) they have copied the licensing of another plugin, which just happened
 to be a GPLv3 licensed plugin,
  (4) they were given mis-information by another plugin developer who is
 also in violation unbeknown to them,
  (5) they were a theme author who knew GPLv3 was ok there and didn't know
 that it wasn't ok for plugins in the WP Repo.

 A newer plugin author or someone, who frankly doesn't care about licensing
 (because they don't care to know or it's too problematic), will make their
 GPLv3 without thinking (or thinking that the latest version is the best or
 for whatever reason). When I have mentioned this to a few authors I knew,
 they immediately changed the license of their plugin without a flinch or
 thinking twice. Since WP has such a good community that helps one another,
 I hope that WP would consider publishing a solid process to remove plugins
 and to have plugins re-instated so that plugins can quickly be re-instated
 without too much of a hiccup.

 Nevertheless, there are some authors who won't budge on the licensing
 thing, which is perfectly fine and their prerogative. And if WP only wants
 to support a GPLv2 or later approach, that is perfectly fine (and their
 prerogative) as well. However, having a policy and not enforcing it is
 tragic and creates a de facto policy. Authors who know and have been
 notified (or attempted to be notified) and do not wish to comply even
 after a warning, etc., should be removed, if that's the policy. Just
 something to consider...

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