- Borrowing bits of code from Sentry for use in an unrelated, non-competing commercial product will no longer be possible for many people -- I suspect many companies' legal teams will bar use of BSL-licensed code out of caution, at least until the 3-year conversion point.
- Using bits of Sentry for internal, non-distributed projects may not be allowed if there's any chance the project will convert to a commercial product (competing or not) within 3 years.
- I suspect there are other scenarios that are technically and legally possible (at least by Sentry's interpretation) but that many corporate lawyers will nix based on an abundance of caution.
- And of course, starting a new open-source project with open governance based on current Sentry code will no longer be an option.
The thing is, BSL's permissions may seem clear to developers, but lawyers will likely get hung up on how to define "competing", and whether a judge would allow a suit to proceed against a (intuitively speaking) clearly non-competing product based on real or perceived ambiguity in the license or in the case itself. Too often, legal teams "just say no" to anything that falls outside their clearly defined (and legally tested) comfort zones. I don't blame corporate lawyers entirely for that, though - it's really a consequence of the legal climate arising from prior case law (which I believe often proceeded on dubious grounds).