Skip to content

chore(licence): de-PMPL — correct proven to MPL-2.0 throughout (38 files)#173

Merged
hyperpolymath merged 1 commit into
mainfrom
claude/proven-depmpl-czncaj
Jun 26, 2026
Merged

chore(licence): de-PMPL — correct proven to MPL-2.0 throughout (38 files)#173
hyperpolymath merged 1 commit into
mainfrom
claude/proven-depmpl-czncaj

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

Owner-directed licence correction (2026-06-26). proven is a sole-owner repo licensed MPL-2.0 (root LICENSE + LICENSES/), but was pervasively mislabelled PMPL-1.0 / Palimpsest-MPL across badges, NOTICE, package manifests, binding READMEs, and two binding LICENSE files. This corrects the repo to MPL-2.0 throughout; docs remain CC-BY-SA-4.0; LICENSES/ holds exactly the texts of licences in use (MPL-2.0 + CC-BY-SA-4.0).

Scope was explicitly confirmed with the owner before sweeping (this is the shape of neurophone#99, but with prior approval this time).

What changed (38 files)

Published package manifestslicense = MPL-2.0 (these set the licence downstream consumers see):
bindings/typescript/package.json, php/composer.json, ruby/proven.gemspec, fsharp/Proven.fsproj, racket/info.rkt, elixir/mix.exs, lua/proven-0.3.0-1.rockspec

Two binding LICENSE files → MPL-2.0 text:
bindings/dart/LICENSE (was a full PMPL "Palimpsest Stewardship Council" text), bindings/r/LICENSE

Docs / metadata → MPL-2.0:
README.adoc badge, NOTICE (rewritten to a plain MPL-2.0 notice), ROADMAP.adoc, MAINTAINERS.adoc, proven-arxiv-paper.tex, domain-specific/tui/src/ui/about.rs (TUI licence label), ~18 binding/domain READMEs (incl. stray "Polymath Public License" / "Palimpsest-MPL" expansions), setup-repo.k9.ncl example

Removed: license/PMPL-1.0.txt (PMPL not in use; the canonical LICENSES/ dir is authoritative; the one README referencing it was updated).

Scope discipline

  • Zero SPDX headers swept — proven had no PMPL SPDX headers; every change was a licence-name string or licence-text file.
  • Left intentionally untouched: contractile.just + .machine_readable/contractiles/Trustfile.a2ml (grep-pattern licence-token lists, i.e. validation logic), and SECURITY-CRITICAL-FIXES-PLAN.md (which documents this PMPL→MPL-2.0 correction).

🤖 Generated with Claude Code


Generated by Claude Code

proven is a sole-owner repo licensed MPL-2.0 (root LICENSE + LICENSES/), but
was pervasively mislabelled PMPL-1.0 / Palimpsest-MPL across badges, the NOTICE,
package manifests, binding READMEs, and two binding LICENSE files. Owner-directed
correction (2026-06-26): repo is MPL-2.0; docs CC-BY-SA-4.0; LICENSES/ holds the
texts of licences actually in use (MPL-2.0 + CC-BY-SA-4.0).

Corrected (38 files):
- README badge, NOTICE (rewritten to plain MPL-2.0), ROADMAP, MAINTAINERS,
  arXiv paper, TUI about-screen label, http/concat/tui domain READMEs
- Published package manifests -> license = MPL-2.0:
  typescript/package.json, php/composer.json, ruby/proven.gemspec,
  fsharp/Proven.fsproj, racket/info.rkt, elixir/mix.exs, lua/*.rockspec
- ~18 binding README licence sections (incl. stray 'Polymath Public License'
  and 'Palimpsest-MPL' expansions) -> MPL-2.0
- bindings/dart/LICENSE (was full PMPL text) + bindings/r/LICENSE -> MPL-2.0 text
- removed stray license/PMPL-1.0.txt (PMPL not in use; LICENSES/ is canonical)

Left untouched (intentional): contractile.just + Trustfile.a2ml grep-pattern
lists (validation logic), SECURITY-CRITICAL-FIXES-PLAN.md (documents this very
correction). No SPDX headers were swept — proven had zero PMPL SPDX headers;
these were licence-name strings.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SuLNP87x3i5YXdq2wYERRK
@hyperpolymath
hyperpolymath marked this pull request as ready for review June 26, 2026 21:26
@hyperpolymath
hyperpolymath merged commit 309afbc into main Jun 26, 2026
19 of 30 checks passed
@hyperpolymath
hyperpolymath deleted the claude/proven-depmpl-czncaj branch June 26, 2026 21:26
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants