-
Notifications
You must be signed in to change notification settings - Fork 10
Conversation
It's already in the Readme. This is bikeshedding. |
It isn't. I've checked this with lawyers multiple times. Unfortunately today we still have to include the full license text. — On Fri, Apr 17, 2015 at 9:57 AM, Barry Allard [email protected]
|
Orrick says it's fine. It's Big4 clipboard auditors that insist on business theater being "safe" because their checkboxes them so. If it makes the auditors feel better, I'll drop a link in. — On Fri, Apr 17, 2015 at 10:50 AM, Juan Batiz-Benet
|
Funny, it's Orrick that told me it's needed :) — On Fri, Apr 17, 2015 at 10:54 AM, Barry Allard [email protected]
|
LOL!!! I'll run it by two other IP lawyer friends. — On Fri, Apr 17, 2015 at 10:56 AM, Juan Batiz-Benet
|
(The dangers of everyone using the same legal shop in the valley.) — On Fri, Apr 17, 2015 at 10:56 AM, Juan Batiz-Benet
|
I'll have to bash some heads and get a free lunch out of it. Just chatted with a gal that specializes in licensing and confirmed with a second source. (I also knew the guy that wrote the Orielly book on it, but sadly he passed away.) The answer is related to the interpretation of "clear intent." It could be argued that a couple words in the Readme isn't obvious enough, so just enough overkill to do this once would be boilerplate in the .go's and an MIT-LICENSE file. (I'll forward this back and see what they say.). I'll do this when I get in front of terminal for being a grouchy, lazy slob. Case study won't hear about in any bschool because it contains privileged info: A gigadollar tort suit related to a petrochem co everyone knows hinged on an expert witness intepretation of safety codes meaning of a comma ("and" or "or"). It was "or," the plantiffs wanted "and." — On Fri, Apr 17, 2015 at 10:58 AM, Barry Allard [email protected]
|
Fixed as of c88edec |
thanks @steakknife! |
and-- that's sadly hilarious. 😢 😑 |
TGIF 🍻 🍷 ☕ |
The pkg should bear an actual
LICENSE
, else vendoring is a bit sketch.