French court issues damages award for violation of GPL

French legal process and long timeline

• Case went through first instance, appeal, Cour de cassation, then a different appeals court, leading to ~14 years from suit to final judgment.
• Cassation doesn’t decide the facts; it checks legal/procedural correctness, then remands, so much of the case had to be re‑done under clarified legal doctrine.
• Commenters note French courts are chronically slow and overloaded; multi‑year or decade‑long civil and criminal cases are common.

What Orange did and how it was litigated

• Orange used the GPL‑licensed Lasso library in an identity provider module for a French government service, modified it, and didn’t comply with GPL obligations (e.g., source release).
• There was an initial attempt at mediation, then a court‑appointed expert to assess whether linking in an Apache module violated GPLv2.
• First instance was a loss for the plaintiff; first appeal reframed it as “parasitism” (unfair competition) rather than copyright/GPL.
• Cassation broke with a prior French doctrine barring simultaneous contractual and tort (copyright) liability, allowing a true copyright/GPL claim on remand.

Damages, scale, and costs

• Reported final award is on the order of €650–860k plus some legal costs; the plaintiff says they spent ~€100k over 14 years and got less back than they spent.
• Some dispute the numbers because the plaintiff had originally requested ~€4.1M; the dispositive section of the judgment appears to award significantly less.
• Many see the sum as small for a large telco and, spread over ~7–14 years of infringement, not a strong deterrent; others stress that the existence of any enforceable judgment is the real win.
• In France, the losing party typically pays a court‑set contribution to the winner’s expenses (article 700), often below actual cost.

Precedent in a civil‑law system

• France is civil law, so precedent is not formally binding, but higher‑court decisions are still widely followed and shape doctrine.
• Commenters expect this ruling to clarify that GPL terms are enforceable as copyright conditions in France and likely influence future EU cases, even if not strictly binding.

Enforcement and collection

• Once a “titre exécutoire” (enforceable title) exists, a judicial officer can seize funds or assets directly from a company like Orange; non‑payment is considered unlikely in practice.

GPL, linking, and license‑choice debates

• Long subthreads debate what counts as a “derivative work” or “linking” for GPL in practice (static vs dynamic linking, plugins, Python imports, process boundaries, SaaS, AGPL).
• Many corporate contributors prefer clearer, permissive licenses (e.g., Apache 2.0, MIT) because GPL’s boundaries and enforcement risk are viewed as legally murky and costly.
• Others argue the ambiguity is overstated, that copyleft is necessary to protect user freedoms and prevent one‑way corporate exploitation of community code.
• There is discussion of dual licensing (commercial + GPL), and how a known commercial price made it easier here to quantify damages.

LLMs and GPL erosion concerns

• Several commenters worry that training large language models on public repositories (including GPL/AGPL code) and then emitting similar code without attribution effectively “launders” licenses and undermines copyleft.
• Others respond that existing copyright rules still apply: humans distributing infringing output remain liable, and courts have yet to definitively classify LLM training and outputs.
• There is mention of ongoing litigation (e.g., around GitHub Copilot) but no resolution cited in the thread.

Messaging: “free software” vs “open source”

• Some criticize the term “free software” as persistently confusing in English (price vs freedom), suggesting “libre”, “freedom software”, or explicit license names instead.
• French terminology (“logiciel libre” vs “logiciel gratuit”) avoids this ambiguity, which is relevant since the case is in France.