Skip to content

License hygiene: canonical BSD-3-Clause LICENSE (GitHub-detectable) + NOTICE.md#44

Merged
WebTigers merged 1 commit into
mainfrom
chore/license-bsd3
Jul 22, 2026
Merged

License hygiene: canonical BSD-3-Clause LICENSE (GitHub-detectable) + NOTICE.md#44
WebTigers merged 1 commit into
mainfrom
chore/license-bsd3

Conversation

@WebTigers

Copy link
Copy Markdown
Owner

Why

GitHub's license classifier reported no license for TigerCore even though LICENSE contained BSD-3-Clause text — because the file appended "Heritage & bundled components" and "Trademarks" prose after the standard text, dropping the match confidence below threshold. So the repo sidebar + API said "no license," which reads as all rights reserved and contradicts the open-source topic.

What

  • LICENSE → the canonical BSD-3-Clause template only, so GitHub badges it BSD-3-Clause.
  • NOTICE.md (new) → the preserved heritage note (TigerZF / Zend Framework 1) + bundled third-party components (Bootstrap, GrapesJS, CodeMirror, jQuery, DataTables, Font Awesome, Parsedown).
  • TRADEMARKS.md — unchanged; still holds the trademark policy. LICENSE grants copyright rights only, never the marks.

No code change, no version bump (license/notice files only). Sibling repos (Tiger, TigerDocs) got the same treatment via direct commits.

🤖 Generated with Claude Code

…le) + NOTICE.md

The LICENSE appended "Heritage & bundled components" and "Trademarks" sections
after the BSD-3 text, dropping GitHub's license classifier below its match
threshold — the repo showed "no license" despite the open-source topic and the
SPDX headers throughout the tree.

Make LICENSE the canonical BSD-3-Clause template only (now detectable), and move
the removed heritage/bundled-components note to NOTICE.md. The trademark policy
already lives in TRADEMARKS.md (unchanged); LICENSE grants copyright rights only.

No code change; no version bump.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@WebTigers
WebTigers merged commit 46c5cfa into main Jul 22, 2026
5 checks passed
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.

1 participant