Skip to content

Relicense from MIT to Apache-2.0 + add CLA#1

Merged
zuchka merged 2 commits into
mainfrom
relicense-apache-2.0
May 2, 2026
Merged

Relicense from MIT to Apache-2.0 + add CLA#1
zuchka merged 2 commits into
mainfrom
relicense-apache-2.0

Conversation

@zuchka

@zuchka zuchka commented May 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

Aligns ding-action with the broader project relicense (see ding-labs/ding#5 and ding-labs/ding-k8s-job#1).

  • Relicense from MIT to Apache-2.0 (canonical text from apache.org).
  • Add NOTICE file per Apache convention.
  • Update README license section.
  • Add an Apache-ICLA-style CLA at .github/CLA.md and CLA Assistant Lite workflow at .github/workflows/cla.yml.

Why MIT → Apache instead of staying MIT

The other repos in the project moved AGPL → Apache, and the README in this repo currently says "MIT — same as DING" — a line that goes stale the moment those PRs land. Two options were on the table:

  1. Keep MIT, just add CLA + URL cleanup.
  2. Move to Apache 2.0 for cross-repo consistency.

Going with #2 because (a) it eliminates the "MIT — same as DING" lie, (b) Apache 2.0 adds an explicit patent grant that MIT lacks, which is strictly more protective for downstream users with no real downside, and (c) one license across the project simplifies legal/marketing/compliance.

If this assumption was wrong and you'd rather keep ding-action on MIT, this PR is straightforward to revert and reduce to just the CLA.

Contributor consent

git log --all --format='%an <%ae>' | sort -u confirms every commit is by the sole maintainer. No third-party consent required.

CLA design notes

  • Modeled on the Apache ICLA v2.0, identical legal substance to the CLAs in ding-labs/ding and ding-labs/ding-k8s-job. Only the introduction is adapted to name ding-action.
  • Sublicense grant in §2 preserves future relicensing flexibility.
  • CLA Assistant Lite runs as a GitHub Action only — no external service. Signatures live in a cla-signatures branch.

Test plan

  • Confirm Apache 2.0 LICENSE matches https://www.apache.org/licenses/LICENSE-2.0.txt exactly.
  • Read through .github/CLA.md and confirm legal posture matches intent.
  • After merge: open a test PR from a non-allowlisted account to confirm the CLA bot prompts for signature.

Follow-up

A separate PR will clean up stale zuchka/ URLs in README.md, action.yml, and examples/*.yml (this is functional, not just cosmetic — action.yml calls api.github.com/repos/zuchka/ding/releases/latest which currently relies on GitHub redirecting to ding-labs/ding).

🤖 Generated with Claude Code

zuchka and others added 2 commits May 1, 2026 18:06
Replace MIT LICENSE with canonical Apache 2.0 text and add NOTICE
file per Apache convention. Update README license section.

Aligns with the parallel relicense in ding-labs/ding (PR #5) and
ding-labs/ding-k8s-job (PR #1). Apache-2.0 across the project gives a
consistent license story; Apache 2.0 also adds an explicit patent grant
that MIT lacks, which is strictly more protective for downstream users.

All commits to date are by the sole maintainer, so no third-party
contributor consent is required for the relicense.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Add an Apache-ICLA-style Contributor License Agreement and CLA Assistant
Lite workflow, mirroring the setup in ding-labs/ding and
ding-labs/ding-k8s-job.

The CLA grants a copyright license that includes the right to
sublicense, preserving the ability to relicense or dual-license the
project in the future without chasing down past contributors. The
project name in the document is adapted for ding-action; the
substantive legal terms are identical to the other repo CLAs.

CLA Assistant Lite runs entirely as a GitHub Action with no external
service. Signatures are stored in a "cla-signatures" branch in this
repo. The maintainer (zuchka) and bots are allowlisted.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@zuchka zuchka merged commit 9d2a477 into main May 2, 2026
@github-actions github-actions Bot locked and limited conversation to collaborators May 2, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant