*Looks for coffee, finds none.*
I’m not on the plugins team but AGPL is incompatible with the GPL. A plugin can’t be declared AGPL as WordPress is GPL
]]>Ha! I’m probably wrong. ??
https://www.gnu.org/licenses/agpl.html
I don’t think it would work in the WordPress repo but as Andrew wisely wrote, check with the plugins team.
]]>The AGPL adds the requirement that, if you run a modified version of code on a server, then you must allow others to download that modified source code from the server as well.
For a plugin in particular, this presents problems with regards to end-users, who may not know how to offer such a download in order to comply with the license. Yet they may modify their plugin to better fit their needs, or to fix issues specific to their server. By so doing, they might unknowingly violate the license, and that’s something we would probably prefer to avoid.
]]>I’d like to release my plugin under the AGPL to WP.org because:
It is for that reason I don’t believe WordPress would “probably not allow plugins using the Affero GPL”. @otto42 If possible, could you please double-check with legal and help keep us updated? This is the first thread in 6 years (as far as I can tell) to bring up AGPL here on the forums, and I’d hate to see the discussion squashed by probabilities without regard for possibilities.
Thank you kindly for your support.
]]>If you want to continue hosting your plugin on Github or your own site, then you can do so there.
]]>We require plugins in the directory to be licensed in ways that are GPL-Compatible, for our own reasons. Not because we are legally obligated to do any such thing, but because that is *our* policy.
So, we won’t accept AGPL licensed code because it is incompatible, and because it does not align with *our* policies for the directory. This is not a legal opinion, because the law is not involved in this decision in any way. Our directory, our hosting services, our rules.
]]>