-
Notifications
You must be signed in to change notification settings - Fork 68
Use Apache-2.0 license for workspace #416
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
Conversation
|
@Jake-Shadle thank you for your contribution! I think smth is wrong with the formatting here. @somtochiama What do u think? This PR essentially replaces the Apache license with an MIT one, wdyt? |
|
@gorbak25 @Jake-Shadle I think we should keep the Apache license and remove MIT instead. It seems to be the default for our open-source projects. It'll also not require an ack from contributors. |
gorbak25
left a comment
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.
lgtm
somtochiama
left a comment
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.
@Jake-Shadle ty!
nit: I think it might be better to have just the license change in this PR
As mentioned in #415 most of the crates in this workspace did not specify their
license, but the ones that did usedMIT, so this setsMITApache-2.0as thelicensein the workspace, along with theedition,repository, andhomepagefields and uses them for all crates in the workspace.This includes an update to the 2024 edition since the version in rust-toolchain is already specified as 1.88.0 and the 2024 edition was introduced in 1.85.0, but I can split out that change if wanted, but it's mostly just changes in rustfmt, only a few changes in the code itself.
Resolves: #415