docs(license): split the data carve-out into NOTICE

The carve-out was 180 words appended to LICENSE, which pushes the file below
the similarity threshold licence detectors match against — a repository whose
licence reads "other" is less inviting to a forker than one that reads MIT,
and the carve-out was never part of MIT's text anyway.

LICENSE is verbatim MIT again, plus three lines binding NOTICE into the terms
so the carve-out travels with any copy rather than being optional reading.
NOTICE carries the substance. README points at both.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
This commit is contained in:
Lucas Winther
2026-08-17 22:33:29 +02:00
co-authored by Claude Opus 5
parent 50fb7b8efb
commit 8d4a28b254
3 changed files with 40 additions and 23 deletions
+2 -2
View File
@@ -274,8 +274,8 @@ scripts.
It does not cover the event data. The schedules under `fixtures/` and `snapshots/`, and the feed
built from them, were compiled by the editors of the sites they came from and describe events run by
the publishers; every event links back to the page it came from. Fork the code freely — the data you
obtain and attribute yourself. The scope note at the foot of `LICENSE` spells this out, and the app's
own colophon says the same thing to readers.
obtain and attribute yourself. [NOTICE](NOTICE) spells this out and travels with the licence, and the
app's own colophon says the same thing to readers.
Unofficial and unaffiliated. Game names, event names and trademarks belong to their respective
owners.