<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="https://writing.kemitchell.com/atom.xml" rel="self" type="application/atom+xml" /><link href="https://writing.kemitchell.com/" rel="alternate" type="text/html" /><updated>2026-11-11T19:28:33-08:00</updated><id>https://writing.kemitchell.com/atom.xml</id><title type="html">/dev/lawyer</title><subtitle>law, technology, and the space between</subtitle><author><name>Kyle E. Mitchell</name></author><entry><title type="html">Freemium the Registry</title><link href="https://writing.kemitchell.com/2026/09/16/Freemium-the-Registry" rel="alternate" type="text/html" title="Freemium the Registry" /><published>2026-09-16T21:21:50-07:00</published><updated>2026-09-16T21:21:50-07:00</updated><id>https://writing.kemitchell.com/2026/09/16/Freemium-the-Registry</id><content type="html" xml:base="https://writing.kemitchell.com/2026/09/16/Freemium-the-Registry"><![CDATA[<p>I can heartily recommend that anyone following this blog for things open source, especially around funding or “sustainability”, read Laurie Voss’ <a href="https://seldo.com/posts/nobody-pays-for-open-source-we-can-force-them-to">“Nobody pays for open source. We can force them to.”</a>.</p>

<p>It’s fair to say I’m biased, a bit of a seldo fan.  I was his “battle lawyer” for npm, which he co-founded and I represented for several years.  I admire his frank assessment of some of that experience in-post, but there’s lots more there to think about, besides.</p>]]></content><author><name>Kyle E. Mitchell</name></author><category term="Open Source" /><category term="npm" /><category term="Funding" /><category term="Sustainability" /><category term="Business" /><summary type="html"><![CDATA[Laurie Voss on an open source funding model]]></summary></entry><entry><title type="html">PolyForm Noncommercial 2.0.0-pre.3</title><link href="https://writing.kemitchell.com/2026/09/12/PolyForm-Licenses-2.0.0-pre.3" rel="alternate" type="text/html" title="PolyForm Noncommercial 2.0.0-pre.3" /><published>2026-09-12T00:00:00-07:00</published><updated>2026-09-12T00:00:00-07:00</updated><id>https://writing.kemitchell.com/2026/09/12/PolyForm-Licenses-2.0.0-pre.3</id><content type="html" xml:base="https://writing.kemitchell.com/2026/09/12/PolyForm-Licenses-2.0.0-pre.3"><![CDATA[<p>I’ve published third preview versions of PolyForm licenses to <a href="https://gist.github.com/kemitchell/e01f19ff2b42dbd17fafe0f284164ca0">a GitHub gist</a>.  Feedback of all kinds is welcome.</p>

<p>Please do <em>not</em> adopt these prereleases for published software.  I feel we’re getting closer to a proper 2.0.0 release, but these prereleases have <em>not</em> yet gone through PolyForm’s full vetting process.</p>]]></content><author><name>Kyle E. Mitchell</name></author><category term="Software Licensing" /><category term="Software" /><category term="Noncommercial" /><category term="Source Available" /><summary type="html"><![CDATA[steps toward 2.0.0]]></summary></entry><entry><title type="html">Common Form Toolbox</title><link href="https://writing.kemitchell.com/2026/09/04/Common-Form-Toolbox" rel="alternate" type="text/html" title="Common Form Toolbox" /><published>2026-09-04T21:21:47-07:00</published><updated>2026-09-04T21:21:47-07:00</updated><id>https://writing.kemitchell.com/2026/09/04/Common-Form-Toolbox</id><content type="html" xml:base="https://writing.kemitchell.com/2026/09/04/Common-Form-Toolbox"><![CDATA[<p>I’ve just launched <a href="https://toolbox.commonform.org">toolbox.commonform.org</a>, a quick, convenient way to use various Common Form contract text analysis and modification tools on snippets of legal text.  Now anyone online can quickly find technical errors, style deficiencies, and comprehensive lists of headings, references, definitions, and term uses without installing any Common Form software.  There’s also a facility for renaming sections and terms.</p>

<p>The site never sends any text you provide to any server.  Everything happens on your own computer.</p>]]></content><author><name>Kyle E. Mitchell</name></author><category term="Common Form" /><summary type="html"><![CDATA[quick utilities for editing contract text]]></summary></entry><entry><title type="html">Sans-Serif Fonts for Contracts</title><link href="https://writing.kemitchell.com/2026/08/30/Sans-Serifs-Fonts-for-Contracts" rel="alternate" type="text/html" title="Sans-Serif Fonts for Contracts" /><published>2026-08-30T12:00:22-07:00</published><updated>2026-08-30T12:00:22-07:00</updated><id>https://writing.kemitchell.com/2026/08/30/Sans-Serifs-Fonts-for-Contracts</id><content type="html" xml:base="https://writing.kemitchell.com/2026/08/30/Sans-Serifs-Fonts-for-Contracts"><![CDATA[<p>A good sans-serif font for contract proposals in Microsoft Word should:</p>
<ul>
  <li>read easily</li>
  <li>include all the characters commonly used in contracts, including legal symbols like ‘§’ and ‘¶’</li>
  <li>work on Windows, Mac, iOS, and Android devices with Microsoft Word, no installation or file-embedding required</li>
  <li>be attainable for Libre Office and other office suite users, perhaps with installation required</li>
  <li>not attract attention to typography</li>
</ul>

<p>The first obvious answer is Arial, the universally available but typographer-maligned clone of Helvetica.  Helvetica itself is available on Macs as standard, but not on PCs.  If you send out Word proposals in Helvetica from your Mac, expect stray formatting changes back in redlines.</p>

<p>The second obvious choice is one of the succession of sans-serif default fonts that Microsoft has shipped with office over the years: Calibri (2006) or Aptos (2024).  These won’t be available to users of other office software.  Aptos won’t be available to anyone running an older version of Office.</p>

<p>The UK firm <a href="https://www.operandi.co.uk/about-operandi/">Operandi</a>, which specializes in designing branded document templates for corporations, publishes <a href="https://www.operandi.co.uk/support/safe-computer-fonts/">this list of safe MSOffice</a> fonts, defined as those available on Windows or Mac where Microsoft Office is installed.  Paring down to their list to just body-text sans-serifs “generally considered websafe”:</p>

