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 
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
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.
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.