Implications of creating a plugin that adds functionality to other developer's plugin?

admin管理员组

文章数量:1332873

I'm thinking in writing a plugin that alow users to import quizes on an existing LMS plugin, that functionality isn't even exists on the paid version of the existing plugin.

Is there any legal impediments of publishing that plugin on the wordpress repositories?.

As this question states, any plugin published on wordpress is under GPL license (the LMS plugin falls in this category), but the paid version is not under those terms.

I don't plan to charge for the plugin, maybe open a donation channel, but mostly I just want to make it as a portfolio item to show to possible employers.

I'm thinking in writing a plugin that alow users to import quizes on an existing LMS plugin, that functionality isn't even exists on the paid version of the existing plugin.

Is there any legal impediments of publishing that plugin on the wordpress repositories?.

As this question states, any plugin published on wordpress is under GPL license (the LMS plugin falls in this category), but the paid version is not under those terms.

I don't plan to charge for the plugin, maybe open a donation channel, but mostly I just want to make it as a portfolio item to show to possible employers.

• plugin-development

Share Improve this question asked Jun 30, 2020 at 17:08 J. R. RamirezJ. R. Ramirez 133 bronze badges

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

If a version of the plugin is available under the GPL then you risk nothing by creating your work and releasing it under the same GPL.

If there's a reason you don't want to publish your code under the GPL, then it gets more complicated.

I referred to this which gives clarity about what is a 'derived' work, and I believe if you use the datastructure or code from another plugin and rely on it for your code to work (e.g. you call a function from that code) then it's reasonable that your project is 'derived' and therefore subject to GPL.

But it's not really worth arguing the point if you're happy to publish it under the GPL anyway - then you're covered either way.

本文标签： Implications of creating a plugin that adds functionality to other developer39s plugin