<ul>
  <li>Arial</li>
  <li>Century Gothic</li>
  <li>Franklin Gothic</li>
  <li>Grandview</li>
  <li>Haettenschweiler</li>
  <li>Lucida Sans</li>
  <li>Seaford</li>
  <li>Skeena</li>
  <li>Tahoma</li>
  <li>Trebuchet MS</li>
  <li>Twentieth Century</li>
  <li>Verdana</li>
</ul>

<p>Of these, the following are also available in Word for iOS on my iPhone without additional download:</p>

<ul>
  <li>Arial</li>
  <li>Tahoma, the default Microsoft used for the UI of Windows 2000 and XP</li>
  <li>Trebuchet MS, which Microsoft used for window titles in Windows XP</li>
  <li>Verdana, designed for reading on old low-resolution screens</li>
</ul>

<p>Arial and Verdana were among Microsoft’s <a href="https://en.wikipedia.org/wiki/TrueType_core_fonts_for_the_Web">Core Fonts for the Web</a>, so are widely available for free download on Linux and other systems.</p>]]></content><author><name>Kyle E. Mitchell</name></author><category term="Contracts" /><category term="Drafting" /><category term="Typography" /><summary type="html"><![CDATA[a systematic search]]></summary></entry><entry><title type="html">Open Community License v1</title><link href="https://writing.kemitchell.com/2026/03/16/Open-Community-License-1" rel="alternate" type="text/html" title="Open Community License v1" /><published>2026-03-16T19:17:53-07:00</published><updated>2026-03-16T19:17:53-07:00</updated><id>https://writing.kemitchell.com/2026/03/16/Open-Community-License-1</id><content type="html" xml:base="https://writing.kemitchell.com/2026/03/16/Open-Community-License-1"><![CDATA[<p>Last year, <a href="https://www.prusa3d.com/">Prusa Research</a>, a Czechia-based manufacturer of 3D printers, drafted and adopted <a href="https://github.com/OpenCommunityLicence/OpenCommunityLicence/">a new license</a> for parts of its CORE line of not-entirely-open products, meant to take on the increasingly dominant and increasingly restrictive <a href="https://bambulab.com">Bambu Lab</a>.</p>

<h2 id="the-license-text">The License Text</h2>

<blockquote>
  <p>Open Community License (OCL v1)</p>
</blockquote>

<p>Versioning is good.  I’d’ve liked to see a more distinctive name.</p>

<p>“Open” and “Community” are the glitteriest of generalities.  Opportunistic marketing sucked them dry long before Prusa published this license.  I’d’ve rather seen “Prusa Public License” or some such.</p>

<blockquote>
  <p>OCL pertains to intellectual property applied in licensor’s products and/or its components (hardware and software) which is distributed under such, including copyright, design, and patent.</p>
</blockquote>

<p>Interesting example of a public license covering both hardware and software.  Licenses covering both are extremely common in private business transactions, but still fairly rare in public licensing practice.</p>

<p>Good on them for clearly mentioning copyright and patent.  I’d take “design” here to mean design patents.  Probably.  One more word would make it perfectly clear.</p>

<blockquote>
  <p>All licensors’s copyrights, designs, and patents as far as relevant to products and/or its components under OCL are community open, as the aim of OCL is to allow open access to community including the essential right, the right-to-repair, by giving users complete freedom of use, copy, modification, and hack, while promoting a fair competition by securing intellectual property rights to prevent vendor locking and patent trolling.</p>
</blockquote>

<p>I came away with the strange feeling this paragraph was meant to sugar the bitter medicine of a restricted license up by roll-calling as many causes célèbres of people who won’t like this license as possible.  Open access.  Right to repair.  Community again.  Fair competition.  Vendor locking—which I’d read as “vendor lock-in”.  Patent trolling.</p>

<p>The use of “hack” as a verb isn’t clear.  It feels a little patronizing here.  A little pandering.</p>

<blockquote>
  <p>NOTE that any part of the product and/or its component provided under a license incompatible with OCL remains unaffected by OCL.</p>
</blockquote>

<p>I’m not entirely sure what this is supposed to mean.  Are they saying that they can slap OCLv1 on a whole repo, then also slap some more restrictive license on things within that repo, like subdirectories, and those more restrictive terms override the OCL?  If so, I don’t think the OCL needs to say anything to make that possible.  Notices in repositories should make it clear.</p>

<blockquote>
  <p>As an [sic] non-commercial END USER</p>
</blockquote>

<p>No definition of “non-commercial.  None is coming later.</p>

<p>However, it’s clearly used here as a descriptor <em>of users</em>, rather than of uses.  Whatever “non-commercial” does or doesn’t mean, that can work out easier for users if their status stays relatively fixed, and they don’t have to think about whether each particular use or project is commercial.  But a lot of people cross over fluidly from personal to work and all kinds of places between, day by day.</p>

<blockquote>
  <p>YOU MAY use, copy, modify, hack the product and/or its components as you wish!</p>
</blockquote>

<p>The capitalized RFC 2119-style verbs usually strike me as unnecessary in legal terms.  They aren’t needed to be clear, and they rarely actually make much of anything clearer, so they mostly seem to work as a kind of dress-up, an attempt to evoke the authoritativeness or presumed rigor of technical standards in legal terms that never went through any standards process.  But I’ve seen them make technical people more comfortable with expressing themselves in license terms.  I don’t see any misuse here to cause problems.</p>

<blockquote>
  <p>YOU SHOULD support the 3D printing community by sharing your creations and modifications.</p>
</blockquote>

<p>I’d bet most US courts would interpret this as what they call “precatory language”: not an obligation any court is supposed to enforce, but just a use of a legal document as medium for getting other kinds of messages.</p>

<blockquote>
  <p>If you distribute your creations, modifications, or any such derivatives YOU MUST do so under OCL or any non-commercial, share-alike license allowing other community members to do everything that YOU MAY.</p>
</blockquote>

<p>Interesting.  A rare case of a share-alike/copyleft license giving flexibility in choice of license terms, beyond simply the same terms or a later version of them.</p>

<p>My own <a href="https://paritylicense.com/versions/7.0.0#contribute">Parity</a> does this, largely to avoid combinatorically expanding the set of potential so-called <a href="https://en.wikipedia.org/wiki/License_compatibility">license compatibility problems</a>.</p>

<p>The OCL’s takes a similar approach, which is also the hardest path, drafting wise: it allows an open-ended set of allowed licenses abstractly, by describing them functionally.  For Parity, the point was explicitly to allow <em>either</em> copyleft or less restricted <em>permissive</em> licensing.  As of version 7.0.0, that’s specified as “another license that allows everything this license [Parity 7.0.0] does”, followed by four named licenses, all permissive.  Here, Prusa seems to want non-commercial and copyleft—written “share-alike”—only, but then uses general language in terms of what’s <em>allowed</em>, like Parity.</p>

<p>I’d read that to allow choosing non-commercial and share-alike licenses that nonetheless allow <em>more</em> than OCLv1 does.  I’m not aware any such license currently exists.  Frankly, the only non-commercial-and-share-alike license that does is the rarely encountered <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/">CC-BY-NC-SA</a> from Creative Commons, whose licenses generally aren’t recommended for software, but have seen use specifically for hardware.</p>

<blockquote>
  <p>This does not concern your creations and modifications that are not derived from the product and/or its components.</p>
</blockquote>

<p>I’d guess what they’re after here is a comforting clarification that share-alike applies to work on 3D printers, rather than work <em>with</em> 3D printers, like objects you design to print and use.  “Derived from” is doing a lot of work here.   I’d state it more specifically, but that would be easier in a license specific to Prusa and its printers, rather than a generic license offered for reuse by anyone, for any kind of project.</p>

<blockquote>
  <p>As a commercial BUSINESS USER</p>
</blockquote>

<p>Without any definition of “commercial” or “non-commercial”, US courts forced to decide whether some use is or isn’t would look around the licenses for contextual hints.  One of the biggest is here: a clear association, if not strict identification, or “commercial” with “BUSINESS”.</p>

<p>That could help organizations like charities and universities, which are rarely called “businesses”, but do a lot more commercial work than many suppose.  That’s why the PolyForm team and I <a href="https://polyformproject.org/licenses/noncommercial/1.0.0/#noncommercial-organizations">specifically addressed generally non-commercial orgs doing arguably commercial things</a> in our noncommercial license for software.</p>

<blockquote>
  <p>YOU MAY use the product and modify it to your use case solely for your internal production use.</p>
</blockquote>

<p>The phrase “internal production use” isn’t a common one in legal drafting I’ve seen.  It seems awkwardly strung between two phrases that <em>are</em>, “internal business purposes” and “production use”.  Those phrases have different meanings, and I wonder if Prusa really wanted to blend them here, or just misquoted “internal business purposes”.</p>

<p>“Production” is industry jargon.  It exists mostly so we can distinguish <em>non-production</em> uses.  For example, many trial licenses with low or no fees and few if any warranties or risk protections only cover <em>non-production</em> use.  The gist is that the customer should try the product or service only in experiments, such as on fake data, and not hook it up to the systems or processes they actually use to sell or serve to others, or use to make money.  For that they need to buy a broader license with more robust legal terms.</p>

<p>I suspect Prusa wouldn’t have any problem with a business user modifying the printer bits they release under this OCLv1 for printing prototypes or test runs, or otherwise doing experiments that don’t yield products they sell to others or form parts of services they sell to others.  So their choice of wording seems like a simple mistake. Perhaps it was a translation error.</p>

<blockquote>
  <p>YOU MUST NOT modify the product and/or its components for any commercial purpose other than your internal production use.</p>
</blockquote>

<p>This is redundant, assuming the business user needs a license to modify in the first place.  No need to say “YOU MAY solely do X”, and then also say “YOU MUST NOT do the opposite of X”.</p>

<blockquote>
  <p>YOU MUST NOT copy or in any way replicate the product and/or its components for any commercial purpose excluding your internal right-to-repair without obtaining a separate business license or repair license.</p>
</blockquote>

<p>Subtle shift here: now “commercial” gets used a descriptor of <em>purposes</em>, rather than of <em>users</em>.</p>

<p>The reuse of “internal” here might suggest that “internal production use” needs to have something to do with repair.  I don’t think that’s clearly expressed, not as any kind of <em>definition</em> or <em>identity</em>.  But again, if a court had to hunt for clues to decide whether some business use was “internal production use”, that could be relevant.</p>

<blockquote>
  <hr />
</blockquote>

<p>I’m not against horizontal rules at all.  But as we’ll see, it’s not terribly clear what effect this particular one will have on legal meaning of terms that follow.</p>

<blockquote>
  <p>Licensor’s products and/or its components under OCL MUST NOT BE subject to any systematic or automated text and/or data mining or other text and/or data collection activity in relation to the product without explicit permission.</p>
</blockquote>

<p>Interesting example of an explicit ban on data mining, and potentially neural network model training.</p>

<p>It’s not clear to me whether is meant to be part of the license terms or just a notice.  There’s a horizontal rule just before, and everything that follows that line seems more like extra information than operative text.  But the idea that the license terms have ended and other, extra notices have begun.  The GPLs and Apache 2.0 say “END OF TERMS AND CONDITIONS”.  That’s clear.</p>

<p>With respect to “AI” these days, a few big questions hover over attempts to set these kind of rules for published works:</p>

<ul>
  <li>
    <p>Do model trainers even need license grants to use work released this way for training?  Or does that fall under “fair use” in the USA, the “text and data mining exception” in the EU, not enjoying the thoughts or sentiments expressed in Japan, or other exceptions elsewhere?</p>
  </li>
  <li>
    <p>Where the laws generally allow mining for training, but require trainers respect opt-outs, does putting this kind of thing in a public IP license, or after one, effectively opt out?  Are miners going to have to search the content they scrape for language like this?  Or is opting out going to require using some kind of public opt-out registry or technical standard for machine readable signaling?</p>
  </li>
  <li>
    <p>Where the laws generally allow mining for training, but require miners only hoover up data they otherwise have the legal right to access, does this kind of language potentially make their initial access unlawful?  How do these terms interact with terms of service and access norms for platforms where the licensor or others might distribute the licensed work, like GitHub’s?</p>
  </li>
</ul>

<blockquote>
  <p>To promote ease of understanding of OCL Licensor keeps and updates a database of products and/or its components licensed under OCL and good practice at [link to the database].</p>
</blockquote>

<p>I definitely wouldn’t recommend including this as operative text in any license.  You aren’t going to be able to update the link in copies of releases that other people redistribute among themselves.  You also open yourself up to contradictions in terms: you might add the license to a new project but forget or delay adding it to your global list.  Are people who see the list entitled to rely on it being complete and up-to-date, based on this language?</p>

<blockquote>
  <p>For practical examples of how this license applies, see the examples/ directory.</p>
</blockquote>

<p>The relevant directory is on GitHub <a href="https://github.com/OpenCommunityLicence/OpenCommunityLicence/blob/main/examples/prusa-ocl-examples.md">here</a>.</p>

<p>I’m very much a fan of using hypotheticals to explain the intent of license terms.  But if the examples are really meant to clarify the license, I wonder why they’re not either copied and pasted into its text or clearly incorporated by reference.</p>

<p>Mentioning them here, semi-casually, after a horizontal rule that may be meant to mark the end of the license terms that legally matter, only sets up ambiguities about the relationship of this license file to the examples files.  Both these license terms and the example files may change over time.</p>

<p>If the examples are just advisory, we have a problem similar to that of the GPL FAQs published by the Free Software Foundation.  Do they only matter if the FSF is the one that holds rights in the project that leads to a legal dispute?  Even in those situations, would allowing the FSF to cite them in court open up a back door allowing it to effectively monkeypatch its own license without updating the text or publishing a new, numbered version?</p>

<p>I am not aware of any rule against writing legal terms into a license, then following them with “For example…” and one or more hypotheticals.  I do it myself.  But whenever I or any other drafters feels intuitively that their legal terms don’t get their point across without examples, that’s a hint to give those terms more thought, too.  Rule-plus-examples should be an intentional choice, a decision about how best to get intent across, not a way to feel better than we should about sending bad language out into the world, like giving a football player with a busted ankle and sending him out onto the field.</p>

<h2 id="overall">Overall</h2>

<p>I don’t see this as a particularly well drafted license.  The combination of <em>both</em> a commercial/non-commercial segmentation <em>and</em> share-alike terms makes it particularly complex, functionally speaking.  At the same time, there’s little language here to help tame that complexity with clarity.</p>

<p>Still, I probably wouldn’t hesitate to rely on this license as a hobbyist doing things no one would confuse for business.  Everyone else should have a look and think twice.  And that’s probably the point.</p>]]></content><author><name>Kyle E. Mitchell</name></author><category term="Open Hardware" /><category term="Licenses" /><category term="3D Printing" /><summary type="html"><![CDATA[an unusual non-commercial hardware-software combo license from 3D printing]]></summary></entry><entry><title type="html">Open Core Ventures Source Available License Version 1.0</title><link href="https://writing.kemitchell.com/2026/03/10/OCVSAL-1.0" rel="alternate" type="text/html" title="Open Core Ventures Source Available License Version 1.0" /><published>2026-03-10T11:02:02-07:00</published><updated>2026-03-10T11:02:02-07:00</updated><id>https://writing.kemitchell.com/2026/03/10/OCVSAL-1.0</id><content type="html" xml:base="https://writing.kemitchell.com/2026/03/10/OCVSAL-1.0"><![CDATA[<p><a href="https://www.opencoreventures.com/">Open Core Ventures</a>, an open-focused venture capital firm, has published a <a href="https://github.com/OpenCoreVentures/open-core-ventures-source-available-license">new source-available license</a>.  It’s short.  Here are notes from my first couple reads through.</p>

<h2 id="takeaways">Takeaways</h2>

<ul>
  <li>
    <p>OCVSAL license only covers non-production use.  It explicitly mentions separate “commercial” production licenses.</p>
  </li>
  <li>
    <p>OCVSAL includes a built-in contributor license agreement.  While we’ve seen that before in licenses like Apache 2, it’s not clear whether, when, or how those could really work.  This one is particularly broad.</p>
  </li>
  <li>
    <p>OCVSAL says that if your local law doesn’t allow disclaiming all warranties, <em>you don’t get any license</em>.  That could affect more states and countries than folks might guess.</p>
  </li>
</ul>

<h2 id="text">Text</h2>

<blockquote>
  <p>Open Core Ventures Source Available License (OCVSAL) version 1.0</p>
</blockquote>

<p>Acronym is a bit of a mouthful.  Versioning is good!</p>

<blockquote>
  <p>Using software and associated documentation files (the “Software”) in production requires a valid commercial agreement from the copyright holder.</p>
</blockquote>

<p>Three cheers for putting the defining feature of the license up top.  This is a non-production license.  Expect to pay for production use.</p>

<p>I’m not aware of any definition of “production” that the law would impose.  Under American contract laws, courts generally try to figure out what the two sides to a set of terms like this meant and would have understood at the time they made their deal.  There is also a concept of “usage of trade”: identifying terms with special technical and business meanings and using evidence of what participants in those fields mean by them to interpret contracts.</p>

<p>Long story short, I’d expect a legal argument about whether a particular use of software under this license was “production” use to end up shaped like a battle of evidence about what “production” means among those in the US-based, English-speaking software business.  That’s not quite as helpful or efficient as a fully fleshed-out definition in the terms, but probably pretty clear in many potential situations.  It’s also a framing that points to what software people say and do, rather than empowering lawyers as the experts.</p>

<p>A small nit on the way this is drafted: vendors may also license through intermediaries like resellers.  I’d probably say something broader than “from the copyright holder”, though I suppose that could be stretched to cover sublicensing, too.</p>

<blockquote>
  <p>The licensor grants you the right to modify the Software, test it, and share modifications to the Software, for non-production use.</p>
</blockquote>

<p>Legally speaking, this is the operative crux, the “grant” where the titular “license” is actually given.  It’s very, very short.</p>

<p>No mention of patents.  Not a fatal law—see how far MIT and BSD got us—but a bit of a regression from the clarity of newer forms like <a href="https://apache.org/licenses/LICENSE-2.0">Apache 2</a> and <a href="https://blueoakcouncil.org/license/1.0.0">Blue Oak</a>.</p>

<p>It’s an interesting choice that it <em>does</em> give the right to make changes, and even to share them.  More about how those changes might be licensed coming below.</p>

<p>I’m struck that this grant does <em>not</em> mention copying, or “reproduction in copies” as the Copyright Act says.  Of course, that will arguably go without saying, especially as a necessary step for “test[ing]” and “use”.</p>

<p>Neither does this grant mention sharing—“distribution of copies”—<em>without</em> modifications.  Yet I’d assume that most adopters of this kind of license would be glad to see verbatim copies traded about like shareware, and not just provide downloads themselves.</p>

<blockquote>
  <p>You must retain this license on any copies of the Software you share with others.</p>
</blockquote>

<p>Short notice-attribution requirement.  Normal open-license stuff.</p>

<blockquote>
  <p>If you provide suggestions, contributions, or other feedback about the Software, you grant the licensor an irrevocable, royalty-free, unlimited license to use that feedback without restriction.</p>
</blockquote>

<p>A built-in CLA, and a very broad one.  This is mixing terminology that we’d typically see in the “feedback” sections of commercial license or SaaS terms with the kind of explicit license-grant language we’d see in a CLA.</p>

<p>The <a href="https://apache.org/licenses/LICENSE-2.0">“Submission of Contributions” section of Apache 2</a> has long stood as an example of writing terms for licensing <em>back</em> from contributors into terms for licensing <em>on</em> to users.  Enforcing that kind of term would be a new move at law, as far as I’m aware.  I suspect it would depend very heavily on establishing license terms as the terms of a contract, rather than just a one-way license grant.  There’s ongoing legal action around those rules now.</p>

<p>The license-grant language here starts to follow the orthodox drafting approach of listing out a bunch of adjectives for various properties of the license: “irrevocable”, “royalty-free”, “unlimited”.  Some of the usual “flags” left out have defaults that I think suit the use case here.  But I’d probably add “sub-licensable” explicitly, to make the thing that the project steward will want to do—incorporate the contributions as part of their project and continue licensing that project overall however it wants—explicitly clear.</p>

<blockquote>
  <p>THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.</p>
</blockquote>

<p>Typical all-warranties disclaimer.</p>

<blockquote>
  <p>IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>
</blockquote>

<p>Typical open-style damages exclusion.</p>

<blockquote>
  <p>IF THE FOREGOING WARRANTY DISCLAIMER IS UNENFORCEABLE UNDER APPLICABLE LAW, THIS LICENSE IS VOID AND YOU HAVE NO RIGHT TO USE THE SOFTWARE.</p>
</blockquote>

<p>Very important.  This potentially makes the whole license a <a href="https://en.wikipedia.org/wiki/NOP_(code)">no-op</a> in many meaningful jurisdictions.  This includes US states that adopted the Uniform Computer Information Transactions Act—Maryland and Virginia—which imposes mandatory warranties, with an exception for “free software” that I would read to clearly <em>not</em> apply to software offered under commercial license for production use.</p>

<p>This isn’t completely new.  I’d argue the EUPL does the same.</p>

<p>I’m not sure whether this kill-switch is meant to apply just if the warranty disclaimers aren’t enforceable, or also if the damages exclusions aren’t.  I’d clarify that, if only to throw light on which jurisdictions the license doesn’t work in.</p>

<hr />

<p><em>Important Correction</em>: As originally published, this blog post attributed the new license to Heather Meeker.  Heather’s firm is <a href="https://oss.capital/">OSS Capital</a>, not Open Core Ventures.  A regrettable and embarrassing mistake!  Thanks to Heather for letting me know.</p>]]></content><author><name>Kyle E. Mitchell</name></author><category term="Source Available" /><category term="Software Licensing" /><category term="Contributor Licensing" /><summary type="html"><![CDATA[a very short non-production license with twists]]></summary></entry><entry><title type="html">LLMs Make Legal Advice Lossy</title><link href="https://writing.kemitchell.com/2025/12/07/LLMs-Make-Legal-Advice-Lossy" rel="alternate" type="text/html" title="LLMs Make Legal Advice Lossy" /><published>2025-12-07T20:15:33-08:00</published><updated>2025-12-07T20:15:33-08:00</updated><id>https://writing.kemitchell.com/2025/12/07/LLMs-Make-Legal-Advice-Lossy</id><content type="html" xml:base="https://writing.kemitchell.com/2025/12/07/LLMs-Make-Legal-Advice-Lossy"><![CDATA[<p>With many-megapixel cameras in our pockets and networks so fast that streaming hiccups piss off pre-teens, it’s easy to forget how frail digital imagery used to be.  When storage cost real money and the Internet was slow, we took photos at much lower resolution.  Then we used formats like <a href="https://en.wikipedia.org/wiki/JPEG">JPEG</a> to strip detail in clever ways that preserved overall impressions, for the sake of speedy sharing.  But if you zoomed in on an image, or even just looked closer, you’d find blurry blobs, jagged edges, and cryptic <a href="https://en.wikipedia.org/wiki/Compression_artifact">artifacts</a> where nuance should have been.  Such were the losses of <a href="https://en.wikipedia.org/wiki/Lossy_compression">lossy compression</a>.</p>

<p>In the real world, there was no <a href="https://tvtropes.org/pmwiki/pmwiki.php/Main/EnhanceButton">enhance button</a>.  Sometimes a photo just wouldn’t show you what you needed to see.  So you had to search around for a better image and wait for it to download.  Or you had to go back to the source.</p>

<p>Something similar is happening with advice to some of my clients.  Instead of reading what I write for them, they’re pasting it into chatbots for summaries, then reading those summaries instead.  It’s fast.  It’s cheap.  It’s at least notionally private.  They don’t have to tell me they’re doing it.</p>

<p>More often than they might hope, I can tell.</p>

<h2 id="abstraction-control">Abstraction Control</h2>

<p>When I give advice, I am nearly always summarizing <em>something</em> from the get-go.  Unless we are really in the weeds of some specific risk assessment or legal theory, I rarely copy-paste statutes, regulations, or court opinions at my clients.  Rather, it’s my job to give the shortest, cleanest generalizations of the rules that work for the decision they need to make—abstractions of the law that <a href="https://en.wikipedia.org/wiki/Leaky_abstraction">leak</a> off into irrelevant space, not all over their dreams and plans.</p>

