Skip to content

License GitHub community-health workflows as MPL-2.0 (fix reuse lint)#156

Merged
hyperpolymath merged 1 commit into
mainfrom
claude/beautiful-edison-x0o5ke
Jun 21, 2026
Merged

License GitHub community-health workflows as MPL-2.0 (fix reuse lint)#156
hyperpolymath merged 1 commit into
mainfrom
claude/beautiful-edison-x0o5ke

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Jun 21, 2026

Copy link
Copy Markdown
Owner

What

Licenses the three standards-adopted community-health workflow stubshypatia-scan.yml, governance.yml, scorecard.yml — as MPL-2.0 (with the standard two-line SPDX header), removing the bare PMPL-1.0-or-later identifier that was failing reuse lint.

Why

reuse lint was failing, and the first instinct (add a LICENSES/PMPL-1.0-or-later.txt) doesn't work — it's a catch-22:

  • File absent: Missing licenses: PMPL-1.0-or-later
  • File present: Bad licenses … not valid SPDX … do not start with 'LicenseRef-'

PMPL (Palimpsest Meta-Public License) is a custom license, so REUSE only accepts it via a LicenseRef- prefix — a bare PMPL-1.0-or-later can't pass either way. Meanwhile REUSE.toml already aggregates .github/** and **/*.yml as MPL-2.0, so the inline PMPL header just layered an invalid second license on top.

How

Per maintainer direction: these are GitHub community-health files, so license them as MPL-2.0 (the estate's code/config license), keeping MPL-2.0 + CC-BY-SA-4.0 as the repo's two licenses. PMPL is no longer used, so no PMPL text file is needed.

-# SPDX-License-Identifier: PMPL-1.0-or-later
+# SPDX-FileCopyrightText: 2026 Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
+# SPDX-License-Identifier: MPL-2.0

Validation — ran reuse lint locally ✅

* Bad licenses: 0
* Missing licenses: 0
* Unused licenses: 0
* Used licenses: CC-BY-SA-4.0, MPL-2.0
* Files with copyright information: 775 / 775
* Files with license information: 775 / 775
Congratulations! Your project is compliant with version 3.3 of the REUSE Specification :-)

Note

The other two failing checks on this PR — Hypatia scan and governance staleness — are unrelated: they come from stale hyperpolymath/standards reusable-workflow pins (the actions/cache@d4373f26 pin was fixed to 1bd1e32a # v4.2.0 on standards@main) and need an estate-standardization re-sync in standards, which is outside these repos.

🤖 Generated with Claude Code

https://claude.ai/code/session_017nyxs8RgqZa72PzrTu3L75

The reuse-lint check failed because the three standards-adopted
community-health workflow stubs (hypatia-scan.yml, governance.yml,
scorecard.yml) declared a bare `SPDX-License-Identifier: PMPL-1.0-or-later`.
PMPL is a custom license, so REUSE rejects the bare identifier (custom
licenses must use a `LicenseRef-` prefix); and REUSE.toml already aggregates
`.github/**` + `**/*.yml` as MPL-2.0 on top, leaving PMPL "used" but invalid.

Per maintainer direction, license the GitHub community-health files as
MPL-2.0 (the estate's code/config license) with the standard two-line SPDX
header, keeping MPL-2.0 + CC-BY-SA-4.0 as the repo's two licenses. PMPL is no
longer used, so no PMPL license text file is required.

Verified locally with `reuse lint`: compliant with REUSE 3.3
(Used licenses: CC-BY-SA-4.0, MPL-2.0; 0 bad / 0 missing / 0 unused;
775/775 files covered).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017nyxs8RgqZa72PzrTu3L75
@hyperpolymath
hyperpolymath force-pushed the claude/beautiful-edison-x0o5ke branch from 5d46a98 to 6417580 Compare June 21, 2026 16:44
@hyperpolymath hyperpolymath changed the title Add missing PMPL-1.0-or-later license text (fix reuse lint) License GitHub community-health workflows as MPL-2.0 (fix reuse lint) Jun 21, 2026
@hyperpolymath
hyperpolymath marked this pull request as ready for review June 21, 2026 16:45
@hyperpolymath
hyperpolymath merged commit 174d8e7 into main Jun 21, 2026
31 of 33 checks passed
@hyperpolymath
hyperpolymath deleted the claude/beautiful-edison-x0o5ke branch June 21, 2026 16:46
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