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.

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 bevy_atmosphere under dual MIT/Apache-2.0 #21

Merged
merged 1 commit into from
Aug 13, 2022
Merged

Conversation

JonahPlusPlus
Copy link
Owner

@JonahPlusPlus JonahPlusPlus commented Aug 1, 2022

When I started this, I didn't know too much about dual licensing, or its benefits. In order to keep this project in line with the Bevy project, I would like to "relicense" this project under the same licenses. I'm going to follow the same path for relicensing as Bevy (see here) and ask every contributor (as of this message and minus the bot) to give their consent by leaving the following comment:

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

Once I get consent from everyone involved, I'll merge this PR. Hopefully, it'll be done by the time I'm finished with the 0.4 release.

Contributor Check-off

@JonahPlusPlus
Copy link
Owner Author

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

3 similar comments
@kbieganski
Copy link
Collaborator

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

@Aceeri
Copy link
Contributor

Aceeri commented Aug 1, 2022

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

@Shatur
Copy link
Collaborator

Shatur commented Aug 1, 2022

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

@JonahPlusPlus
Copy link
Owner Author

@cryscan I would really like to get your input on this. While your changes have been overwritten in this last update, I would still like to get your consent if possible, just to make sure everyone is on the same page and that there won't be any future issues surrounding this.

@cryscan
Copy link
Contributor

cryscan commented Aug 13, 2022

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

@JonahPlusPlus
Copy link
Owner Author

Thank you everyone for your contributions. I'll be having this update out in a couple days, just need to rewrite documentation. The current main branch is now up to date, so if you would like to test it out, any feedback is appreciated.

@JonahPlusPlus JonahPlusPlus reopened this Aug 13, 2022
@JonahPlusPlus JonahPlusPlus merged commit 7aa542c into master Aug 13, 2022
@JonahPlusPlus JonahPlusPlus deleted the license branch August 30, 2022 03:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants