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

Change license from LGPL to MIT #365

Merged
merged 2 commits into from
Nov 2, 2023
Merged

Change license from LGPL to MIT #365

merged 2 commits into from
Nov 2, 2023

Conversation

landreman
Copy link
Contributor

Presently simsopt has the LGPL license. In the new world of private stellarator companies, this license is proving to be a complication. I’m most familiar with the perspective from Type One Energy, for which I do some consulting and where @mbkumar now works. Although scientists at the company are adding features to a private fork of simsopt, lawyers are advising them not to push these improvements to the public simsopt repo because the LGPL license could require open-sourcing of other proprietary code. The company is unsure about continuing to use simsopt generally due to this risk of the LGPL license affecting their IP. It would be better for everyone if the companies felt free to push improvements to the public repository so all users can benefit.

So, I propose we change the license to the MIT license. More information about the differences can be found here, here, and other sites. To change the license, my understanding is that we should get approval from everyone who has contributed code under the previous license: @mbkumar @florianwechsung @ejpaul @akaptano @rogeriojorge @abaillod @MigMadeira @mishapadidar @tmqian @kchammond @zhucaoxiang @phuslage @migueljmp @smiet @AlexWiedman @jons-pf @rahulgaur104 @andrewgiuliani @TacitusQ @jloizu @StanczakDominik @zhisong kindly approve the pull request or reply below to let us know if you approve of the change. If you have any concerns, let me know.

akaptano
akaptano previously approved these changes Oct 19, 2023
andrewgiuliani
andrewgiuliani previously approved these changes Oct 19, 2023
mbkumar
mbkumar previously approved these changes Oct 19, 2023
rahulgaur104
rahulgaur104 previously approved these changes Oct 19, 2023
rogeriojorge
rogeriojorge previously approved these changes Oct 19, 2023
zhucaoxiang
zhucaoxiang previously approved these changes Oct 19, 2023
ejpaul
ejpaul previously approved these changes Oct 19, 2023
abaillod
abaillod previously approved these changes Oct 19, 2023
@kchammond
Copy link

This is fine with me.

@migueljmp
Copy link
Contributor

I approve

@MigMadeira
Copy link
Contributor

I approve the change

@jloizu
Copy link
Contributor

jloizu commented Oct 19, 2023 via email

@jloizu
Copy link
Contributor

jloizu commented Oct 22, 2023 via email

@landreman
Copy link
Contributor Author

Hi again, Since we at EPFL are very minor contributors, we do not want to oppose or stop the process for tool long, but I do have a question: it seems the Apache license is essentially as open as the MIT but ensures a reference to the origin of the code, which may be good, and about what has been changed, if I understood correctly. Why not Apache license instead of MIT? Thanks, Joaquim

@jloizu As I understand it, the MIT and Apache licenses are quite similar in practice, both being in the permissive rather than copyleft category. Apache has a rule that derivative works must state changes made from the original version, which seems like a minor chore/annoyance. It looks like MIT is significantly more popular than Apache. Unless other people here favor Apache over MIT, I’d suggest we stick with MIT since most of the contributors here have already approved it.

@jons-pf
Copy link
Contributor

jons-pf commented Oct 23, 2023

FYI, I use the Apache license for most of my OSS projects, but I agree that the MIT license can be described as even "less annoying". Let's stick with MIT for SIMSOPT.

@codecov
Copy link

codecov bot commented Oct 23, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (51b37b4) 91.46% compared to head (1abdaf4) 91.38%.
Report is 53 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #365      +/-   ##
==========================================
- Coverage   91.46%   91.38%   -0.08%     
==========================================
  Files          72       72              
  Lines       12825    12700     -125     
==========================================
- Hits        11730    11606     -124     
+ Misses       1095     1094       -1     
Flag Coverage Δ
unittests 91.38% <100.00%> (-0.08%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
src/simsopt/_core/dev.py 42.85% <ø> (ø)
src/simsopt/_core/finite_difference.py 94.06% <ø> (ø)
src/simsopt/_core/json.py 83.67% <ø> (ø)
src/simsopt/_core/optimizable.py 90.35% <ø> (ø)
src/simsopt/_core/types.py 100.00% <ø> (ø)
src/simsopt/_core/util.py 87.64% <ø> (ø)
src/simsopt/geo/__init__.py 100.00% <100.00%> (ø)
src/simsopt/geo/finitebuild.py 100.00% <100.00%> (+0.53%) ⬆️
src/simsopt/geo/framedcurve.py 100.00% <100.00%> (ø)
src/simsopt/geo/strain_optimization.py 100.00% <100.00%> (ø)
... and 16 more

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

jloizu
jloizu previously approved these changes Oct 25, 2023
Copy link
Contributor

@jloizu jloizu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I approve the change of license.

smiet
smiet previously approved these changes Oct 25, 2023
@smiet
Copy link
Contributor

smiet commented Oct 25, 2023

We're good at EPFL as well! Thanks for the patience!

tmqian
tmqian previously approved these changes Oct 26, 2023
Copy link
Collaborator

@tmqian tmqian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good to me! Thanks for the helpful links.

@mishapadidar
Copy link
Contributor

this is okay with me

@landreman
Copy link
Contributor Author

Everyone who contributed code has now approved the change. Thank you to all of you for responding.

@landreman landreman merged commit 4da5214 into master Nov 2, 2023
56 of 57 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.