Permissive
OpenRoots and Apache License 2.0
Apache-2.0 in freely; OpenRoots out only through separate relicensing or clean aggregation.
Inbound
yesApache-2.0 material entering an OpenRoots work
Apache-2.0 requires notice preservation, a statement of changes, and carries an express patent grant with a termination trigger. All three survive intact inside an OpenRoots work; none of them constrains the outer licence.
Outbound
conditionalOpenRoots material entering a Apache-2.0 project
Not by default. Apache-2.0 cannot absorb OpenRoots restrictions. It works only where the OpenRoots licensor separately releases the material under Apache-2.0 or another compatible grant.
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.The combined work is under the OpenRoots instrument and must preserve Apache-2.0 notices and the changes statement for Apache-covered portions.
Composite distribution
Both shipped side by side, not merged.Clean inbound and as aggregation. Apache notice mechanics compose cleanly with an outer instrument.
Patent position
Express grants and termination triggers.Apache-2.0 section 3 grants patent rights and terminates them on patent litigation against the project. The OpenRoots instruments adopt the same defensive-termination shape, so the two do not conflict.
The royalty
Where the Canopy obligation bites.Apache-2.0 forbids charging for the licence grant itself but permits charging a fee for the work. The Canopy royalty is a term of the OpenRoots grant, not a charge levied on the Apache-2.0 grant, so the two coexist. Confirm this against a specific deployment with counsel.
Current permanent terms
What holds for as long as the release exists.No convergence occurs by time alone. Apache remains Apache; OpenRoots remains OpenRoots.
Other pairs