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

Add license #87

Closed
ZeroEkkusu opened this issue Mar 6, 2022 · 3 comments
Closed

Add license #87

ZeroEkkusu opened this issue Mar 6, 2022 · 3 comments
Assignees
@onbjerg
Labels
T-meta Type: updates to the repo

Comments

@ZeroEkkusu
Copy link
Contributor

Which one?
@onbjerg onbjerg added the T-meta Type: updates to the repo label Mar 7, 2022
@onbjerg onbjerg self-assigned this Mar 7, 2022
@onbjerg onbjerg moved this to Todo in Foundry Book Mar 7, 2022
@onbjerg onbjerg closed this as completed in 56faf51 Mar 7, 2022
Repository owner moved this from Todo to Done in Foundry Book Mar 7, 2022
@ZeroEkkusu
Copy link
Contributor Author

ZeroEkkusu commented Mar 7, 2022 •
edited
Loading

Which license is the repo licensed under? (What does APACHE apply to and what MIT)

@onbjerg
Copy link
Collaborator

onbjerg commented Mar 7, 2022

Apache/MIT dual license is super common in the Rust ecosystem - AFAIK it gives end-users the option to choose. Personally, I hate licensing talks since I don't really speak legalese, so I just opt for the same licenses most of the time. Some rationale can be found here: sfackler/rust-postgres-macros#19 and here: https://github.com/dtolnay/rust-faq#why-a-dual-mitasl2-license

@ZeroEkkusu
Copy link
Contributor Author

ZeroEkkusu commented Mar 7, 2022 •
edited
Loading

Thanks! I always want to learn more about legal aspects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@onbjerg onbjerg

Labels
T-meta Type: updates to the repo
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@onbjerg @ZeroEkkusu