Skip to content

fix: align composer.json license with LICENSE (MPL-2.0)#443

Merged
tuj merged 1 commit into
release/3.0.0from
feature/composer-license
May 8, 2026
Merged

fix: align composer.json license with LICENSE (MPL-2.0)#443
tuj merged 1 commit into
release/3.0.0from
feature/composer-license

Conversation

@turegjorup
Copy link
Copy Markdown
Contributor

Summary

  • Sets composer.json license to MPL-2.0, matching the LICENSE file shipped at the repo root. Was incorrectly proprietary — wrong for a public open-source project and contradicting the bundled license terms.
  • Adds two related project-meta fields that the previous file was missing: homepage (canonical repo URL) and support.issues / support.source (issue tracker + source URL). Used by composer support, GitHub's dependency graph, SBOM generators, and Packagist.

Other meta — left to your call

These are also missing but I held off because they need input rather than a clear-cut fix. Worth a follow-up commit on this branch (or a separate PR) if you'd like:

  • authors — array of { name, email } for credited contributors. ITK Dev / OS2Display org? Specific maintainers?
  • keywords — searchable tags. Optional for type: project projects; useful if this ever ends up on Packagist.
  • description — currently "Api backend for OS2display". The repo now houses the full project (admin + client + templates per UPGRADE.md), so something like "OS2Display" or "OS2Display digital signage platform" would be more accurate. I left it alone to keep the PR scope minimal.

Happy to push any of these once you decide.

Test plan

  • composer validate --strict → green
  • composer normalize --dry-run → already normalised

🤖 Generated with Claude Code

…age/support

The repository ships under the Mozilla Public License 2.0 (see `LICENSE`)
but `composer.json` still declared `proprietary` — wrong for a published
open-source project and contradicts the bundled license file. Switching to
the SPDX identifier `MPL-2.0` aligns the package metadata with reality.

Also fills in two adjacent fields that downstream tooling (Composer,
Packagist, GitHub dependency graph, SBOM generators) expects on a public
project:
  - `homepage` — points at the canonical repo
  - `support.issues` / `support.source` — the GitHub issue tracker and
    source URL, used by `composer support` and surfaced in dependency
    listings

`authors` and `keywords` are intentionally left out — both want input on
who/what to list and were not the immediate gap.

Verified with `composer validate --strict` (green) and `composer normalize
--dry-run` (already normalised).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@turegjorup turegjorup requested a review from tuj May 6, 2026 23:01
@turegjorup turegjorup self-assigned this May 6, 2026
@tuj tuj merged commit 55b900f into release/3.0.0 May 8, 2026
18 of 19 checks passed
@tuj tuj deleted the feature/composer-license branch May 8, 2026 11:39
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.

2 participants