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

Should we relicense Xilem and Masonry to the dual MIT/Apache License? #673

Open
PoignardAzur opened this issue Oct 16, 2024 · 1 comment

Comments

@PoignardAzur
Copy link
Contributor

There are a few reasons to do this:

  • It's our default license.
  • Some people are interested in having a maximally permissive license.
  • Because Masonry is intended to be a foundational crate for most of the ecosystem, a maximally permissive license makes sense.

Any reason not to do this?

@PoignardAzur PoignardAzur changed the title Should we relicense Masonry to the dual MIT/Apache License? Should we relicense Xilem and Masonry to the dual MIT/Apache License? Oct 16, 2024
@DJMcNab
Copy link
Member

DJMcNab commented Oct 16, 2024

Zulip discussion

The main reason to not want to is that a proportion of our code comes from Druid. That isn't in itself a problem, but it does make this task much more challenging, as we need to either determine how much of the Druid code we've kept, or also relicense Druid. I think that doing the latter is (remarkably) likely to be easier, and has greater advantage for the future. But it does make things a bit more complicated, and increases the likelihood of people being uncontactable.

See bevyengine/bevy#2373 and gfx-rs/wgpu#1473 for prior art

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

No branches or pull requests

2 participants