But Is It Open?The online edition
Type & theme

Make yourself comfortable

Page color
Text size
20 px
Reading width
Ask about this chapter ↗

Your settings and place stay in this browser.

Chapter 16 · Timothy O’Brien

Legal Background for Engineers and Users

5 minute read14 source notesFree online edition

An engineer can read a license and still be unable to say what a court would do with it. That doesn’t make reading pointless. It helps distinguish a permission you actually have from an assumption built around a download button.

Chapter 15 covered the documents and clauses to preserve. This chapter covers the legal questions beneath them: how permissions can be enforced, what counts as an agreement, whose law applies, and when an experiment becomes a commitment. I am not a lawyer; the purpose here is to help engineers recognize and describe those questions for qualified counsel.

Open-source conditions are part of the arrangement that makes reuse possible. Apache 2.0 requires notices and identification of changes when distributing covered material. The GPL imposes additional obligations when copies are conveyed.1 Those conditions differ from model terms that limit a field of use or require a larger business to negotiate permission.

Jacobsen v. Katzer is an important example of enforcement. The Federal Circuit held that the Artistic License’s conditions could be enforced as copyright conditions, rather than only as contractual promises.2 The decision did not establish that every license term is enforceable everywhere, and it did not address model weights.

Other familiar cases need their procedural status attached. In Artifex v. Hancom, the court allowed contract and copyright claims concerning Ghostscript to proceed past dismissal. That ruling did not find a GPL violation; the parties later settled.3 Software Freedom Conservancy’s case against Vizio asks whether a consumer can enforce source-code obligations as an intended third-party beneficiary of the GPL. The cited case record was still ongoing at the manuscript’s November 2026 cutoff. Intermediate rulings did not decide every question in SFC’s favor.4

A second distinction is between a license condition and a contractual promise. MDY v. Blizzard held that violating the covenant at issue was not itself copyright infringement. Berman v. Freedom Financial Network required conspicuous notice and unambiguous assent for the online contract theory before it.5 These software and consumer-web cases help identify questions about model agreements; none decides whether all model weights are copyrightable or whether every download creates a contract.

Most open-source projects never see litigation. Their participants share code, review changes, and resolve disagreements without it. The legal permissions still matter when someone tests the arrangement, particularly when the relationship is no longer cooperative.

When a prototype becomes a commitment

“It’s only a prototype” describes a stage of development, not a legal exemption. A team may already have accepted access terms, sent confidential information to a service, or distributed a derivative before it decides the prototype is a product.

Agentic development can bring those decisions forward. These are illustrations, not incidents I’m reporting: a tool might choose a dependency, accept gated access using a company account, send a dataset to an API, or publish a fine-tune. Each can create a question about permission, authority, or disclosure. Whether a particular agent action binds a person or company is fact-dependent; assuming it cannot is a poor operating rule.

Inexperience makes the consequences easier to dismiss. Discovery, interruption, and disputes over what someone accepted are expensive even before a court decides the merits. Keeping the technical record from chapter 15 makes the decision easier to reconstruct.

Knowledge can matter to particular claims, defenses, and remedies. It does not excuse every infringement. In U.S. copyright law, intent generally is not an element of infringement, although innocent infringement can reduce statutory damages.6 “We didn’t know” and “it was experimental” are therefore explanations to investigate, not protections to rely on.

The useful threshold is the point where work commits the organization: accepting special terms, disclosing protected data, deploying for customers, or distributing material. Review the terms while the choice can still be changed cheaply.

Whose law, and which court

A governing-law clause identifies the law used to interpret an agreement. A forum clause identifies where disputes are heard. An arbitration clause can send the dispute outside ordinary court proceedings. They are separate provisions.

Classic open-source licenses often omit them. Apache 2.0 grants worldwide copyright and patent permissions without choosing a governing law, court, or arbitration process.7 Some model agreements make explicit choices.

The older DeepSeek-LLM model license selects Chinese law and exclusive jurisdiction in the courts where the relevant Hangzhou company is domiciled.8 The license for Qwen1.5-1.8B likewise specifies Chinese law and Hangzhou courts.9 These are court clauses, not arbitration requirements.

