linebender / druid

A data-first Rust-native UI design toolkit.
https://linebender.org/druid/
Apache License 2.0
9.55k stars 569 forks source link

Relicense Druid under dual MIT/Apache-2.0 #2414

Open DJMcNab opened 2 hours ago

DJMcNab commented 2 hours ago

What

We are planning on relicensing Druid under the MIT/Apache 2.0 dual license. This matches the standard licenses used by Linebender, and it gives maximum compatibility with the rest of the Rust ecosystem. For context, Druid is currently solely licensed under the Apache 2.0 license.

If you are mentioned in this issue, we need your help to make this happen

To agree to this relicense, please read the details in this issue, then leave a comment with the following message:

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

For clarity, this is the MIT expat license, with SPDX license identifier of MIT.

This also follows a similar move done by Bevy. See their issue for additional motivation and discussion of the dual license.

Other Linebender Projects

Other Linebender projects, such as Glazier, Masonry and Xilem are currently also under only the Apache 2.0 license, due to their use of Druid code. Once this relicensing process is complete, we will also relicense those projects to the same MIT/Apache 2.0 license.

Future of Druid

The Druid project itself is being discontinued. The relicensing is still very useful. It will allow us to do one final release under the new licensing terms.

Druid contains a lot of great work done by hundreds of contributors over many years. Now is the time to make sure that work has the best chance of living on in other projects. The dual MIT/Apache 2.0 licensing will help achieve that goal.

Many of the core developers of Druid are now working on the Xilem stack, including Masonry, which uses Druid code as its basis. We see Xilem as the future of Druid.

Contributor checklist

We also need:

If you are aware of any contributors not listed in this checklist, please let us know.

ratmice commented 1 hour ago

I'm not certain that the mentions worked, I noticed because of the "subscribed to the thread", rather than "because you were mentioned", and the @ links don't link to the user as I would expect, perhaps they don't work in check lists?

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

xStrom commented 1 hour ago

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