chore(license): align with AtelierOS — CLA §3 relicense + trademark n…#7
Merged
Conversation
…otice
Three artefacts now match the AtelierOS licensing posture documented at
github.com/veegee82/AtelierOS. The Apache-2.0 LICENSE itself is
unchanged (it is already canonical Apache-2.0 with the Copyright 2026
Silvio Jurk appendix).
* NOTICE — adds the trademark-notice block ("AWP" / "Agent Workflow
Protocol" identifiers reserved for the canonical project; forks
renamed remain permitted) and points the third-party-components
section at the reference/ manifests.
* CLA.md (NEW) — v1.0 Contributor License Agreement mirroring the
AtelierOS v3.0 CLA model:
§2 Outbound License (Apache-2.0) — restates Apache § 5 for clarity
§3 Relicense Right — perpetual, non-exclusive grant to relicense
future Contributions under (a) OSI-approved, (b) source-
available (BSL/FSL/Elastic-v2), or (c) commercial terms; past
Apache-2.0 releases stay Apache-2.0 forever, the contributor
keeps Apache-2.0 rights to their own work indefinitely.
§4-§7 representations, warranty disclaimer, sign-by-PR-or-DCO
trailer, German governing law.
* CONTRIBUTING.md — new "License and CLA" + "Trademark" sections
explain the §2/§3 split in plain language, document the
no-bot/PR-is-acceptance sign-off model, and reserve the AWP /
Agent Workflow Protocol name for the canonical project.
Why: keeps the future relicensing option open (hyperscaler-clone
defence, enterprise procurement) without needing to re-coordinate
with past contributors. Same path Sentry, HashiCorp, and MariaDB
MaxScale took. Mirrors AtelierOS exactly so contributors active in
both projects sign once and recognise the pattern.
Signed-off-by: shumway <silvio.jurk@googlemail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…otice
Three artefacts now match the AtelierOS licensing posture documented at github.com/veegee82/AtelierOS. The Apache-2.0 LICENSE itself is unchanged (it is already canonical Apache-2.0 with the Copyright 2026 Silvio Jurk appendix).
NOTICE — adds the trademark-notice block ("AWP" / "Agent Workflow Protocol" identifiers reserved for the canonical project; forks renamed remain permitted) and points the third-party-components section at the reference/ manifests.
CLA.md (NEW) — v1.0 Contributor License Agreement mirroring the AtelierOS v3.0 CLA model: §2 Outbound License (Apache-2.0) — restates Apache § 5 for clarity §3 Relicense Right — perpetual, non-exclusive grant to relicense future Contributions under (a) OSI-approved, (b) source- available (BSL/FSL/Elastic-v2), or (c) commercial terms; past Apache-2.0 releases stay Apache-2.0 forever, the contributor keeps Apache-2.0 rights to their own work indefinitely. §4-§7 representations, warranty disclaimer, sign-by-PR-or-DCO trailer, German governing law.
CONTRIBUTING.md — new "License and CLA" + "Trademark" sections explain the §2/§3 split in plain language, document the no-bot/PR-is-acceptance sign-off model, and reserve the AWP / Agent Workflow Protocol name for the canonical project.
Why: keeps the future relicensing option open (hyperscaler-clone defence, enterprise procurement) without needing to re-coordinate with past contributors. Same path Sentry, HashiCorp, and MariaDB MaxScale took. Mirrors AtelierOS exactly so contributors active in both projects sign once and recognise the pattern.