What is the appropriate license for third-party plugins?
-
Sorry if similar questions have been asked in the past. I could not find.
I'm trying to create a third-party plugin as a corporation.
Is the appropriate license GPL?
I'm sure there are cases where we don't want to OSS, so I'd like to be sure. -
@mitu the DWC itself is GPL, so it is not allowed to modify it without disclosing the changed sources. The DSF plugin is LGPL (lesser GPL), this is allowed to change and use commercially without disclosing sources. So if you create a plugin under license LGPL like the DSF plugin, you can create and change without disclosing analogue to DSF plugin. You can see the license in the LICENSE file in the root directory of the project.
In the past was discussion whether it is allowed to LGPL a library which is connected to a GPL main program (e. g. at LINUX, which is GPL), and the answers were different. It depends on the kind of linkage. DSF plugin is already LGPL, so I expect my answer to be ok.
I am no lawyer. I am sure about my answer, because it was a topic in my job, but nevertheless my answer is without liability.
To answer your direct question: to license your plugin under GPL would not be ok, as explained. Use LGPL instead.
-
@mitu if in doubt, talk to the copy rght holder (i.e., Duet3D). They may be open to dual license DWC under the right circumstances.
As an end user who chose Duet3D exactly because its open source hardware and software, I'd be disappointed if someone benefited from this graciousness without reciprocating. But maybe I am not your target audience.
<>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>
-
if you create a plugin under license LGPL like the DSF plugin, you can create and change without disclosing analogue to DSF plugin.
I had the same understanding, but it was helpful to get another opinion.
I have plans to create many plug-ins for our products in the future, and while I would like to make them OSS as much as possible, I was worried about handling plug-ins that might contain sensitive information, but it looks like it will be no problem.
Thank you for your response. -
if in doubt, talk to the copy rght holder (i.e., Duet3D). They may be open to dual license DWC under the right circumstances.
that's right, I will consult to copy right holder
Please let me know that you would like to release it as OSS as much as possible.
I just had a hard time handling it when it contained confidential company information
