Re:PolyForm Noncompete Licenses
by kemitchell on Friday May 15, 2020 @01:49PM
(#23195062)
Thanks for the typo fix, which someone also e-mailed to me, as well. The virus has me working from the couch, and despite jacking my font sizes up and wearing my driving glasses, I am making far more typos than usual.
Publication of standardized legal building blocks is a big passion of mine. I think it's essential, both for the good of law clients and for the mental health of their lawyers, that we do a lot more of it. Besides PolyForm, see also:
The OSS license body is rejecting these non-compete licenses as open source.
To be somewhat pedantic, the Open Source Initiative maintains the open source definition and has a license review process which can lead to a license becoming an OSI-approved license. There are a variety of reasons licenses don't get approved but one of them is that it doesn't meet the open source definition.
I'm not sure any of these "non-compete" licenses have been rejected by the OSI. I'm pretty sure at least some of them haven't been submitted because they almost certainly would fail to be approved.
But to be clear, anyone can claim their license is an "open source license" just not that it's an OSI-approved license if it's not.
I suppose what I am getting at is that, like with many things, humams tend to gravitate towards adopting definitions around the governing body (experts) certification. We can get into problems, like certified organic, when there are too many bodies creating standards. There was actually an analogous conversation in Cuelang about this, w.r.t. user registered builtins, Cue code which can no longer be used with cue, and the worry of fracturing the ecosystem.
https://opensource.stackexchange.com/questions/8367/is-the-t...
This is one of the top results when searching
I appreciate attempts to standardize the law, and make it more accessible and cost-effective to rely on.
Hmmm, guess there are issues though