-
Notifications
You must be signed in to change notification settings - Fork 28
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
Re-license under apache and MIT #53
Comments
I've submitted a PR so that everyone can precisely see how the change would look like: #54 . It not only triple-licenses the library, but also requires all future contributions to be triple licensed as well. |
This license is fine with me. |
fine by me!
|
fine with me as well |
fine by me. |
I'm fine with this re-license too |
This is fine by me. |
It is fine for me too ! |
I'm not very familiar with licensing, and if this doesn't affect our usage of mach in servo, I agree. |
@gterzian servo can still license the library under the exact same terms (2-clause-BSD license). Multiple licensing means that you can pick the license that suits you best. |
👍 sounds good to me! |
Ping @dcuddeback and @lashomb, it has been almost 2 weeks since first call. |
@dcuddeback @lashomb - ping |
@fitzgen in the current license you are the sole copyright holder for the crate. I am not sure if this implies that you are able to re-license the crate at will, but it might be possible for you to do so. I've tried contacting both @dcuddeback and @lashomb (which only fixed some typos) privately per email without any luck. So I don't think they will respond any time soon. |
The
mach
crate is currently licensed under the 2-clause-BSD license. To be able to use themach
crate fromlibstd
, it would help if we could re-license the library (including all contributions), under the same licenses the Rust project uses: the MIT License and the Apache License 2.0. That is, the library would be available under 3 licenses: 2-clause-BSD/MIT/APACHE2.0.These are all mach contributors:
Would you all agree to that ?
The text was updated successfully, but these errors were encountered: