Revisions to Objective Best Practices for Plugin Development? [closed]

Commonmark migration

Source Link

edited Jun 15, 2020 at 8:21

1

License Plugins under a GPL Compatible License

##License Plugins under a GPL Compatible License PlugPlug-ins and themes should be licensed under a WordPress-compatible license. This enables them to be re-distributed with WordPress as a "program." A recommended license is the GPL. Take care that all code libraries included with the plug-in are compatible with the same license.

(This has been a problem and serious point of debate both in the past and present.)

replaced http://wordpress.stackexchange.com/ with https://wordpress.stackexchange.com/

Source Link

edited Apr 13, 2017 at 12:37

Community Bot

1

##License Plugins under a GPL Compatible License Plug-ins and themes should be licensed under a WordPress-compatible license. This enables them to be re-distributed with WordPress as a "program." A recommended license is the GPL. Take care that all code libraries included with the plug-in are compatible with the same license.

(This has been a problem been a problem and serious point of debate point of debate both in the past and present.)

Grammar cleanup, added reference to GPL

Source Link

edited Aug 25, 2010 at 20:41

EAMann

32.2k
9
88
147

##License Plugins under a GPL Compatible License AddPlug-Onsins and themes should be licensed under a WordPress-compatible license. This enabledenables them being able to be re-distributed with WordPress as one software programa "program." A fitting one is the GPL itself. Take care that all code libraries included with the plugin are compatible with thatrecommended license toois the GPL. Take care that all code libraries included with the plug-in are compatible with the same license.