They also belong to particular releases. The cited Qwen3 checkpoint moved to Apache 2.0, while Qwen3.8-Max later used a custom license.10 Original DeepSeek-V3 retained a custom model license with the Hangzhou clause, but DeepSeek-R1 and DeepSeek-V3-0324 use MIT, which has no governing-law clause.11 Kimi K2’s modified MIT text also lacks a governing-law or forum clause.12 The publisher’s home country is no substitute for reading the file.

Suppose you download an older checkpoint in Albuquerque. Have you agreed to litigate in Hangzhou? The text alone cannot answer. Did you click agreement or merely receive a file containing a notice? Are you acting as a consumer or business? Is the clause exclusive, and can local mandatory protections override it? Where are the parties and their assets, and what claim is being brought?

A choice-of-law clause can matter without guaranteeing a foreign hearing. A resulting judgment may also need recognition where enforcement is sought. The Hague conventions on court agreements and judgments, and the New York Convention on arbitration awards, address different parts of that process; they do not make every model agreement enforceable in every country.13

Hosted access adds another relationship. The API or enterprise agreement may supply the relevant venue, data-processing obligations, and indemnity.14 The same model can reach a user through a direct API, an aggregator, a cloud marketplace, or a local download. Those routes need separate analysis.

What to bring to counsel

A consequential use deserves review by someone who knows the agreements and jurisdictions involved. Common triggers include:

  • customer-facing deployment or distribution of weights, adapters, or fine-tunes
  • training, distillation, or fine-tuning using another provider’s material
  • confidential or personal data, or a licensed retrieval collection
  • a regulated workflow or an agent authorized to take consequential actions
  • unreleased models, evaluation access, or other specially negotiated terms

Bring the precise release identifier, revision, saved license and incorporated policies, access record, and service agreements. Add a system map: which model is called through which provider, what data enters it, where processing occurs, and where outputs go. Note changes since the original review.

The engineering task is to describe the system accurately enough that another person can analyze it. The legal task is to evaluate that account against the agreements and law. A lawyer cannot assess an arrangement the team cannot explain, and an engineer should not promise a court outcome from a model-card label.

Those questions remain when someone changes the weights. The next chapter follows them through models whose refusal behavior has been removed.

