-
-
Notifications
You must be signed in to change notification settings - Fork 0
chore(license): migrate PMPL scaffold emissions to MPL-2.0 per owner ruling #106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,14 +2,13 @@ SPDX-License-Identifier: MPL-2.0 | |
|
|
||
| ================================================================================ | ||
| EXHIBIT B — QUANTUM-SAFE PROVENANCE SPECIFICATION | ||
| Palimpsest-MPL License Version 1.0 | ||
| Supplementary to the MPL-2.0 License | ||
| ================================================================================ | ||
|
|
||
| 1. PURPOSE | ||
|
|
||
| This exhibit specifies the cryptographic algorithms and procedures for | ||
| quantum-safe provenance in software distributed under the Palimpsest-MPL | ||
| License. | ||
| quantum-safe provenance in software distributed under the MPL-2.0 License. | ||
|
|
||
| 2. APPROVED ALGORITHMS | ||
|
|
||
|
|
@@ -93,7 +92,7 @@ Palimpsest-MPL License Version 1.0 | |
|
|
||
| 7. COMPLIANCE | ||
|
|
||
| Quantum-safe provenance is OPTIONAL under PMPL-1.0. When present, | ||
| Quantum-safe provenance is OPTIONAL under MPL-2.0. When present, | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win Correct the MPL-2.0 section reference and attribution. The exhibit refers to MPL-2.0 Section 4.1, but MPL-2.0 has no Section 4.1 and does not impose the quantum-safe provenance rule described here. Cite this as project policy or exhibit guidance, and state that it does not modify MPL-2.0. Apply the same correction to the satellite exhibit. 📍 Affects 2 files
🤖 Prompt for AI Agents |
||
| it must follow this specification. Stripping quantum-safe signatures | ||
| from distributions is prohibited per Section 4.1 of the License. | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -62,7 +62,7 @@ trust-verify: trust-license-content trust-no-secrets-committed trust-container-i | |||||
|
|
||||||
| # LICENSE contains expected SPDX identifier | ||||||
| trust-license-content: | ||||||
| grep -q 'SPDX\|License\|MIT\|Apache\|PMPL\|MPL' LICENSE | ||||||
| grep -qiE 'Mozilla Public License|MIT License|Apache License|General Public License|Creative Commons' LICENSE && ! grep -qi palimpsest LICENSE | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win Require MPL-2.0, not any recognised licence. The check accepts MIT, Apache, GPL, and Creative Commons text. A Check the exact SPDX identifier and, preferably, the canonical MPL-2.0 title. Proposed check- grep -qiE 'Mozilla Public License|MIT License|Apache License|General Public License|Creative Commons' LICENSE && ! grep -qi palimpsest LICENSE
+ grep -q '^SPDX-License-Identifier: MPL-2.0$' LICENSE && grep -q '^Mozilla Public License Version 2.0$' LICENSE && ! grep -qi palimpsest LICENSE📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||
|
|
||||||
| # No .env or credential files in repo | ||||||
| trust-no-secrets-committed: | ||||||
|
|
||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,13 +2,13 @@ SPDX-License-Identifier: MPL-2.0 | |
|
|
||
| ================================================================================ | ||
| EXHIBIT A — ETHICAL USE GUIDELINES | ||
| Palimpsest-MPL License Version 1.0 | ||
| Supplementary to the MPL-2.0 License | ||
| ================================================================================ | ||
|
|
||
| 1. PURPOSE | ||
|
|
||
| These guidelines define ethical use expectations for software distributed | ||
| under the Palimpsest-MPL License. They are not legally binding restrictions | ||
| under the MPL-2.0 License. They are not legally binding restrictions | ||
|
Comment on lines
+5
to
+11
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🗄️ Data Integrity & Integration | 🟠 Major | 🏗️ Heavy lift Align both legal exhibits with the repository's documentation licence. The README's
🧰 Tools🪛 LanguageTool[locale-violation] ~5-~5: License must be spelled with a “c” when used as a noun in British English. Use “licence”. (LICENCE_LICENSE_NOUN_SINGULAR) [locale-violation] ~11-~11: License must be spelled with a “c” when used as a noun in British English. Use “licence”. (LICENCE_LICENSE_NOUN_SINGULAR) 📍 Affects 2 files
🤖 Prompt for AI Agents |
||
| but represent the community's shared values and expectations. | ||
|
|
||
| 2. PRINCIPLES | ||
|
|
@@ -55,12 +55,12 @@ Palimpsest-MPL License Version 1.0 | |
| 4. ENFORCEMENT | ||
|
|
||
| These guidelines are enforced through community norms, not legal action. | ||
| Disputes should be raised with the Palimpsest Stewardship Council for | ||
| Disputes should be raised with the project maintainers for | ||
| non-binding guidance. | ||
|
|
||
| 5. AMENDMENTS | ||
|
|
||
| These guidelines may be updated by the Palimpsest Stewardship Council. | ||
| These guidelines may be updated by the project maintainers. | ||
| Updates apply to new distributions, not retroactively. | ||
|
|
||
| ================================================================================ | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Reject stale PMPL identifiers as well as
palimpsest.For example, a
LICENSEfile containing valid MPL text andSPDX-License-Identifier: PMPL-1.0passes this command. The firstgrepmatches, and the negative check does not findpalimpsest. The trust check then accepts a stale PMPL claim.Extend the negative pattern to include
PMPL.Suggested validation change
📝 Committable suggestion
🤖 Prompt for AI Agents