-
Notifications
You must be signed in to change notification settings - Fork 185
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
Proposed license change to Apache-2.0 #997
Conversation
2caccf0
to
653a063
Compare
Tasks:
|
The number of reviewers is limited to 15. Therefore, @jan-matthis @manuelgloeckler @famura @gmoss13 @ppjgoncalves @psteinb @tomMoral @jnsbck @coschroeder @LouisRouillard @bkmi @dgreenberg @rdgao @alvorithm @danielmk @jsvetter @ybernaerts @plcrodrigues @conormdurkan @lappalainenj @jahma @JuliaLinhart @tbmiller-astro @Ziaeemehr @sethaxen @ADelau @ImahnShekhzadeh @VictorSeven @narendramukherjee @MilesCranmer, if cannot approve above please express your view on the license change by commenting below. Many thanks 🙏 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #997 +/- ##
==========================================
+ Coverage 76.37% 77.03% +0.65%
==========================================
Files 84 90 +6
Lines 6507 6615 +108
==========================================
+ Hits 4970 5096 +126
+ Misses 1537 1519 -18
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Yes, I fully approve this change, and believe it would be important to keep the sbi toolbox sustainable! |
This sounds great. I 100% support this. |
I approve this change, thanks @janfb! |
approved! |
I am in favor of commercially permissive licenses. Personally I use MIT most of the time for my small projects but I fully support the change to Apache-2.0 for sbi. |
approved. |
Very much in favor of this change 👍 |
Approve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approve
Approve also. |
I approve! |
Approve |
Approve |
approved! |
Happy to approve! |
I approve of this |
Sounds good to me! |
LGTM! |
I approve |
I think this is a good change, approved |
LGTM! Thank you! |
e9579c0
to
77e5082
Compare
77e5082
to
c523f1d
Compare
While in general I remain a proponent of strong copyleft licenses, I also wholeheartedly share the goal to make sbi (and pyknos) approachable for a wider community of users and developers. Acknowledging compelling arguments made by fellow team members, I am now keen to find out in practice to what extent adopting a weaker copyleft for these projects might help to that end. Hence, I approve relicensing sbi under the Apache 2.0 license. |
The change from |
Dear SBI contributors,
After extensive discussions, we, the initial copyright-holders of the
sbi
repository (Jan, Michael, Álvaro, Jan-Matthis, Conor, and Jakob), propose to relicense thesbi
library under theApache 2.0
license. Below, we provide the background and rationale for this change.Proposed change
Up until now, the
sbi
repository was licensed under the AGPLv3 license which has a strong copyleft. We suggest changing the license to the Apache 2.0 license. TheApache 2.0
license is a permissive license, (likeMIT
orBSD3
) and is also used in several other open-source projects such as PyMC or ArviZ.Why do we want to change the license?
Many former
sbi
contributors have moved on from academia and into industry, but the strong copyleft of theAGPLv3
license restricts the use of thesbi
toolbox in their new job: Corporate lawyers usually veto contributions to strong-copylefted code bases to avoid potential litigation. We know our current choice of license limits contributions fromsbi
users now with private companies and suspect that it might be a deterrent for future ones. After extensive discussions about the implications, we are suggesting to adopt a weak copyleft (‘liberal’ or ‘permissive’) license. We believe that the risk that companies usesbi
without giving back to the community is worth the additional community buy-in we expect. We hope that looking at the affiliations of contributors over time will help us understand better this trade-off based on actual data.Contributor approval for license change
A license change requires the consent of all copyright holders. Each individual who has contributed code to the
sbi
repository holds the copyright for their specific contribution. As such, we need unanimous agreement from all contributors for the proposed license change (minor amendments, such as typo corrections, do not fall under this rule). Thus, we kindly ask all contributors to express their views on the proposed license change, either by approving this pull request, commenting below that they agree, or by starting a discussion if they have any concerns.Thank you very much and all the best!
Jan, Michael, Álvaro, Jan-Matthis, Conor, Jakob