Notes

  1. Apache Software Foundation, “Apache License, Version 2.0,” January 2004, section 4 (redistribution must keep copyright and attribution notices and carry “prominent notices stating that You changed the files”), https://www.apache.org/licenses/LICENSE-2.0; Free Software Foundation, “GNU General Public License, version 3,” 29 June 2007, sections 4 to 6 (conditions on conveying copies, including source-code obligations), https://www.gnu.org/licenses/gpl-3.0.html. ↩

  2. Jacobsen v. Katzer, 535 F.3d 1373 (Fed. Cir. 2008), No. 2008-1001, decided 13 August 2008, https://www.cafc.uscourts.gov/opinions-orders/08-1001.pdf. The court vacated the denial of a preliminary injunction and remanded, “having determined that the terms of the Artistic License are enforceable copyright conditions.” On remand the district court again denied a preliminary injunction: Jacobsen v. Katzer, 609 F. Supp. 2d 925 (N.D. Cal. 2009), https://openjurist.org/609/fsupp2d/925/jacobsen-v-katzer-1886775. ↩

  3. Artifex Software, Inc. v. Hancom, Inc., No. 3:16-cv-06982-JSC (N.D. Cal.), order denying motion to dismiss, ECF No. 32 (25 April 2017), docket on CourtListener, https://www.courtlistener.com/docket/4548911/artifex-software-inc-v-hancom-inc/. Hancom had argued, among other things, that as a South Korean company developing its software outside the United States it could not face U.S. copyright damages: Wilson Sonsini, “Court Ruling Supports Contractual and Statutory Enforcement of Open Source Software Licenses,” 19 May 2017, https://www.wsgr.com/en/insights/court-ruling-supports-contractual-and-statutory-enforcement-of-open-source-software-licenses.html. The ruling addressed the pleadings, not the merits; the parties filed a notice of settlement in December 2017 and the case was dismissed with prejudice on 17 January 2018 (same docket). ↩

  4. Software Freedom Conservancy, Inc. v. Vizio, Inc., No. 30-2021-01226723-CU-BC-CJC (Cal. Super. Ct., Orange County, filed 19 October 2021); Software Freedom Conservancy, “Software Freedom Conservancy v. Vizio Inc.” (case page listing the status as ongoing with trial in late 2026; last updated 27 February 2026), https://sfconservancy.org/copyleft-compliance/vizio.html. Rulings so far are procedural or partial. On 29 December 2023 the court denied Vizio’s motion for summary judgment, finding a triable issue of fact on whether SFC is a third-party beneficiary of the GPL: minute order, https://sfconservancy.org/docs/Order_Denying_Vizio_Motion_for_Summary_Judgement_12-29-23.pdf. On 23 December 2025 it granted Vizio’s second motion for summary adjudication on a narrower question, holding that GPLv2 and LGPLv2.1 do not require that modified software be reinstallable while the device stays operable: minute order, https://sfconservancy.org/docs/2025-12-23_SFC-vs-Vizio_30-2021-01226723-CU-BC-CJC_Leal-minute-order.pdf. No final judgment was found as of 15 November 2026. ↩

  5. MDY Industries, LLC v. Blizzard Entertainment, Inc., 629 F.3d 928 (9th Cir. 2010), amended opinion, section III.B, https://law.justia.com/cases/federal/appellate-courts/ca9/09-15932/09-15932-2011-02-25.html; Berman v. Freedom Financial Network, LLC, 30 F.4th 849 (9th Cir. 2022), https://cdn.ca9.uscourts.gov/datastore/opinions/2022/04/05/20-16900.pdf. These concern the claims and agreements before those courts, not model-license enforceability generally. ↩

  6. 17 U.S.C. § 504(c)(2) (where the infringer proves it “was not aware and had no reason to believe that his or her acts constituted an infringement of copyright,” the court may reduce statutory damages to not less than $200), Legal Information Institute, Cornell Law School, https://www.law.cornell.edu/uscode/text/17/504. On intent: Fitzgerald Publishing Co. v. Baylor Publishing Co., 807 F.2d 1110 (2d Cir. 1986) (“Even an innocent infringer is liable for infringement. Under Sec. 501(a) intent or knowledge is not an element of infringement.”), Justia, https://law.justia.com/cases/federal/appellate-courts/F2/807/1110/311559. ↩

  7. Apache Software Foundation, “Apache License, Version 2.0,” sections 2 and 3 (perpetual, worldwide copyright and patent grants), https://www.apache.org/licenses/LICENSE-2.0. The text has no governing-law, venue, or arbitration section; it mentions “applicable law” only in its warranty and liability clauses. ↩

  8. DeepSeek, “DeepSeek License Agreement,” Version 1.0, 23 October 2023, section 14 (“governed and construed under PRC laws”; “The courts located in the domicile of Hangzhou DeepSeek Artificial Intelligence Fundamental Technology Research Co., Ltd. shall have exclusive jurisdiction”), LICENSE-MODEL in the DeepSeek-LLM repository, GitHub, https://github.com/deepseek-ai/DeepSeek-LLM/blob/main/LICENSE-MODEL. ↩

  9. Alibaba Cloud, “Tongyi Qianwen Research License Agreement,” release date 30 November 2023, section 8 (laws of China; “The People’s Courts in Hangzhou City shall have exclusive jurisdiction”), LICENSE file for Qwen1.5-1.8B, Hugging Face, https://huggingface.co/Qwen/Qwen1.5-1.8B/blob/main/LICENSE. ↩

  10. Qwen team, Qwen3-235B-A22B LICENSE (Apache 2.0), https://huggingface.co/Qwen/Qwen3-235B-A22B/raw/main/LICENSE; Qwen3.8-Max LICENSE, https://huggingface.co/Qwen/Qwen3.8-2.4T-A95B/blob/main/LICENSE (custom terms including display and separate-license requirements, with no governing-law or forum clause). These are distinct checkpoint licenses. ↩

  11. DeepSeek, “DeepSeek License Agreement,” Version 1.0, section 14, LICENSE-MODEL in the DeepSeek-V3 repository, GitHub, https://github.com/deepseek-ai/DeepSeek-V3/blob/main/LICENSE-MODEL (the same PRC-law and Hangzhou exclusive-jurisdiction clause as the DeepSeek-LLM license); DeepSeek, MIT License, LICENSE file for DeepSeek-R1, Hugging Face, https://huggingface.co/deepseek-ai/DeepSeek-R1/blob/main/LICENSE; DeepSeek, MIT License, LICENSE file for DeepSeek-V3-0324, Hugging Face, https://huggingface.co/deepseek-ai/DeepSeek-V3-0324/blob/main/LICENSE. All accessed 15 November 2026; license files can change between revisions. ↩

  12. Moonshot AI, “Modified MIT License,” LICENSE file in the Kimi-K2 repository, GitHub, https://github.com/moonshotai/Kimi-K2/blob/main/LICENSE (accessed 15 November 2026; it adds a display requirement for products above 100 million monthly active users or $20 million in monthly revenue and contains no governing-law or forum clause). ↩

  13. Hague Conference on Private International Law (HCCH), “Convention of 30 June 2005 on Choice of Court Agreements,” in force 1 October 2015, https://www.hcch.net/en/instruments/conventions/full-text/?cid=98 (it applies only to exclusive choice-of-court agreements in civil or commercial matters and excludes contracts to which a consumer is a party, Arts. 1(1) and 2(1)(a)); HCCH, “Convention of 2 July 2019 on the Recognition and Enforcement of Foreign Judgments in Civil or Commercial Matters,” in force 1 September 2023, https://www.hcch.net/en/instruments/conventions/full-text/?cid=137; UNCITRAL, “Convention on the Recognition and Enforcement of Foreign Arbitral Awards (New York, 1958),” in force 7 June 1959, https://uncitral.un.org/en/texts/arbitration/conventions/foreign_arbitral_awards. ↩

  14. For one example, OpenAI, “OpenAI Services Agreement,” updated 1 December 2025, effective 1 January 2026, sections 13 (Indemnification) and 15 (Dispute Resolution), with “Venue” defined as the courts of Dublin for customers in the EEA, Switzerland, or the UK and courts in San Francisco County, California for all others, https://openai.com/policies/services-agreement. ↩

