Relicense Druid under dual MIT/Apache-2.0 #2414
Comments
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
1 similar comment
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
xStrom
added
help wanted
|
You are getting this message because you previously contributed to Druid - a GUI toolkit in Rust.
|
|
You are getting this message because you previously contributed to Druid - a GUI toolkit in Rust.
|
|
You are getting this message because you previously contributed to Druid - a GUI toolkit in Rust.
|
|
You are getting this message because you previously contributed to Druid - a GUI toolkit in Rust.
|
|
You are getting this message because you previously contributed to Druid - a GUI toolkit in Rust.
|
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
1 similar comment
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. Also I just feel like saying it's a shame github doesn't have some better mechanism for this. Fingers crossed this does not cause some form of email storm. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
5 similar comments
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. Also yeah the email storm 💀 |
|
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
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I’m not sure why relicense a dead project, but sure, I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
5 similar comments
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. PS. Good luck with Xilem, I hope using winit solves many of the platform backend issues. They were a pain, and held the progress back in my opinion. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
10 similar comments
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
2 similar comments
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0
license, allowing licensees to choose either at their option.Message ID:
***@***.***>
… |
|
I license past and future contributions under the dual MIT/Apache-2.0
license, allowing licensees to choose either at their option.
…On Wed, Nov 6, 2024 at 5:23 AM jjl ***@***.***> wrote:
I license past and future contributions under the dual MIT/Apache-2.0<br>
license, allowing licensees to choose either at their option.Message
ID:<br> ***@***.***><br> <br> ><br>
—
Reply to this email directly, view it on GitHub
<#2414 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB3FPYGBTLAQFKCZBAJAYLZ7IJ5DAVCNFSM6AAAAABRARYSR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJZG42DENJXGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
9 similar comments
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
|
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
and others
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:
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
@8176135@agentsim@AlexKnauth@amtep@andlr@andrewhickman@arifd@arthmis@astrale-sharp@AtomicGamer9523@Azorlogh@barsae@becky112358@benoitryder@bheisler@binomial0@bjorn@cbondurant@cbrewster@ccqpein@chris-zen@Ciantic@colinfruit@covercash2@crsaracco@crumblingstatue@CryZe@Cupnfish@dakata1337@danieldulaney@Denaun@dfrg@dhardy@djeedai@dkess@Dmitry-Borodin@DrGabble@dristic@dsp@Duddino@edwin0cheng@edwin0minv@elrnv@emigr2k1@felixrabe@Fenex@fishrockz@ForLoveOfCats@gergohuszar@giannissc@Giesch@gmorenz@GoldsteinE@hammsvietro@hampuslidin@HoNile@hwchen@i509VCB@ineol@Insprill@JAicewizard@james-lawrence@jaredoconnell@JarrettBillingsley@Jerboas86@jjl@jplatte@jpochyla@jrmuizel@jTerracina@justinmoon@Kartoffelsaft@kbalt@Kethku@kianmeng@kindlychung@kingosticks@klemensn@knpwrs@konkers@koutoftimer@kud1ing@lassipulkkinen@LastLightSith@Lejero@LiHRaM@liias@lisael@longmathemagician@lord@luleyleo@lzhoucs@Majora320@malmz@mastfissh@mathiaspeters@matthewgapp@maurerdietmar@MaximilianKoestler@melody-notpond@mendelt@MGlolenstine@minimal-state@mlrv@mobile-bungalow@ModProg@mralve@mrandri19@msiglreith@mwcampbell@newcomb-luke@ngugcx@NickLarsenNZ@nilsmartel@nunotexbsd@nvll@ofek@panekj@Pavel-N@peaceiris@peamaeq@perlindgren@Perlmint@PoignardAzur@PolyMeilex@psychon@Psykopear@pyroxymat@r-ml@Ralith@ratmice@raymanfx@redcathode@rhzk@RichardPoole42@rjwittams@rofrol@rosefromthedead@rschulman@rylev@s3thi@sapphire-arches@Schaback@scholtzan@SecondFlight@SergejJurecko@sigaloid@sjoshid@smmalis37@sprocklem@Stanislav-Lapata@Steve-xmh@superfell@Swatinem@sysint64@tay64@tbillington@teddemunnik@terhechte@thecodewarrior@theduke@ThomasMcandrew@timakro@tirix@tomaszmduda@totsteps@twitchyliquid64@ul@vbsteven@viktorstrate@vishalsodani@vkahl@wandercn@winksaville@xarvic@xkns@yrns@Zarenor@zaynetro@zedseven@zhiburt@zwlxtWe also need:
7k5x- fdc7562 / Add psst in more_information.md #1949Bruno Dupuis- f35bec8If you are aware of any contributors not listed in this checklist, please let us know.
The text was updated successfully, but these errors were encountered: