News for hackers. Stuff that matters.
Re:PolyForm Noncompete Licenses by ghaff on Friday May 15, 2020 @01:30PM (#23194835)
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.

Re:PolyForm Noncompete Licenses by verdverm on Friday May 15, 2020 @05:05PM (#23197391)
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.
Re:PolyForm Noncompete Licenses by verdverm on Friday May 15, 2020 @05:36PM (#23197764)
https://opensource.stackexchange.com/questions/8367/is-the-t...

This is one of the top results when searching