First, the revenue is a fixed number, this is usually a bad idea in contracts that will last a long time. There should be some adjustable indexing going on.

Second, the revenue number is in USD, this is probably less of an issue, but still creates ambiguity. What if revenue is reported in a different currency? Do we use an exchange rate? Which one? At what point in time do we choose the exchange rate? At the time revenue is reported? At the time the license comes into effect? Unclear.

Third, there are probably ways of skirting thresholds by artificially manipulating your corporate structure through subsidiaries etc., changing both revenue and headcount. How would that be solved?

Fourth, how is labor measured? By average salary? By specific salary? What counts as labor on the project? Who approves the labor? This also adds management and accounting overhead to the open source project, which isn't great.

I applaud the efforts, but I see some challenges in using the license. I hope these issues can be answered!

Assuming 5%, Google can us only up to 20 CSL protects, assuming they have 100% profit.

> “Attributable Revenue” means revenue directly or indirectly generated through the use of the Software, including but not limited to product sales, SaaS fees, subscriptions, licensing, consulting, advertising, automation value, or labor displacement.

It's hard to know what is not included. Layers and accountant will run away.

Let's suppose I sell icecream and cakes[1], and use a program to manage the icecream stock, do I have to include the croissant revenue? What if I sell sometimes a piece of cake with a ball of icecream on top?

[1] It's common here. In summer they sell icecram and in winter cake+coffe, but you actually can order any of them all year long.