Permissive
OpenRoots and MIT License
Take MIT in freely. Do not push OpenRoots material out into an MIT project unless separately relicensed.
Inbound
yesMIT material entering an OpenRoots work
MIT imposes only that its notice travels with the work. Nothing in it restricts the terms of the surrounding work, so MIT material enters an OpenRoots work freely, provided the MIT notice is preserved in the NOTICE file alongside the OpenRoots notice.
Outbound
noOpenRoots material entering a MIT project
An MIT-licensed project cannot absorb OpenRoots material and remain MIT, because MIT grants recipients the right to sublicense and to use without royalty, and the Canopy tier can require a royalty. Relabelling OpenRoots material as MIT would be a grant the licensor never made.
Mechanism
Where the pairing holds and where it breaks.
A matrix cell tells you the answer. These are the clauses that produce it.
Derivative works
One combined, distributable artifact.A combined work carries the OpenRoots instrument. The MIT-derived portions remain separately available under MIT from their original source, which nothing here can withdraw.
Composite distribution
Both shipped side by side, not merged.Shipping both side by side is straightforward. Each file carries its own header, the NOTICE file lists both, and no merge occurs.
Patent position
Express grants and termination triggers.MIT grants no express patent licence. OpenRoots carries its own patent grant and patent-peace clause for the OpenRoots portion only.
The royalty
Where the Canopy obligation bites.The royalty attaches to the OpenRoots portion only, and is computed on revenue attributable to it. MIT material inside the work does not enlarge the base.
Current permanent terms
What holds for as long as the release exists.No automatic conversion occurs. The OpenRoots portion remains under OpenRoots terms unless the licensor separately relicenses it.
Other pairs