From But Is It Open? by Timothy O’Brien (Discursive, 2026). © 2026 Timothy O’Brien. All rights reserved.

Chapter 165 min leftNext →

The book, chapter by chapter.

Source note

Go to the notes & sources ↓

The vocabulary.

A short guide to the book’s recurring terms. Follow each chapter for the argument and its sources.

Open weights
A release makes a trained model’s learned parameters available. The accompanying terms decide what you can do with them. Access to weights alone does not provide the training data, code or recipe. Read the chapter →
Copyleft
A way of using license conditions to preserve recipients’ freedoms when covered software is passed on. The obligations depend on the license and on what you distribute or make available. Read the chapter →
Permissive licenses
Licenses such as MIT and Apache 2.0 grant broad reuse rights with comparatively few conditions. Notice obligations still apply, and a software license does not automatically cover a release’s data or other components. Read the chapter →
Reproducibility
The ability to reconstruct and examine how an artifact was produced using the resources that are published. Running an existing checkpoint is a different achievement from rebuilding its training. Read the chapter →
Governance
Who can participate, who makes decisions, and how authority over a project or release is shared. A right to use the code does not by itself create a voice in upstream decisions. Read the chapter →
Training data
The examples used to train a model. Publishing the data, documenting its provenance and describing how it was filtered are distinct kinds of disclosure; privacy and other rights may limit what can be shared. Read the chapter →

A passage worth sharing.

Select a passage in the chapter, or share the one you’re reading.