DJMcNab commented 3 weeks 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

[x] @cmyr
[x] @raphlinus
[x] @futurepaul
[x] @xStrom
[x] @maan2003
[x] @jneem
[ ] @richard-uk1
[x] @8176135
[ ] @agentsim
[x] @AlexKnauth
[x] @amtep
[x] @andlr
[x] @andrewhickman
[x] @arifd
[x] @arthmis
[ ] @astrale-sharp
[x] @AtomicGamer9523
[x] @Azorlogh
[ ] @barsae
[x] @becky112358
[x] @benoitryder
[x] @bheisler
[x] @binomial0
[x] @bjorn
[x] @cbondurant
[x] @cbrewster
[x] @ccqpein
[x] @chris-zen
[x] @Ciantic
[x] @colinfruit
[x] @covercash2
[x] @crsaracco
[x] @crumblingstatue
[x] @CryZe
[x] @Cupnfish
[ ] @dakata1337
[x] @danieldulaney
[ ] @Denaun
[x] @dfrg
[x] @dhardy
[x] @djeedai
[x] @dkess
[x] @Dmitry-Borodin
[x] @DrGabble
[x] @dristic
[x] @dsp
[x] @Duddino
[ ] @edwin0cheng
[ ] @edwin0minv
[x] @elrnv
[x] @emigr2k1
[ ] @felixrabe
[x] @Fenex
[x] @fishrockz
[x] @ForLoveOfCats
[ ] @gergohuszar
[x] @giannissc
[ ] @Giesch
[x] @gmorenz
[x] @GoldsteinE
[ ] @hammsvietro
[x] @hampuslidin
[x] @HoNile
[x] @hwchen
[x] @i509VCB
[x] @ineol
[x] @Insprill
[x] @JAicewizard
[x] @james-lawrence
[x] @jaredoconnell
[x] @JarrettBillingsley
[ ] @Jerboas86
[x] @jjl
[ ] @jplatte
[ ] @jpochyla
[ ] @jrmuizel
[x] @jTerracina
[ ] @justinmoon
[ ] @Kartoffelsaft
[x] @kbalt
[x] @Kethku
[x] @kianmeng
[ ] @kindlychung
[x] @kingosticks
[x] @klemensn
[x] @knpwrs
[x] @konkers
[x] @koutoftimer
[x] @kud1ing
[ ] @lassipulkkinen
[ ] @LastLightSith
[ ] @Lejero
[x] @LiHRaM
[x] @liias
[ ] @lisael
[ ] @longmathemagician
[x] @lord
[x] @luleyleo
[ ] @lzhoucs
[x] @Majora320
[x] @malmz
[x] @mastfissh
[ ] @mathiaspeters
[x] @matthewgapp
[x] @maurerdietmar
[x] @MaximilianKoestler
[x] @melody-notpond
[x] @mendelt
[x] @MGlolenstine
[ ] @minimal-state
[ ] @mlrv
[x] @mobile-bungalow
[x] @ModProg
[ ] @mralve
[ ] @mrandri19
[x] @msiglreith
[x] @mwcampbell
[x] @newcomb-luke
[ ] @ngugcx
[x] @NickLarsenNZ
[ ] @nilsmartel
[ ] @nunotexbsd
[x] @nvll
[x] @ofek
[x] @panekj
[x] @Pavel-N
[ ] @peaceiris
[ ] @peamaeq
[ ] @perlindgren
[x] @Perlmint
[x] @PoignardAzur
[x] @PolyMeilex
[x] @psychon
[x] @Psykopear
[x] @pyroxymat
[x] @r-ml
[x] @Ralith
[x] @ratmice
[x] @raymanfx
[x] @redcathode
[ ] @rhzk
[ ] @RichardPoole42
[x] @rjwittams
[x] @rofrol
[x] @rosefromthedead
[x] @rschulman
[x] @rylev
[x] @s3thi
[x] @sapphire-arches
[x] @Schaback
[ ] @scholtzan
[x] @SecondFlight
[x] @SergejJurecko
[x] @sigaloid
[x] @sjoshid
[x] @smmalis37
[x] @sprocklem
[x] @Stanislav-Lapata
[x] @Steve-xmh
[x] @superfell
[x] @Swatinem
[x] @sysint64
[x] @tay64
[x] @tbillington
[x] @teddemunnik
[x] @terhechte
[x] @thecodewarrior
[ ] @theduke
[x] @ThomasMcandrew
[ ] @timakro
[x] @tirix
[ ] @tomaszmduda
[x] @totsteps
[x] @twitchyliquid64
[x] @ul
[x] @vbsteven
[x] @viktorstrate
[ ] @vishalsodani
[x] @vkahl
[x] @wandercn
[ ] @winksaville
[ ] @xarvic
[x] @xkns
[x] @yrns
[x] @Zarenor
[x] @zaynetro
[x] @zedseven
[ ] @zhiburt
[x] @zwlxt

We also need:

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

ratmice commented 3 weeks ago

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

xStrom commented 3 weeks ago

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

DJMcNab commented 3 weeks ago

You are getting this message because you previously contributed to Druid - a GUI toolkit in Rust. We are going through a relicensing process. We kindly ask you to please read this issue, and respond as directed in the initial comment. Thank you!

@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

DJMcNab commented 3 weeks ago

You are getting this message because you previously contributed to Druid - a GUI toolkit in Rust. We are going through a relicensing process. We kindly ask you to please read this issue, and respond as directed in the initial comment. Thank you!

@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

DJMcNab commented 3 weeks ago

You are getting this message because you previously contributed to Druid - a GUI toolkit in Rust. We are going through a relicensing process. We kindly ask you to please read this issue, and respond as directed in the initial comment. Thank you!

@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

DJMcNab commented 3 weeks ago

You are getting this message because you previously contributed to Druid - a GUI toolkit in Rust. We are going through a relicensing process. We kindly ask you to please read this issue, and respond as directed in the initial comment. Thank you!

@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

DJMcNab commented 3 weeks ago

You are getting this message because you previously contributed to Druid - a GUI toolkit in Rust. We are going through a relicensing process. We kindly ask you to please read this issue, and respond as directed in the initial comment. Thank you!

@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
@zwlxt

Azorlogh commented 3 weeks ago

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

Insprill commented 3 weeks ago

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

cbondurant commented 3 weeks ago

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.

thecodewarrior commented 3 weeks ago

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

andlr commented 3 weeks ago

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

jaredoconnell commented 3 weeks ago

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

Steve-xmh commented 3 weeks ago

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

ThomasMcandrew commented 3 weeks ago

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

sigaloid commented 3 weeks ago

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

i509VCB commented 3 weeks ago

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 💀

zedseven commented 3 weeks ago

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

Psykopear commented 3 weeks ago

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

SergejJurecko commented 3 weeks ago

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

kbalt commented 3 weeks ago

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

GoldsteinE commented 3 weeks ago

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.

binomial0 commented 3 weeks ago

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

xkns commented 3 weeks ago

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

cbrewster commented 3 weeks ago

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

konkers commented 3 weeks ago

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

yrns commented 3 weeks ago

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

NickLarsenNZ commented 3 weeks ago

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

hwchen commented 3 weeks ago

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

mwcampbell commented 3 weeks ago

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

Pavel-N commented 3 weeks ago

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

crumblingstatue commented 3 weeks ago

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

AtomicGamer9523 commented 3 weeks ago

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.

Don't worry, this definitely did :)

JarrettBillingsley commented 3 weeks ago

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

maan2003 commented 3 weeks ago

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

rylev commented 3 weeks ago

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

kud1ing commented 3 weeks ago

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

klemensn commented 3 weeks ago

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

CryZe commented 3 weeks ago

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

kingosticks commented 3 weeks ago

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

futurepaul commented 3 weeks ago

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

andrewhickman commented 3 weeks ago

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

emigr2k1 commented 3 weeks ago

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

On Fri, Nov 1, 2024, 11:20 AM Nick Steel @.***> wrote:

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

— Reply to this email directly, view it on GitHub https://github.com/linebender/druid/issues/2414#issuecomment-2452269620, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJTLZLXLH3IZIFXEWJ7ZAD3Z6OZ5LAVCNFSM6AAAAABRARYSR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSGI3DSNRSGA . You are receiving this because you were mentioned.Message ID: @.***>

dfrg commented 3 weeks ago

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

DrGabble commented 3 weeks ago

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

twitchyliquid64 commented 3 weeks ago

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

ofek commented 3 weeks ago

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

MGlolenstine commented 3 weeks ago

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

SecondFlight commented 3 weeks ago

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

Schaback commented 3 weeks ago

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

linebender / druid

Relicense Druid under dual MIT/Apache-2.0 #2414

What

Other Linebender Projects

Future of Druid

Contributor checklist