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.

Sign up for GitHub

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

Jump to bottom

[DISCUSSION] Relicense Ambient under dual MIT/Apache-2.0 #160

Closed
AngelOnFira opened this issue Feb 23, 2023 · 5 comments
Closed

[DISCUSSION] Relicense Ambient under dual MIT/Apache-2.0 #160

AngelOnFira opened this issue Feb 23, 2023 · 5 comments
Assignees
@FredrikNoren

Comments

@AngelOnFira
Copy link

I'm not sure where the team stands on it, but I just wanted to bring up the tendency for Rust projects to eventually end up dual licensing under MIT/Apache 2.0. To potentially reduce the amount of overhead of doing it in the future, or otherwise have an issue early to reference that discusses the reason it's just MIT, I thought I would open something up.

I don't want to rehash what has been said before, so I'll just link lots of other places that have had good discussions on the topic:

As far as I know, the current process would just be getting the internal Ambient team to sign off, plus maybe a few external people that might be working on ongoing contributions.
@philpax
Copy link
Contributor

philpax commented Feb 23, 2023

Yeah, I realised this as well earlier today when I was looking through the codebases to attribute. I'm fine with it for the reasons you've mentioned (and the earlier we do it, the better it is). Leaving this one for @FredrikNoren to decide :)

@FredrikNoren
Copy link
Contributor

Hm yeah I don't see any reason not to do this; let's do it Monday unless we find some reason why we shouldn't.

@ten3roberts
Copy link
Contributor

We since have one external PR, so we will have to make sure the author agrees to the relicense

@philpax
Copy link
Contributor

philpax commented Feb 24, 2023

@daniellavoie Are you okay with your fix being relicensed?

@daniellavoie
Copy link
Contributor

I agree! Would be rude not to agree given the nature of the contribution 😅

@FredrikNoren FredrikNoren mentioned this issue Feb 27, 2023
Closed
philpax pushed a commit that referenced this issue May 23, 2023
@FredrikNoren
Update license to dual MIT and Apache2. Fixes #160
b40ab73
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@FredrikNoren FredrikNoren

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@philpax @FredrikNoren @daniellavoie @AngelOnFira @ten3roberts