You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I've seen a few reviews on this great project - all talking about this project being open source. I don't see a license file here though, so currently it's still "all rights reserved". Is the intent to turn this project open source? The current unclarity will stifle its integration by others, as there's the legal uncertainty of what will happen if a company tries to integrate this.
If you're intending to actually use a free license, there probably are two options to consider. The first one is a more liberal license like MIT, the other one a more protective license like GPL. I'll just set a start here for discussing the basic pros and cons of both.
MIT
It's the easiest one to apply. Basically you're saying: go ahead and use it in what ever way you want. Just don't take credit for the code. Pro: it's very easy to adopt, and third parties can quickly and easily implement your work. Con: Third parties don't need to keep their changes to the code open, allowing them to create improved versions of your work without sharing them in a same way
GPL
This license basically states you have the right to view, modify and redistribute the code, but you have to give credit and also offer source code if you redistribute changes to the code. Pro: This is the best way to make sure that improvements by third parties trickle back to the original project. Con: Some will refrain from using code because of this requirement.
Not an expert, but just getting a start to a discussion...
The text was updated successfully, but these errors were encountered:
I have not assigned a main license but instead added LICENSE.TXT files to each folder with their respective licenses. Blender Addons for instance require a certain license as per the Blender Foundation and the models folder has a different license and once the fab files are uploaded they will have a different license as well. Because this project has so many moving parts I don't think one encompassing license will do. The intent is to keep it as open as possible.
Hi,
I've seen a few reviews on this great project - all talking about this project being open source. I don't see a license file here though, so currently it's still "all rights reserved". Is the intent to turn this project open source? The current unclarity will stifle its integration by others, as there's the legal uncertainty of what will happen if a company tries to integrate this.
If you're intending to actually use a free license, there probably are two options to consider. The first one is a more liberal license like MIT, the other one a more protective license like GPL. I'll just set a start here for discussing the basic pros and cons of both.
MIT
It's the easiest one to apply. Basically you're saying: go ahead and use it in what ever way you want. Just don't take credit for the code.
Pro: it's very easy to adopt, and third parties can quickly and easily implement your work.
Con: Third parties don't need to keep their changes to the code open, allowing them to create improved versions of your work without sharing them in a same way
GPL
This license basically states you have the right to view, modify and redistribute the code, but you have to give credit and also offer source code if you redistribute changes to the code.
Pro: This is the best way to make sure that improvements by third parties trickle back to the original project.
Con: Some will refrain from using code because of this requirement.
Not an expert, but just getting a start to a discussion...
The text was updated successfully, but these errors were encountered: