Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions CONTRIBUTOR_LICENSE_TRANSITION_v2.0_DRAFT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# Contributor-retained-rights transition — DRAFT, 19 November 2026

**Not in force. Do not activate or advertise ICLA v2.0 as binding before legal review and formal approval.**

## Why

The operative ICLA v1.1 and Corporate Contributor Agreement assign transferable economic rights in accepted contributions to Botshare LTD. The proposed v2.0 model instead preserves contributor ownership while granting Botshare LTD broad non-exclusive, perpetual, irrevocable, worldwide, royalty-free, transferable, sublicensable and commercial exploitation rights. This is a material legal change, not a word change.

## Release checklist

1. Engage Cyprus-qualified intellectual-property counsel to assess draft ICLA v2.0, corporate equivalents, patent rights, authorship/moral-right limitations, data protection, and past assignment chains.
2. Decide whether corporate contributors will have a separately updated **Corporate Contributor License Agreement v2.0**; the operative corporate agreement remains assignment-based until an approved replacement is signed. Do not route corporate-owned work through the individual agreement.
3. Confirm any background material and upstream-rights exceptions with contributors before acceptance. Do not automatically relicense Apache-2.0 or other third-party source to MIT.
4. Approve final legal text, assign immutable document version and preferably a digest, and publish it alongside archived ICLA v1.1. Keep historical agreement records.
5. Configure CLA Assistant's **actual organization-wide acceptance document** to the exact approved v2.0, verify the linked URL and version in a test PR, and **require new affirmative acceptance for contributors whose new work is covered by v2.0**. A Markdown PR alone does not configure the external service.
6. Keep DCO, provenance, third-party notice and CODEOWNERS requirements. Update CLA.md, IP_POLICY.md, DCO.md, CONTRIBUTING.md, corporate agreement references, reviewer instructions and automated check expectations **in one reviewed transition**.
7. Avoid a transition window where an ambiguous CLA status permits an unlicensed contribution. Verify that historical v1.1 acceptances do not masquerade as acceptance of v2.0.
8. Test one individual PR and one corporate-authorized PR through the end-to-end CLA and DCO workflow before activating across repositories.
9. Communicate to all contributors: contributors retain copyright ownership under **new v2.0**; Botshare holds a permanent broad non-exclusive licence; existing assigned contributions under v1.1 remain assigned absent separately executed reassignment/licensing arrangements.
10. Record formal approval and effective date. Review all pending PRs for which agreement was accepted before transition and identify their controlling version individually.

## Manas / OpenArm example

For Manas's contribution to upperbody-sw #69, clarify that his pre-existing `openarm-control` Apache-2.0 Background Material is separately owned; any copies or derivative components must be identified file-by-file with provenance before acceptance. Do not insist that independent Apache-2.0 code is MIT simply because a contributor has signed a CLA. If v2.0 is approved in time, Manas must affirmatively accept it before the applicable contributions are merged. Until then, v1.1 remains the operative agreement, and the contributor should not be pressured to sign a contract they do not understand or accept.

## Scope limitation

This proposal does **not** change the project's outbound asset licensing rules: MIT original software/firmware, CERN-OHL-P-2.0 original hardware, CC BY 4.0 original documentation/content, explicit asset-specific dataset/model terms. Third-party and derivative assets retain applicable upstream requirements. Existing public licences are not revoked.
83 changes: 83 additions & 0 deletions CORPORATE_CONTRIBUTOR_LICENSE_AGREEMENT_v2.0_DRAFT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,83 @@
# OpenAMRobot Corporate Contributor License Agreement — v2.0 DRAFT

**Status: proposal only — NOT IN FORCE. Legal review and authorized signatures required.**
**Proposed version:** 2.0, 19 November 2026. The current Corporate Contributor Agreement v1.1 remains operative until this agreement is legally approved and duly executed.

This proposed agreement is between **Botshare LTD**, Company ID HE479056, Limassol, Cyprus (“Company”) and the signatory legal entity (“Contributor Organization”).

## 1. Definitions and authorization

“Authorized Contributor” means an individual identified in writing by Contributor Organization, with their attributable GitHub account, who is authorized to submit eligible contributions. “Contribution” includes source and object code, firmware, CAD, drawings, hardware designs, schematics, documentation, tests, datasets, AI models, media and other protectable material intentionally submitted for OpenAMRobot. “Accepted Contribution” means one merged by an authorized maintainer or expressly accepted in writing by Company.

This Agreement covers rights Contributor Organization owns or lawfully controls. Contributor Organization provides and maintains the Authorized Contributors list, notifies Company of changes, and obtains all employment, contractor, institutional, co-author and inventor permissions needed for the licences granted here. It shall not purport to license rights belonging to individuals or third parties it does not control.

## 2. Ownership retained; irrevocable, broad commercial licence

**Contributor Organization retains ownership of all intellectual property rights it holds in its Contributions. No transfer or assignment of ownership to Company occurs under this Agreement.** Its Authorized Contributors retain any non-transferable rights and authorship as provided by law. Contributor Organization remains free to independently use, modify, distribute, license and commercially exploit its own contributions, subject to existing third-party rights.

For each Accepted Contribution, Contributor Organization grants Company a **non-exclusive, worldwide, perpetual, irrevocable, fully paid, royalty-free, transferable and sublicensable licence** under all copyright, database, design and related rights it can lawfully license, to reproduce, modify, adapt, translate, combine, distribute, publish, communicate, display, perform, create derivative works, make, have made, use, sell, offer for sale, import, maintain, commercialize, license, sublicense and otherwise exploit that Accepted Contribution **for any purpose**, including open-source and proprietary products and services. These permissions cover Company affiliates, contractors, clients, customers, distributors, licensees, successors and acquirers by transfer or sublicense.

The licence survives Contributor Organization's departure, changes to Authorized Contributors, and termination of this Agreement, subject to mandatory law and third-party obligations. Company receives no title to the Contributor Organization's intellectual property merely through acceptance.

## 3. Outbound licence consistency

Contributor Organization authorizes publication of original Accepted Contributions under the project's published asset-specific licences: MIT for software/firmware; CERN-OHL-P-2.0 for original hardware design sources; CC BY 4.0 for original documentation/content; and express asset-specific terms for datasets/AI models. Trademarks and brand assets require separate permissions.

Company may sublicense, dual-license or commercially distribute relevant rights under other terms, including proprietary terms, only to the extent Contributor Organization's grant and valid upstream rights allow. No third-party material is automatically relicensed. Original contributions must not carry contributor-added restrictions incompatible with the intended outbound terms without explicit acceptance by Company.

## 4. Background and third-party material

Contributor Organization retains ownership of correctly disclosed pre-existing Background Material. Each PR must identify included or required Background Material and all third-party material with source, rights holder, exact version, licence, notices, modifications and limitations.

For Contributor Organization-owned Background Material necessarily included in an Accepted Contribution, Contributor Organization grants Company and downstream recipients a non-exclusive, perpetual, irrevocable, worldwide, royalty-free licence sufficient to use, modify, distribute and exploit that material in connection with the Accepted Contribution, solely to the extent lawfully licensed. It remains owned by Contributor Organization.

Incompatible, unlicensed, confidential or unauthorised third-party content must not be included. Existing upstream notices and licence requirements remain in force. Company can reject or require removal of material that cannot satisfy the intended licence or provenance standard.

## 5. Patent rights

Contributor Organization retains its patents and inventions. It grants Company and recipients of each Accepted Contribution a worldwide, perpetual, non-exclusive, irrevocable except on defensive termination, royalty-free, transferable, sublicensable licence to make, have made, use, sell, offer for sale, import and otherwise exploit that Accepted Contribution under patent claims it may lawfully license that are necessarily infringed by the Accepted Contribution as submitted alone or in its submitted combination with OpenAMRobot. Unrelated later combinations and unrelated claims are excluded.

The patent licence may terminate for a recipient that initiates patent litigation alleging that the Accepted Contribution or OpenAMRobot infringes the recipient's patents, except defensive counterclaims and subject to mandatory law. Ownership of patents and inventions is not assigned.

## 6. Authors, inventors and moral rights

The authors and inventors remain identified as required by law. Company will retain reasonable attribution through Git history or equivalent records and preserve mandatory notices. Contributor Organization will obtain from Authorized Contributors consents to modification, combination, adaptation, commercialization, release or withdrawal of Accepted Contributions necessary to exercise this Agreement, as legally permitted. This is not a blanket copyright assignment or waiver of legally non-waivable authorship. Company may not knowingly falsely attribute authorship.

## 7. Representations and compliance

Contributor Organization represents that it: has authority to execute this Agreement; controls sufficient rights to grant the licences; has necessary individual, employer, client, university, sponsor and co-author authorizations; discloses third-party, Background and materially AI-assisted content; submits no unauthorized confidential or personal information, trade secrets or credentials; complies with asset-specific licensing, DCO, provenance and security policies; and will notify Company promptly if these representations become inaccurate.

Every Authorized Contributor must use their own attributable GitHub identity and sign every commit under the DCO. A valid DCO does not assign IP or substitute for this Agreement. A passing automated check cannot resolve missing corporate or third-party authority.

## 8. Records and changes

Company may record authorized contributors, agreement version, dates, signed authorization, PRs, commit hashes and acceptance decisions. Signed agreements and identity documents are not published in source repositories. Material amendments require execution/acceptance of a newly identified version; publication of updated Markdown is insufficient. Existing Corporate Contributor Agreement v1.1 assignments are not retroactively reversed.

## 9. No obligation, remuneration or partnership

Company need not accept or use any Contribution or pay remuneration absent a separate written agreement. The parties do not enter employment, agency, partnership, joint venture or a governance arrangement. Neither party waives liabilities that mandatory law prohibits excluding.

## 10. Term, disputes and signatures

Either party may terminate prospectively by written notice. Licences granted on previously Accepted Contributions survive termination. Cyprus law governs, subject to mandatory protections; Cyprus courts have jurisdiction except where mandatory jurisdiction applies. If a term is invalid, the balance remains enforceable where possible.

**Contributor Organization**
Legal name: ____________________
Registration number: ____________________
Registered address and country: ____________________
Authorized signatory and title: ____________________
Email: ____________________
Signature and date: ____________________

**Authorized Contributors (initial list)**
| Full legal name | GitHub username | Authorization basis |
|---|---|---|
| | | |

**Botshare LTD**
Authorized representative and title: ____________________
Signature and date: ____________________

---

**Legal review note:** Draft only. Seek Cyprus-qualified IP advice on corporate copyright title, employee invention compensation, sublicensing/assignment, moral rights, patents, applicable institutional obligations, and electronic execution before activation.
Loading