Source available
OpenRoots and Commons Clause condition
The closest conceptual match for the no-resale angle. Treat as compatible only with clear component boundaries.
Inbound
conditionalCommons-Clause material entering an OpenRoots work
Commons Clause permits many uses but removes the right to sell the covered software itself. Commons-Clause material can enter an OpenRoots work only if the combined distribution does not grant commercialization rights the upstream Commons Clause withheld.
Outbound
conditionalOpenRoots material entering a Commons-Clause project
The two models are philosophically close but not identical. OpenRoots allows larger independent products and restricts competing commercialization of the Work itself; Commons Clause turns on whether the value derives substantially from the covered software.
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.Possible only with careful separation of what is OpenRoots and what is Commons-Clause covered. Do not collapse the two into a single grant unless the same licensor controls both sides.
Composite distribution
Both shipped side by side, not merged.Aggregation is workable when each component keeps its own notice, upstream URL, copyright notice, and licence text.
Patent position
Express grants and termination triggers.Patent terms come from the underlying licence to which Commons Clause is attached. OpenRoots patent peace governs only the OpenRoots portion.
The royalty
Where the Canopy obligation bites.Commons Clause forbids selling the covered software itself; OpenRoots prices Canopy use and separately blocks competing commercialization. These are compatible only where the commercialized value is a larger independent product.
Current permanent terms
What holds for as long as the release exists.No automatic conversion occurs. Each component keeps its own source-available commercial restriction.
Other pairs