<p>I pick the level of each abstraction.  That is often one of the most important decisions I make in service of a client on a problem.  How high-level can we talk?  Where do we need to drill down from there?</p>

<p>LLMs give my clients a silent veto over these decisions.  Prevailing trends toward ever sparser chat- and text-style writing, plus the ever crushing weight of time pressure, push them in one direction: fewer words, fewer details, terser summaries. In other words, lossier pictures of the law, more riven with smudge-blobby background, <a href="https://en.wikipedia.org/wiki/Jaggies">corrupted lines</a>, and <a href="https://en.wikipedia.org/wiki/Aliasing">arbitrary aberrations</a>.  Cheap automatic summaries of expensive professional précis of complex, often unsynthesized source material.</p>

<p>Based on prior, pre-LLM experience with expertise, I suspect using a chatbot to do this looks and intuitively <em>feels</em> different from using an LLM to flesh a subject out.  Few remain surprised now when prompting an LLM too hard summons out inscrutable gobbledygook littered with allusions or even citations to nonexistent authorities, thanks to <a href="https://www.damiencharlotin.com/hallucinations/">the headline-grabbing lawyers who’ve fallen in this hole by the pageful</a>.  But I’m not aware of any similar click-grabbing parables for the dangers of chatbot summarization, unless you squint and count the poor souls who’ve convinced themselves they’re geniuses or prophets.  Given the abstractness involved—we’re talking about a general pattern with the process of generalization here—I wonder if there could be such a story.</p>

<h2 id="for-instance">For Instance</h2>

<p>Having made that rather lofty generalization-of-generalities point, I feel a sudden urge to touch ground again.  Perhaps that’s the kind of instinct that’s helping keep some of us sane these days.</p>

<p>Take the basic rule of copyright ownership that authors own the rights in their works.  That’s a fair general statement of the law on the books.  It’s also a dangerous thing to tell a client involved in working business.  In business, the “rule”—the normal thing that usually happens—is that legal rights end up with employers and clients.  Sometimes the law itself gives them over.  Sometimes they get there through contracts most everyone signs.</p>

<p>Even that more practical heuristic lays traps for unwary clients when exceptions matter.  Is the client dealing with contracts doing one of the kinds of jobs that can be “work made for hire” under the <a href="https://www.govinfo.gov/app/details/USCODE-2024-title17/USCODE-2024-title17-chap1-sec101">statutory definition</a>?  Is telling the client about “ownership” without mentioning <a href="https://www.npr.org/sections/therecord/2013/09/12/221750447/taking-back-funkytown-songwriters-prepare-for-a-custody-battle">some creators’ rights to terminate old deals after 35 years</a> heaping on irrelevant trivia or pointing out a critical wrinkle?  Do we need to talk exceptions just under current law, for new work, or do we need to consider old rules for older works, as well?</p>

<p>Not every legal question points to a decision tree as knotted as this one.  But this one’s not an especially crooked specimen, either.  The law can do far worse, then flock a few branches with uncertainty, besides.</p>

<p>It is a totally normal part of a functioning lawyer’s day to mentally scale levels of abstraction like this, picking and choosing where to stand the client, what to point at, and what wave past.  After all, every irrelevant nuance, variation, and aberration costs money to write up, eats client time, and drags the convo closer to their limit, where there’s just too much new information, they’re overwhelmed, we all fall down, and we have to double back again.</p>

<p>Getting good at neither coddling nor firehosing clients is a significant part of the difference between being a good law student and being a good lawyer.  If you learn all the rules, exceptions, and citations and stop there, you are at best fully equipped to waste a lot of client time.  Practicing law is often partly teaching law, but unless the job is law professor, we’re rarely called on to teach anybody everything on any particular point.  Hiring a lawyer is not attending law school secondhand in installments.  We pay lawyers to think, not just remember.</p>

<p>Still, we’ve all seen the kind of run-on, over-inclusive, largely unhelpful advice that comes from counsel who “dump” the law as they learned it, or in the raw form they recently dug it out of the books, without any tailoring to their reader or the problem.  This is what a lot of law-student and new-lawyer writing looks like.</p>

<p>Overshooting on detail is apparently a natural tendency for competent, aspiring minds learning the field.  Now we’ve given clients the tools to overcompensate by <em>under</em>shooting.  We’ve automated it, hyped it, and subsidized it.</p>

<h2 id="word-choice">Word Choice</h2>

<p>I have also seen a second, related danger.  I’m less confident I can spot this when it’s happening, but I’m developing a hunch that’s more often than I first thought.</p>

<p>To summarize a summary is not just to compress an already compressed explanation, but also, often, to reword it.  Choice of words can be important in what I do.  Not inevitably in the cartoonish way those with little experience of the law tend to suppose, where <a href="https://www.youtube.com/watch?v=Qgr4dcsY-60">failing to say exactly the right thing makes no magic</a>.  In a more serious way affecting how much advice my clients need, longer-term.</p>

<p>Many of my clients, maybe most, have heard me say that it’s my job to learn their language, not their job to learn mine.  I’ve found this to be an effective way of signaling that it’s on me to write and speak so my clients understand, and on them to complain when they don’t and not feel sheepish about it.  It’s a framing tool like the <a href="https://flippedform.com/">flipped form concept</a>, but for correspondence, not just drafted operative terms.</p>

<p>Still, there are occasionally tidbits of jargon that just make sense to teach and to learn.  To help clients communicate with others besides me.  To help them search out supplementary materials.  To make them seem savvy in more experienced company.</p>

<p>Sometimes these are words or phrases directly from primary sources, like “derivative work” in the Copyright Act.  Sometimes they’re live concepts in law or business practice, like “right of first refusal”.  And sometimes they’re well distributed technical terms, like <a href="https://en.wikipedia.org/wiki/Fork_(software_development)">“forking” in software</a>.  It’s important to be able to explain each of these in Real English.  But there’s separate, identifiable value in knowing which shorthands get said and heard.</p>

