<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr">You might want to check out Iain Mitchell’s chapter in this book</div><div dir="ltr"><br></div><div dir="ltr"><a href="https://global.oup.com/academic/product/free-and-open-source-software-9780199680498?cc=us&lang=en&">https://global.oup.com/academic/product/free-and-open-source-software-9780199680498?cc=us&lang=en&</a></div><div dir="ltr"><br></div><div dir="ltr">There’s a second edition currently in the works but it won’t be out til the summer</div><div dir="ltr"><br><blockquote type="cite">On Feb 27, 2020, at 6:28 PM, Michael Downey <michael@downey.net> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>And now for something completely different...</span><br><span></span><br><span>While it's not nearly as common as it was for a while, now and then we get some government and inter-governmental clients who want to roll their own license because they think they are a special case of indemnity or privilege requirements, things along those lines. But typically when we hear those remarks, it's not coming from legal folks with FLOSS experience but instead just default thinking that the most protective stance is to create something bespoke.</span><br><span></span><br><span>Can anyone on the list recommend any good reading materials, essays, talks, or presentations on why we should discourage bespoke licenses, especially for governments and similar agencies?</span><br><span></span><br><span>Thanks in advance for any memories or bookmarks folks can dust off --</span><br><span></span><br><span>Michael Downey</span><br><span>United Nations Foundation</span><br><span></span><br><span>_______________________________________________</span><br><span>License-discuss mailing list</span><br><span>License-discuss@lists.opensource.org</span><br><span>http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</span><br></div></blockquote></body></html>