Skip to content

chore(licence): normalise to MPL-2.0 (code) + CC-BY-SA-4.0 (docs) - #38

Merged
hyperpolymath merged 2 commits into
mainfrom
chore/licence-normalisation-2026-06-24
Aug 25, 2026
Merged

chore(licence): normalise to MPL-2.0 (code) + CC-BY-SA-4.0 (docs)#38
hyperpolymath merged 2 commits into
mainfrom
chore/licence-normalisation-2026-06-24

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner
  • LICENSES/ = {MPL-2.0.txt, CC-BY-SA-4.0.txt}; root LICENSE = verbatim MPL-2.0 (GitHub display)
  • SPDX: code -> MPL-2.0, docs (.md/.adoc) -> CC-BY-SA-4.0; metadata/badge fixes; vendored untouched

Summary

Closes #

Type of change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (would change existing behaviour)
  • 🕳️ Soundness fix (fixes a checker/proof false-negative)
  • 📖 Documentation
  • 🧹 Refactor / tech debt (behaviour-preserving)
  • ⚡ Performance
  • 🔧 Build / CI / tooling

How has this been verified?

Checklist

  • My commits are signed (git commit -S).
  • I ran the project's own checks/tests locally and they pass.
  • New files carry the correct SPDX-License-Identifier (code/config MPL-2.0,
    prose CC-BY-SA-4.0); I did not relicense existing files.
  • Docs are updated, and no public claim now overstates what the code does.
  • I have not introduced a soundness hole (or I have flagged where I might have).

Notes for reviewers

- LICENSES/ = {MPL-2.0.txt, CC-BY-SA-4.0.txt}; root LICENSE = verbatim MPL-2.0 (GitHub display)
- SPDX: code -> MPL-2.0, docs (.md/.adoc) -> CC-BY-SA-4.0; metadata/badge fixes; vendored untouched

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@gitar-bot

gitar-bot Bot commented Aug 24, 2026

Copy link
Copy Markdown

Important

You are using the Gitar free plan. Upgrade to unlock code review, CI analysis, auto-apply, custom automations, and more.

Gitar

@hyperpolymath
hyperpolymath enabled auto-merge (squash) August 24, 2026 22:42
Resolves 11 conflicts. The branch dates from 2026-06-24; main has since
renamed the docs to AsciiDoc and removed all ReScript, so most conflicts
were the branch editing files that no longer exist.

Resolution, by class:

  * 4x modify/delete on .md (CHANGELOG, CODE_OF_CONDUCT, SECURITY,
    docs/tech-debt-2026-05-26) -- main renamed each to .adoc. Accepted
    main's deletion, and PORTED THIS PR'S PURPOSE onto the surviving
    .adoc files, which carried no SPDX header. Deleting alone would have
    discarded the licence normalisation this PR exists to do.

  * 4x modify/delete on .res (Deno x2, Resilience, bindings/Deno) --
    main deleted all ReScript; the repo now has zero .res files, and
    ReScript is banned by LANGUAGE-POLICY.adoc S3 (uncontested).
    Accepted main's deletion; the branch was only adding licence
    headers to files that should not exist.

  * 2x add/add on LICENSES/*.txt -- differences were trailing whitespace
    and http:// vs https://. Took main's canonical text verbatim rather
    than hand-mixing; a licence text is taken whole from one side, never
    merged hunk by hunk.

  * 1x content conflict on CONTRIBUTING.adoc -- kept the branch's SPDX
    header and `= Contributing Guide` document title, then main's
    content. Main's version began with `== Clone the repository`, a
    section header with no document title, which is malformed AsciiDoc.

SPDX headers follow the repo's existing AsciiDoc convention (`//` line
comments), matched from README.adoc / MAINTAINERS.adoc / ROADMAP.adoc.

Verified: zero unresolved paths; no conflict markers anywhere in the
tree; both LICENSES byte-identical to main; no deleted path still
present on main.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath disabled auto-merge August 25, 2026 16:30
@hyperpolymath
hyperpolymath merged commit 247ed68 into main Aug 25, 2026
10 of 11 checks passed
@hyperpolymath
hyperpolymath deleted the chore/licence-normalisation-2026-06-24 branch August 25, 2026 16:30
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.

1 participant