CIP-9999 | Add mandatory Copyright + related cleanup

[rphair]

Fixes #759.

In addition to mimicking the CIP licensing requirements for the CPS, this removes static LICENSE files from the CIPs that still had them in spite of the fact that linking the license in the document footer is (and is preferred to be) sufficient for license binding. (It also fixes that license link in one case that I missed in #389 "Remediation")

It might be less work to do the CPS license updates as part of this PR, but I think not because:

• some CPS authors will want to consider CC vs. Apache, and others might by default leave that choice to editors
• we could want to coordinate this with parsers for the Dev Portal and cips.cardano.org since currently undefined YAML header data might trigger warnings / errors / inappropriate formatting. cc @KtorZ @katomm

[Ryun1]

Do we want to add a License field to the CPS header?

[rphair]

@Ryun1 you've spotted an interesting problem which I guess had always been a bother & didn't articulate till now. All along, the CIP has had License in the CIP header but has a Copyright section in the document. I believe this is proper... but I reflected the duplicate term when calling it Copyright in the description of the front matter data. I'll fix that now... plus the pending updates to the CPS template which I still haven't committed.

[rphair]

... or maybe you mean this CPS header. That was actually one of the things I said should be delayed in the OP, if so... it would be bad if this file itself got omitted on the derived sites due to syntax errors. In any case will double-check all this stuff & update in next few minutes.

[rphair]

OK @Ryun1 TL;DR last 2 comments: oversight you pointed out is fixed in ed51527

[Crypto2099]

Looks good

[Ryun1]

I meant, do we want to edit the CPS yaml header to have a License to match the CIPs yaml header?

[rphair]

yes & thanks @Ryun1 ... currently it's the same:

https://github.com/rphair/CIPs/blob/9463c113323ef0bebf55b5310bca2cc2cba17935/CIP-0001/README.md#header-preamble

License Abbreviation of an approved license(s)

https://github.com/rphair/CIPs/blob/9463c113323ef0bebf55b5310bca2cc2cba17935/CIP-9999/README.md#header-preamble

License Abbreviation of an approved license(s)

[Ryun1]

ahh sorry! I meant also in the template file

[rphair]

@Ryun1 likewise they are also currently the same in the last section (except for CIP vs CPS):

• https://raw.githubusercontent.com/rphair/CIPs/9463c113323ef0bebf55b5310bca2cc2cba17935/.github/CIP-TEMPLATE.md
• https://raw.githubusercontent.com/rphair/CIPs/9463c113323ef0bebf55b5310bca2cc2cba17935/.github/CPS-TEMPLATE.md

[Ryun1]

Wait, am I being silly?
I cant see the License in the CPS yaml header. I can see it in the document sections but not the header.

so the header would be:

---
CPS: ?
Title: ?
Status: Open
Category: ?
Authors:
    - John Doe <[email protected]>
Proposed Solutions: []
Discussions:
    - https://github.com/cardano-foundation/CIPs/pull/?
Created: YYYY-MM-DD
License: CC-BY-4.0
---

[rphair]

@Ryun1 you are not being silly but the purpose of this PR (posted in #762 (comment)) is deliberately not to modify any CPS headers for [my own] worry that it will break downstream tooling & could well require some coordination beyond the editorial "rules" set in this PR:

It might be less work to do the CPS license updates as part of this PR, but I think not because ... we could want to coordinate this with parsers for the Dev Portal and cips.cardano.org since currently undefined YAML header data might trigger warnings / errors / inappropriate formatting.

p.s. edit: and now I am being silly since I confused the document structure in the CPS with the sample in the Template file. So here I go again with one more commit & thanks again @Ryun1 for the double check 🤓

[rphair]

License: CC-BY-4.0

OK @Ryun1 - done and done in ee096be I hope 😅