It also would allow for unsavory gamesmanship due to the "license available" trigger. Wait for widespread adoption, then release a commercial license. Suddenly

It also would allow for unsavory gamesmanship due to the "license available" trigger. Wait for widespread adoption, then release a commercial license. Suddenly you have a lot of scrambling to either replace the product or buy a license. Alternatively, license cost could be inflated greatly after adoption. I just see the terms as creating too many unknowns about the future. Maybe I missed it, but do you have to constantly monitor all your dependencies for whether they may have just released a commercial license? The effects of the license shouldn't vary depending on some outside input (the existence or not of a commercial license). And the 90-day "trial" period seems both too long and too short at the same time. It's long enough to make tracking a little more difficult and too short to even make it into production from testing for many uses. (I assume the 90-days starts as soon as an org begins testing the product, not necessarily starting upon shipping.)