[Resubmitting this comment I made against a previous flagged article] At first glance it Blue Oak seems like a decent license, and the points the author makes

[Resubmitting this comment I made against a previous flagged article] At first glance it Blue Oak seems like a decent license, and the points the author makes about MIT [0] seem valid. My major issue with adopting a new license however is how well known it probably isn't, so there is not yet a clear legal consensus on it. In all software companies I've worked in there is a clear list of licenses that have been pre-approved and I can just log the inclusion of any open source using those licenses and everything is fine. However, if I want to use anything not already on the list it requires a manual approval process from the legal department, which is usually time consuming, and often just results in a 'no' because they are too risk averse to asses the licenses properly themselves, but are happy relying on the consensus that licenses like MIT and BSD are OK for commercial use. Also, while a lot of the authors crtisisms of MIT seem valid points about uncertainty I think there is a lot to be said for the long length of time it has stood and the general consensus on it's intentions. If I see an MIT license, I can basically know I can do whatever I want with it, provided I give attribution, and there is no warrenty. I'm not going to worry about being sued over someone's interpretation of "deal in the software" because AFAIK, that has never happened in the 40+ years the license has been in use. I think I'd actually feel more at risk using Blue Oak just because of the lack of commentary and consensus on it's terms. The only really substantial point he makes is about variants under the same name, but the lesson here is to just do a diff on licenses to check it's in the standard form. And anyway, doesn't the same problem apply to Blue Oak and in fact all licenses, if you don't do a diff on the license text someone could easily produce and use a variant without you noticing. [0] - https://writing.kemitchell.com/2016/09/21/MIT-License-Line-by-Line.html https://writing.kemitchell.com/2016/09/21/MIT-License-Line-b...