-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Relicense {fmt} to make it more friendly for standard library vendors #1073
Comments
Boost Software License (BSL) also has no binary requirement.
|
This is similar to https://github.com/apple/swift/blob/master/CONTRIBUTING.md with an explicit clause that allows changing license for #1073.
That's fine with me! |
I agree to the changes |
By the way, I am the artist formerly known as just "Brian" on this list, so you can remove it. |
As a note, mwinterb and Michael Winterberg are the same. Unless there's another Michael Winterberg out contributing :) |
I agree to the changes. |
No objections. |
I agree with changing the license! |
I agree to the changes! |
I agree to the changes. |
I agree to license changes as well. |
I agree as well :) |
I agree to the changes. |
1 similar comment
I agree to the changes. |
That's ok with me. |
I agree to the changes. |
LGTM, I agree +1 |
Late to the party. Agreed! |
Please stay far, far, far away from CLAs -- they are a huge pain that can add significant hurdles to contribution or even make it legally impossible to contribute. My own experience with this has been with Microsoft/vcpkg; they require signing a CLA in order to open a PR to add a package. I sent the legal department at work an email asking for permission to sign the CLA at the beginning of the year -- it has not been approved because of some "indemnity clause", and they have offered no alternatives for how we can get a package submitted (nearly 6 months later). To be clear, the code for adding a package could legally be open sourced, but because of the CLA it's impossible for me to contribute that change upstream. I've even asked if I could prepare the package and open the PR on my own time so that I could sign the individual CLA instead, and the answer was basically no (submitting the package would be too similar to the project I was getting paid to work on). And this restriction applies no matter how trivial the change is. Some of the writing on the subject (DCO would be much easier for contributors at companies than a CLA): Beyond that, an unmodified license that fulfills the requirements you're looking for (Boost as suggested above?) might be easier to get past corporate legal departments than one with exceptions added (ZeroMQ LGPL with static linking exception raised some questions) -- at least as far as upstreaming any changes go. I know where I work legal gives a bit more scrutiny to contributions to OSS projects if their chosen license also covers patents. |
BSD will continue to be an option so exception is not a problem. |
All current contributors to
|
I have no objections to changing the license terms. |
I agree to the changes. |
I do of course agree to changing license terms in any way you see fit. |
I am fine with the changes. |
The new license draft: https://github.com/fmtlib/fmt/blob/master/LICENSE.rst |
According to Billy O'Neal, the standard library vendors (including libstdc++) all can't look at BSD-licensed code. To fix this we need to drop all requirements on binary redistribution, e.g. introduce a clause similar to "LLVM Exceptions to the Apache 2.0 License":
See also http://llvm.org/foundation/relicensing/
Also might be a good time to introduce CLA: https://github.com/cla-assistant/cla-assistant
List of current library contributors from blame:
The text was updated successfully, but these errors were encountered: