Consider moving to the GPLv3 license

[frankiejarrett]

While the Apache License 2.0 is considered to be GPL 3.0 compatible, it would be more straightforward to just license the plugin as GPL 3.0 since that is the standard defined and required by the WordPress open source project itself.

You also won't be able to submit this to the WordPress.org plugin repository (#12) unless it is explicitly licensed as GPLv2 or later.

https://wordpress.org/about/license/

[ThemeSurgeon]

I second that recommendation. Would be better to submit the plugin through regular WordPress.org repo for maximum exposure.

[majelbstoat]

We'll chat about this. The plugin has already been submitted to the WP Plugins DB, and is awaiting review.

FWIW, the licensing rules for that state: "Your plugin must be compatible with the GNU General Public License v2, or any later version."

https://wordpress.org/plugins/about/

[ThemeSurgeon]

Thanks Jamie - I am doing a little work on a couple of things that I think will make it easier to get approved by the plugin review team, assuming you are good with that.

Best to you and yours,

John

John Teague Founder Theme Surgeons LLC john@themesurgeons.com https://themesurgeons.com

On Twitter https://twitter.com/themeSurgeon | Google+ https://plus.google.com/+ThemesurgeonsWordPress/

On Thu, Oct 8, 2015 at 12:01 PM, Jamie Talbot notifications@github.com wrote:

We'll chat about this. The plugin has already been submitted to the WP Plugins DB, and is awaiting review.

FWIW, the licensing rules for that state: "Your plugin must be compatible with the GNU General Public License v2, or any later version."

https://wordpress.org/plugins/about/

— Reply to this email directly or view it on GitHub https://github.com/Medium/medium-wordpress-plugin/issues/16#issuecomment-146624226 .

[frankiejarrett]

Thanks for your consideration, @majelbstoat. Yeah, you are right, I just found this post.

So if you have an internal reason for using Apache 2.0, this is apparently fine to do, and it looks like you can be published into WordPress.org repo.

However, if there's no specific reason for choosing this one, then I suppose my suggestion here is just to use the more straightforward license used by the parent project.

Thanks!

[sagudo]

cc @feerst

[majelbstoat]

Having spoken with legal, and having confirmed with a reviewer at WP, for simplicity's sake, we're going to stay with Apache 2, in line with our other open source work. Appreciate your consideration.