Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch PyRadiomics License #268

Closed
JoostJM opened this issue Jul 5, 2017 · 9 comments
Closed

Switch PyRadiomics License #268

JoostJM opened this issue Jul 5, 2017 · 9 comments
Labels

Comments

@JoostJM
Copy link
Collaborator

JoostJM commented Jul 5, 2017

To have a more clear, but still open license, switch from the 3D slicer license to an open license.

No copyleft license, as this is incompatible with the Slicer license (as needed in SlicerRadiomics).

Alternatives:

cc @Radiomics/developers

@JoostJM
Copy link
Collaborator Author

JoostJM commented Jul 5, 2017

Also consider adding disclaimer specifying PyRadiomics is not intended for clinical use
(e.g. print statement in the __init__.py)

@fedorov
Copy link
Collaborator

fedorov commented Jul 5, 2017

Differences between the two alternatives, quoted from https://www.quora.com/Whats-the-different-between-Apache-v2-0-and-MIT-license:

image

@JoostJM
Copy link
Collaborator Author

JoostJM commented Jul 5, 2017

@haarburger, @jbvimort, @jaasantinha, @blezek, @vnarayan13.
I mentioned you here because you are also listed as contributors on PyRadiomics.

@blezek
Copy link
Collaborator

blezek commented Jul 5, 2017

+1 for MIT License. Simple so people don't need to think about it.

@fedorov
Copy link
Collaborator

fedorov commented Jul 5, 2017

Another option is 3-clause BSD, it is also used quite often in the research software. Very close to MIT, but the difference is this part:

Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

@fedorov
Copy link
Collaborator

fedorov commented Jul 5, 2017

Some relevant discussions

Few more data points for the popular open source projects that came to my mind:

I am leaning towards either 3-clause BSD or MIT. Apache-2 is so long!

@vnarayan13
Copy link
Contributor

vnarayan13 commented Jul 6, 2017 via email

@JoaoSantinha
Copy link

JoaoSantinha commented Jul 6, 2017 via email

@jcfr
Copy link
Collaborator

jcfr commented Jul 11, 2017

Moving to an OSI approved license is great. I have no problem with MIT or 3-clause BSD license. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants