Relicense Druid under dual MIT/Apache-2.0
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 9.7k
- Forks
- 565
- PR merge metrics
- No merged PRs in 30d
Description
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
- @cmyr
- @raphlinus
- @futurepaul
- @xStrom
- @maan2003
- @jneem
- @richard-uk1
-
@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 -
@zwlxt
We also need:
7k5x- https://github.com/linebender/druid/commit/fdc7562483188210971e13d71b1d400885ad9af6 / https://github.com/linebender/druid/pull/1949Bruno Dupuis- https://github.com/linebender/druid/commit/f35bec8056d81da597d26a72c4b631690c74e7b7
If you are aware of any contributors not listed in this checklist, please let us know.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the relicense details and contributor checklist first, including the linked commit and pull request #1949. Confirm whether the relevant contribution is listed and follow the issue's stated response process; done means the required contributor agreements are recorded and the relicensing work can proceed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 15/100