Strong copyleft
OpenRoots and GNU General Public License v3.0
Incompatible in both directions for derivatives. Aggregate only.
Inbound
noGPL-3.0 material entering an OpenRoots work
GPL-3.0 section 10 forbids imposing any further restriction on the rights it grants. A revenue-triggered royalty is a further restriction. Combining GPL-3.0 material into a work distributed under an OpenRoots instrument would therefore breach the GPL, and no drafting on the OpenRoots side can cure that.
Outbound
noOpenRoots material entering a GPL-3.0 project
Equally not, and for the same clause. A GPL-3.0 project cannot absorb OpenRoots material under current terms.
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.Not permissible in either direction for a combined derivative work. This is a genuine incompatibility, not a paperwork problem.
Composite distribution
Both shipped side by side, not merged.Mere aggregation on the same medium is permitted by GPL-3.0 and is the only safe pattern: separate processes, separate distribution units, no linking, no combined binary.
Patent position
Express grants and termination triggers.GPL-3.0 carries a patent grant and an anti-tivoisation provision. Neither is the source of the incompatibility; section 10 is.
The royalty
Where the Canopy obligation bites.The royalty is precisely the further restriction that section 10 prohibits. This is the clearest case in the matrix and the one to raise first with a legal team.
Current permanent terms
What holds for as long as the release exists.No automatic conversion changes the answer. Only separate relicensing can make OpenRoots material enter a GPL-3.0 project.
Other pairs