e8ddfc34a6
Both are MIT, which asks for the permission notice to be included with the software. Tabulator's minified .js carried only "(c) Oliver Folkerd 2025" and its .css carried nothing; Vue's banner names @license MIT but omits the permission text. Each now has its upstream LICENSE vendored verbatim beside it -- fetched, not authored, with the URL and sha256 recorded. ★ AND THE ALLOWLIST IS WHY IT WOULD NOT HAVE WORKED. generate-tree stages vendor/ by an explicit PATH LIST, so the licences sat in data/vendor and never reached the tree: staged count 0. Vendoring a notice the staging step drops is not compliance, it is paperwork. Both LICENSE paths are now listed. documentation/THIRD-PARTY.md is the register the sweep produced: every non-original thing dx-maps ships, its source, its licence, whether the licence or attribution actually travels, and the gap. Compiled by inspecting the SHIPPED tree rather than the source lists, because the question is what a recipient receives. Four rows are left OPEN and marked as such. Two are unverified and need a look (world-adm0's provenance, the pplr upstream). Two need a decision, not a fetch: people-groups and the 304 derived tables carry data whose redistribution terms are not established, 36 MB of it. Attaching a licence I have not confirmed would be worse than the gap, so those go to the Driver. geoBoundaries is closable by work rather than judgment -- CC BY needs attribution, and the .meta.json sidecar pattern already exists here for one file of eight. |
||
|---|---|---|
| .. | ||
| architecture | ||
| assets | ||
| contributing | ||
| needs-eyes | ||
| readme-images | ||
| screenshots | ||
| CLOUD-DEVELOPMENT-ENVIRONMENT.md | ||
| CONTRIBUTING.md | ||
| develop-a-plugin-and-see-it-live.md | ||
| explanation.md | ||
| how-to.md | ||
| HOWTO-join-the-table.md | ||
| PRESET-PLUGIN-STANDARD.md | ||
| README-embed-example.md | ||
| README-embed-gospel-resources.md | ||
| README-SECTION-3-cli-commands.md | ||
| README.md | ||
| reference-capability-exemplars.md | ||
| reference-library-index.md | ||
| reference-universal-props.md | ||
| reference.md | ||
| THIRD-PARTY.md | ||
| tutorial.md | ||
| vendored-font-noto-serif-devanagari.md | ||
| vendored-fonts.md | ||
| why.md | ||
documentation/ — pick your path
"what is this?" "teach me" "how do I …?" "look it up" "all the detail"
│ │ │ │ │
why.md ──────────► tutorial.md ────► how-to.md ────► reference.md ───► architecture/
(2 min, 1 diagram) (first map) (task recipes) (tables) (contracts)
- why.md — the problem and the "map islands" idea. Start here.
- tutorial.md — build your first map, no jargon.
- how-to.md — recipes: embed, iframe, SPA, colors, CDN, mobile, tokens.
- reference.md — config fields, build scripts, the
profile-configcontract. - explanation.md — the model in 15 lines.
- architecture/ — the deep end: full contracts, the per-file catalog.
- README-embed-example.md — the drop-in README used when this bundler is embedded inside a host repo.
- README-embed-gospel-resources.md — the gospel map's URL contract for partner embeds: bring your own ISO 639-3 list, one country, one group, or the zero-access view.
Working on the repo:
- develop-a-plugin-and-see-it-live.md — ★ the golden path: zero to a plugin live, in 6 steps.
- README-SECTION-3-cli-commands.md — every command, per deployment method, with prerequisites.
- reference-capability-exemplars.md — which bundle is at which capability tier (generated).
- reference-library-index.md — the reusable
library/pieces you can import (generated). - CONTRIBUTING.md and contributing/ — how to contribute, and the bar for
library/.
Nothing on the simple path is longer than a few minutes; everything complex lives in
architecture/, linked from where you'd need it.