<p>When a client uses a chatbot to effectively rewrite my guidance, I lose control of how worthwhile terms get introduced.  I lose control of how they’re sprinkled through the text later, <a href="https://en.wikipedia.org/wiki/Input_hypothesis">to develop fluency</a>.  Both content and presentation end up on invisible autopilot.  There is no bright line between those in the law.</p>

<p>I’ve seen this bite in particular where a client takes a summary without telling me, advances the conversation, and then misunderstands a later message.  All of a sudden, it turns out they weren’t following along on all the levels I’d assumed.  They weren’t getting everything they paid for, either.</p>

<p>If I was going deeper or longer than suited their needs, that should have been said, and I should have adjusted, potentially reducing their bill.  As they fell deeper behind on the lingo then anticipated, I can only expect they hit their limit sooner, potentially inducing yet more summarization on the sly.</p>

<h2 id="still">Still</h2>

<p>None of this is to say it’s all bad.  There is a pressure coming here that I feel I ought to welcome.</p>

<p>I blog in sections.  My e-mails often come with bold-faced headings.  I do a lot of outlining.  Increasingly chat-, text-, and tweet-driven workstyles are veering ever further away from my preferred dose and concentration of prose.  And yes, I’m getting older.</p>

<p>I see some strong if somewhat hand-wavy arguments that slower, longer, and careful writing better suit at least some of the kinds of work clients pay me to do.  But in the same way it’s on me to write so clients understand, there’s a strong case it should be on me to write more like what they’d prefer to read, as well.</p>

<p>Fortunately, while the dramas of this new lawyer-client dynamic interest me well enough, I don’t think they point to any kind of newfangled remedy.  I need to keep pushing myself, and setting clients up to push me, toward plainer, shorter, better organized writing.  We also need to stay on the level.  If clients are in positions that drive them to interpose chatbots between us, whether out of verve for the tech or simply under time crunch, I should be making it clear that’s something they should tell me they’re doing.  I should be prompting them to say so.</p>]]></content><author><name>Kyle E. Mitchell</name></author><category term="AI" /><category term="Law Practice" /><category term="Writing" /><summary type="html"><![CDATA[cheap chatbot summaries take important choices away]]></summary></entry><entry><title type="html">PolyForm Noncommercial 2.0.0-pre.2</title><link href="https://writing.kemitchell.com/2025/11/05/PolyForm-Noncommercial-2.0.0-pre.2" rel="alternate" type="text/html" title="PolyForm Noncommercial 2.0.0-pre.2" /><published>2025-11-05T00:00:00-08:00</published><updated>2025-11-05T00:00:00-08:00</updated><id>https://writing.kemitchell.com/2025/11/05/PolyForm-Noncommercial-2.0.0-pre.2</id><content type="html" xml:base="https://writing.kemitchell.com/2025/11/05/PolyForm-Noncommercial-2.0.0-pre.2"><![CDATA[<p>Here is the latest draft of the PolyForm Noncommercial license for software, with the edits that got left out of the draft I blogged yesterday.  I’ve gone in and marked the changes for anyone who read the first.</p>

<blockquote>
  <h1 id="polyform-noncommercial-license-200-pre2">PolyForm Noncommercial License 2.0.0-pre.2</h1>

  <p><a href="https://polyformproject.org/licenses/noncommercial/2.0.0-pre.2">https://polyformproject.org/licenses/noncommercial/2.0.0-pre.2</a></p>

  <h2 id="noncommercial-use">Noncommercial Use</h2>

  <p>This license gives you free permission for this software, but only for noncommercial uses. The next two sections give examples of noncommercial uses, but do not rule out others.</p>

  <h2 id="personal-uses">Personal Uses</h2>

  <p>Research, experiment, and testing for the benefit of public knowledge, education, private entertainment, hobby projects, amateur pursuits, and religious observance are all noncommercial uses.</p>

  <h2 id="noncommercial-organizations">Noncommercial Organizations</h2>

  <p>Work on behalf of any charitable organization, educational institution, public research organization, public safety or health organization, environmental protection organization, or government institution are all noncommercial uses.</p>

  <h2 id="copyrights">Copyrights</h2>

  <p>The licensor gives you permission under its copyrights in this software to run, <ins>make copies of,</ins> make changes to, and share copies of and changes to this software, but only for noncommercial uses.</p>

  <h2 id="patents">Patents</h2>

  <p>The licensor gives you permission under any patent claims it can license, or becomes able to license, that you would infringe by running, <ins>copying,</ins> changing, or sharing this software, but only for noncommercial uses.</p>

  <h2 id="notices">Notices</h2>

  <p>Make sure anyone who gets a copy of this software from you also gets a copy of this license or the URL for it above, as well as copies of any plain-text lines beginning with <code class="language-plaintext highlighter-rouge">Required Notice:</code> that the licensor provided with this software.</p>

  <h2 id="fair-use">Fair Use</h2>

  <p>This license does not limit “fair use” under copyright law.</p>

  <h2 id="no-other-rights">No Other Rights</h2>

  <p>You may not sublicense or transfer your license for the software to anyone else. The terms of this license do not imply any other <del>licenses</del><ins>permission</ins>.</p>

  <h2 id="patent-defense">Patent Defense</h2>

  <p>If you claim in writing that this software infringes or contributes to infringement of any patent, your patent permission under this license ends immediately. If your company claims in writing that this software infringes or contributes to infringement of any patent, your patent permission ends immediately for work on behalf of your company.</p>

  <h2 id="violations">Violations</h2>

  <p>The first time the licensor warns you in writing that you have violated any term of this license, or done anything with the software not permitted by this license, your <ins>copyright and patent permission under this </ins>license can nonetheless continue if you come into full compliance with this license, and take practical steps to correct past violations, within 30 days. Otherwise, your copyright and patent permission under this license ends immediately.</p>

  <h2 id="no-liability">No Liability</h2>

  <p><strong><em>As far as the law allows, this software comes as is, without any warranty or condition. As far as the law allows the licensor will not be liable to you for any legal damages related to this license or this software, under any kind of legal claim.</em></strong></p>

  <h2 id="you-and-your-company">You and Your Company</h2>

  <p>Throughout this license, <em>you</em> refers to the individual or legal entity agreeing to these terms, and <em>your company</em> refers to any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization. <em>Control</em> means ownership of substantially all the assets of an organization or the power to direct its management and policies by vote, contract, or otherwise.</p>
</blockquote>]]></content><author><name>Kyle E. Mitchell</name></author><category term="Software Licensing" /><category term="Software" /><category term="Noncommercial" /><summary type="html"><![CDATA[shorter, better noncommercial license terms for software]]></summary></entry><entry><title type="html">PolyForm Noncommercial 2.0.0-pre.1</title><link href="https://writing.kemitchell.com/2025/11/04/PolyForm-Noncommercial-2.0.0-pre.1" rel="alternate" type="text/html" title="PolyForm Noncommercial 2.0.0-pre.1" /><published>2025-11-04T21:26:08-08:00</published><updated>2025-11-04T21:26:08-08:00</updated><id>https://writing.kemitchell.com/2025/11/04/PolyForm-Noncommercial-2.0.0-pre.1</id><content type="html" xml:base="https://writing.kemitchell.com/2025/11/04/PolyForm-Noncommercial-2.0.0-pre.1"><![CDATA[<p><a href="https://heathermeeker.com">Heather Meeker</a> and I have long wanted to do new version 2s of the <a href="https://polyformproject.org">PolyForm</a> licenses, to make them even shorter and easier to read.  We now have a draft of a new <a href="https://polyformproject.org/licenses/noncommercial/">Noncommercial</a> license to share, down to less than 550 words.</p>

<p>If you have a chance to read through, do share any thoughts to <a href="mailto:kyle@kemitchell.com">kyle@kemitchell.com</a>.  We give these licenses away for free, and put a ton of extra work in to try and make them approachable.  Every fresh pair of eyes and fresh perspective makes the terms better for all involved.</p>

<blockquote>
  <h1 id="polyform-noncommercial-license-200-pre1">PolyForm Noncommercial License 2.0.0-pre.1</h1>

  <p><a href="https://polyformproject.org/licenses/noncommercial/2.0.0-pre.1">https://polyformproject.org/licenses/noncommercial/2.0.0-pre.1</a></p>

  <h2 id="noncommercial-use">Noncommercial Use</h2>

  <p>This license gives you free permission for this software, but only for noncommercial uses. The next two sections give examples of noncommercial uses, but do not rule out others.</p>

  <h2 id="personal-uses">Personal Uses</h2>

  <p>Research, experiment, and testing for the benefit of public knowledge, education, private entertainment, hobby projects, amateur pursuits, and religious observance are all noncommercial uses.</p>

  <h2 id="noncommercial-organizations">Noncommercial Organizations</h2>

  <p>Work on behalf of any charitable organization, educational institution, public research organization, public safety or health organization, environmental protection organization, or government institution are all noncommercial uses.</p>

  <h2 id="copyrights">Copyrights</h2>

  <p>The licensor gives you permission under its copyrights in this software to run, make changes to, and share copies of and changes to this software, but only for noncommercial uses.</p>

  <h2 id="patents">Patents</h2>

  <p>The licensor gives you permission under any patent claims it can license, or becomes able to license, that you would infringe by running, changing, or sharing this software, but only for noncommercial uses.</p>

  <h2 id="notices">Notices</h2>

  <p>Make sure anyone who gets a copy of this software from you also gets a copy of this license or the URL for it above, as well as copies of any plain-text lines beginning with <code class="language-plaintext highlighter-rouge">Required Notice:</code> that the licensor provided with this software.</p>

  <h2 id="fair-use">Fair Use</h2>

  <p>This license does not limit “fair use” under copyright law.</p>

  <h2 id="no-other-rights">No Other Rights</h2>

  <p>You may not sublicense or transfer your license for the software to anyone else. The terms of this license do not imply any other licenses.</p>

  <h2 id="patent-defense">Patent Defense</h2>

  <p>If you claim in writing that this software infringes or contributes to infringement of any patent, your patent permission under this license ends immediately. If your company claims in writing that this software infringes or contributes to infringement of any patent, your patent permission ends immediately for work on behalf of your company.</p>

  <h2 id="violations">Violations</h2>

  <p>The first time the licensor warns you in writing that you have violated any term of this license, or done anything with the software not permitted by this license, your license can nonetheless continue if you come into full compliance with this license, and take practical steps to correct past violations, within 30 days. Otherwise, your copyright and patent permission under this license ends immediately.</p>

  <h2 id="no-liability">No Liability</h2>

  <p><strong><em>As far as the law allows, this software comes as is, without any warranty or condition. As far as the law allows the licensor will not be liable to you for any legal damages related to this license or this software, under any kind of legal claim.</em></strong></p>

  <h2 id="you-and-your-company">You and Your Company</h2>

  <p>Throughout this license, <em>you</em> refers to the individual or legal entity agreeing to these terms, and <em>your company</em> refers to any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization. <em>Control</em> means ownership of substantially all the assets of an organization or the power to direct its management and policies by vote, contract, or otherwise.</p>
</blockquote>]]></content><author><name>Kyle E. Mitchell</name></author><category term="Software Licensing" /><category term="Software" /><category term="Noncommercial" /><summary type="html"><![CDATA[shorter, better noncommercial license terms for software]]></summary></entry><entry><title type="html">Wired on a Surrogacy Gone Wrong</title><link href="https://writing.kemitchell.com/2025/10/15/Surrogacy" rel="alternate" type="text/html" title="Wired on a Surrogacy Gone Wrong" /><published>2025-10-15T00:00:00-07:00</published><updated>2025-10-15T00:00:00-07:00</updated><id>https://writing.kemitchell.com/2025/10/15/Surrogacy</id><content type="html" xml:base="https://writing.kemitchell.com/2025/10/15/Surrogacy"><![CDATA[<p>If you have access to <a href="https://www.wired.com">Wired Magazine</a> and teach or think about contracts, I’d strongly recommend <a href="https://www.wired.com/story/the-baby-died-whose-fault-is-it-surrogate-pregnancy/">“The Baby Died. Whose Fault Is It?”</a> by Emi Nietfeld, about a contract for <a href="https://en.wikipedia.org/wiki/Surrogacy">surrogacy</a> gone wrong.</p>]]></content><author><name>Kyle E. Mitchell</name></author><category term="Contracts" /><summary type="html"><![CDATA[a thoroughly modern contract case]]></summary></entry></feed>