Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
6bd4b68
legal: contributor agreement v2.0 transition note
BotshareAI Nov 22, 2026
7617ecf
legal: align DCO note with contributor agreement v2.0
BotshareAI Nov 22, 2026
2d558ac
legal: align NOTICE with contributor agreement v2.0
BotshareAI Nov 22, 2026
363fe26
legal: align organization profile with contributor agreement v2.0
BotshareAI Nov 22, 2026
e638d92
legal: align LICENSING with contributor agreement v2.0
BotshareAI Nov 22, 2026
2a61c98
legal: align GOVERNANCE with contributor agreement v2.0
BotshareAI Nov 22, 2026
d9bb38f
legal: align README with contributor agreement v2.0
BotshareAI Nov 22, 2026
7de8564
legal: define material AI assistance and its disclosure
BotshareAI Nov 22, 2026
4aa660e
legal: record agreement version, coverage start and guardian consent
BotshareAI Nov 22, 2026
18680dc
legal: add licence-compatibility and asset-card items to the PR template
BotshareAI Nov 22, 2026
679b53e
legal: privacy notice 1.1 (CLA Assistant, acceptance fields, guardian…
BotshareAI Nov 22, 2026
2eca89f
legal: align CONTRIBUTING with contributor agreement v2.0
BotshareAI Nov 22, 2026
63c6e25
state: record contributor agreement 2.0 work
BotshareAI Nov 22, 2026
75796c3
legal: align IP policy with contributor agreement v2.0
BotshareAI Nov 22, 2026
0f9f0cd
legal: commercial compatibility classes, asset cards and background m…
BotshareAI Nov 22, 2026
7fb9fcc
legal: version-aware contributor agreement process and v2.0 activatio…
BotshareAI Nov 22, 2026
f4ad6b0
legal: guardian consent form for contributors under 18
BotshareAI Nov 22, 2026
a452126
legal: corporate contributor license agreement v2.0
BotshareAI Nov 22, 2026
0097fca
legal: individual contributor license agreement v2.0
BotshareAI Nov 22, 2026
9010d86
state: point the contributor agreement row at PR 95
BotshareAI Nov 22, 2026
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
3 changes: 2 additions & 1 deletion .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,7 @@ platform lead. Telemetry and fixtures are not safety evidence. -->

- [ ] Every commit is signed off under the [DCO](https://github.com/openAMRobot/.github/blob/main/DCO.md).
- [ ] I am covered by an accepted [Contributor Agreement](https://github.com/openAMRobot/.github/blob/main/CLA.md).
- [ ] Third-party material is identified with source and licence.
- [ ] Third-party and background material is identified with source and licence, and nothing included or required is under non-commercial, copyleft or other restricted terms ([policy](https://github.com/openAMRobot/.github/blob/main/THIRD_PARTY_POLICY.md)).
- [ ] Any dataset, simulation asset, model or weights comes with its provenance card.
- [ ] No confidential, personal, credential or export-controlled information is included.
- [ ] No partner, customer or private person is named; the application is Use_Case_1.
3 changes: 2 additions & 1 deletion AI_CONTRIBUTION_POLICY.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,8 @@ AI tools may assist OpenAMRobot work, but the human contributor remains responsi

A contributor must:

- disclose material generative-AI assistance in the pull request;
- disclose material generative-AI assistance in the pull request description: which parts, which tool, and that the contributor reviewed and tested them. Assistance is material when a tool generated a substantial part of the code, text, design or data; autocomplete, spelling and formatting aids are not. Per-commit tool trailers are not required;
- confirm that the tool's terms allow the output to be submitted and licensed under the contributor agreement;
- review output for correctness, safety, security, licence compatibility, provenance, and substantial similarity;
- confirm authority to submit all prompts, inputs, references, and outputs;
- avoid entering confidential information, personal data, credentials, client material, unpublished inventions, or restricted source into an AI service;
Expand Down
82 changes: 60 additions & 22 deletions CLA.md
Original file line number Diff line number Diff line change
@@ -1,54 +1,92 @@
# OpenAMRobot Contributor Agreement Process

Botshare LTD requires an accepted contributor agreement before accepting an external contribution.
Botshare LTD requires a recorded contributor agreement before accepting an external contribution.

## Applicable agreement
## Agreement versions

- Use the [Individual Contributor Agreement](INDIVIDUAL_CONTRIBUTOR_AGREEMENT.md) when contributing in your own capacity.
- Use the [Corporate Contributor Agreement](CORPORATE_CONTRIBUTOR_AGREEMENT.md) when an employer or organization owns, controls, sponsors, or authorizes the work.
| Version | Model | Documents | Status |
|---|---|---|---|
| 2.0 | Contributor keeps ownership; Botshare LTD receives a permanent, irrevocable, worldwide, royalty-free, transferable and sublicensable licence | [Individual Contributor License Agreement](INDIVIDUAL_CONTRIBUTOR_LICENSE_AGREEMENT.md), [Corporate Contributor License Agreement](CORPORATE_CONTRIBUTOR_LICENSE_AGREEMENT.md), [Guardian Consent](MINOR_CONTRIBUTOR_GUARDIAN_CONSENT.md) | Approved text. **Not yet offered for acceptance.** |
| 1.1 | Assignment of transferable economic rights to Botshare LTD | [Individual Contributor Agreement](INDIVIDUAL_CONTRIBUTOR_AGREEMENT.md), [Corporate Contributor Agreement](CORPORATE_CONTRIBUTOR_AGREEMENT.md) | Currently offered through CLA Assistant. Closed to new acceptances from the activation date of version 2.0. |

**Activation date of version 2.0:** not set. Botshare LTD records the date here, in the same change that records the activation evidence below. Until then, CLA Assistant presents version 1.1, and nobody is covered by version 2.0.

The version whose acceptance is recorded for a contributor governs that contributor's contributions:

- Contributions accepted under version 1.1 stay under version 1.1. Assignments already made remain in effect.
- From the recorded time a contributor accepts version 2.0, version 2.0 governs every contribution of that contributor accepted afterwards, and no assignment under version 1.1 takes place for them.
- Publishing or changing a file in this repository does not change the agreement any contributor has accepted.

## Which agreement applies

- Use the Individual agreement when contributing in your own capacity.
- Use the Corporate agreement when an employer or organization owns, controls, sponsors, or authorizes the work.
- If an employer, university, client, sponsor, co-author, joint inventor, or other party may have rights, obtain written authorization before submission.
- A contributor must not self-select the Individual Agreement merely to avoid a rights holder’s authorization.
- A contributor must not choose the Individual agreement to avoid a rights holder's authorization.
- A contributor under 18 needs the Guardian Consent on record before any contribution is merged.

## Individual contributor workflow

OpenAMRobot uses CLA Assistant with the organization-wide, shared **OpenAMRobot ICLA v1.1**.
OpenAMRobot uses CLA Assistant with one organization-wide agreement.

1. Open a pull request.
2. Follow the CLA Assistant link shown on the pull request.
3. Authenticate with the GitHub account used for the contribution.
4. Review and affirmatively accept the complete ICLA v1.1.
5. Wait for the CLA Assistant status check to pass.
3. Sign in with the GitHub account used for the contribution.
4. Read the complete agreement shown, check its document identifier and version, and accept it.
5. Wait for the `license/cla` status check to pass.
6. Ensure every commit also passes DCO.

An individual normally signs the shared agreement once. Later pull requests from the same verified GitHub account are recognized automatically while that agreement version remains applicable.
A contributor normally accepts once per version. When a new version is activated, CLA Assistant asks for a new acceptance on the next pull request.

## Contributors under 18

1. A parent or legal guardian completes the [Guardian Consent](MINOR_CONTRIBUTOR_GUARDIAN_CONSENT.md) and sends it privately to **[email protected]**.
2. Botshare LTD confirms in writing that it is on record.
3. Only then may a maintainer merge the contributor's pull requests. A CLA Assistant acceptance given by the minor alone is not sufficient.
4. On reaching 18, the contributor accepts the Individual agreement personally.

## Corporate, employer, and institutional workflow

CLA Assistant acceptance is for contributors acting in their individual capacity. Where an employer, company, university, sponsor, client, or institution owns or controls the work:

1. complete the [Corporate Contributor Agreement](CORPORATE_CONTRIBUTOR_AGREEMENT.md);
1. complete the Corporate agreement in force;
2. have an authorized representative sign it;
3. identify the Authorized Contributors and GitHub usernames;
4. send the agreement privately to **[email protected]** with subject: `OpenAMRobot Corporate Contributor Agreement — [legal entity]`; and
5. wait for Botshare LTD to confirm coverage before submitting or merging Contributions.
3. list the Authorized Contributors and their GitHub usernames;
4. send it privately to **[email protected]** with subject `OpenAMRobot Corporate Contributor Agreement, [legal entity]`; and
5. wait for Botshare LTD to confirm coverage in writing before submitting or merging contributions.

An organization that signed version 1.1 stays under version 1.1 until both parties have signed version 2.0.

Signed agreements, identity documents, and private authorization records must never be committed to a public repository.

## Acceptance controls

DCO and the Contributor Agreement are cumulative:
DCO and the contributor agreement are cumulative:

- DCO records provenance and the committer's certification.
- The accepted agreement governs inbound rights: assignment under version 1.1, licence under version 2.0.
- Passing an automated check does not cure invalid acceptance, missing authority, missing guardian consent, impersonation, or undisclosed third-party rights.
- A pull request must not merge until both DCO and the applicable agreement requirement are satisfied.
- A green `license/cla` check shows that the contributor accepted the agreement CLA Assistant presented at that time. Before the activation date that is version 1.1. A maintainer must not treat any contributor as covered by version 2.0 before the activation date, or without a CLA Assistant record of that contributor dated on or after it.

## Activating version 2.0

Version 2.0 is activated only when all of the following are done and recorded:

- DCO records provenance and the committer’s certification.
- The accepted Agreement governs assignment and inbound rights.
- Passing an automated check does not cure invalid acceptance, missing authority, impersonation, or undisclosed third-party rights.
- A pull request must not merge until both DCO and the applicable CLA requirement are satisfied.
1. Botshare LTD's director approves the final texts in writing, after legal review.
2. The exact approved Individual text is published in a new, separately versioned CLA Assistant document. The version 1.1 document is never edited.
3. The published text is compared with the file in this repository and the SHA-256 of the file is recorded below.
4. A test pull request confirms that CLA Assistant shows version 2.0, asks a version 1.1 signer for a new acceptance, and records the acceptance with the document identifier.
5. The version 1.1 signature list is exported and stored privately with the version 1.1 text.
6. The organization-wide CLA Assistant link is switched to the version 2.0 document, and the activation date is entered above.
7. Every open external pull request is rechecked so that it asks for version 2.0.

Botshare LTD maintains records linking the agreement or electronic acceptance to the contributor, agreement version, GitHub identity, corporate authorization where relevant, pull requests, commit hashes, timestamps, and acceptance decision.
Activation evidence (filled in at activation): CLA Assistant document URL and revision: not set. SHA-256 of the Individual text: not set. Test pull request: not set.

## Version changes

The agreement version accepted by the contributor governs Contributions covered by it. A material amendment requires new acceptance. Updating a public Markdown file or Gist does not silently amend an accepted agreement. A material new version must use a separately versioned agreement record.
A material amendment requires new acceptance. Updating a public Markdown file or CLA Assistant document does not amend an accepted agreement. A material new version uses a separately versioned agreement record.

## Data protection

Contributor records are handled under the [Contributor Privacy Notice](CONTRIBUTOR_PRIVACY_NOTICE.md). Public repositories must contain no signed agreements, residential addresses, identification documents, or private contact details.
Contributor records are handled under the [Contributor Privacy Notice](CONTRIBUTOR_PRIVACY_NOTICE.md). Public repositories must contain no signed agreements, residential addresses, dates of birth, identification documents, or private contact details.
7 changes: 5 additions & 2 deletions CLA_RECORDKEEPING.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,14 +8,17 @@ For each contributor, record privately:

- legal name and verified contact email;
- GitHub username and, where applicable, employer or represented entity;
- agreement type (ICLA or CCLA), exact version, acceptance method, and acceptance timestamp;
- agreement type (ICLA or CCLA), document identifier and exact version, acceptance method, and acceptance timestamp;
- for a contributor under 18, that guardian consent is on record and its date (the form itself and the date of birth stay in the private file only);
- CCLA signatory authority and the covered contributor list;
- repository, pull request number, and accepted commit hashes;
- disclosed Background IP, third-party material, AI assistance, employer, university, client, sponsor, or co-author permissions;
- accepting maintainer and merge timestamp; and
- any exception, withdrawal, superseding agreement, or legal follow-up.

Export CLA Assistant acceptance records regularly and retain them with the immutable agreement version that the contributor accepted. Restrict access to authorized Botshare LTD personnel and apply the Contributor Privacy Notice and applicable retention requirements.
A contributor's coverage under a version starts at the recorded acceptance time of that version, never earlier. When a contributor moves from version 1.1 to version 2.0, keep both records: contributions accepted before the version 2.0 acceptance time stay under version 1.1.

Export CLA Assistant acceptance records regularly, and always before the organization-wide agreement is switched to a new version, and retain them with the immutable agreement version that the contributor accepted. Restrict access to authorized Botshare LTD personnel and apply the Contributor Privacy Notice and applicable retention requirements.

DCO status and Git history support provenance but do not replace the Contributor Agreement record.

Expand Down
36 changes: 36 additions & 0 deletions CLA_TRANSITION_v2.0.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
# Contributor agreement transition to version 2.0

Status on 22 November 2026: version 2.0 texts approved in direction by the owner and prepared for review. **Not activated.** The live status is the table in [CLA.md](CLA.md).

## What changes

Version 1.1 assigns transferable economic rights in accepted contributions to Botshare LTD. Under version 2.0 the contributor keeps ownership and grants Botshare LTD a non-exclusive, worldwide, perpetual, irrevocable, royalty-free, transferable and sublicensable licence, with patent rights, for any purpose. The public project licences do not change.

## What does not change

- Contributions accepted under version 1.1 stay assigned. This transition reverses nothing.
- DCO sign-off on every commit.
- Outbound licences: MIT, CERN-OHL-P-2.0, CC BY 4.0.

## Before activation

1. Legal review by Cyprus-qualified intellectual property counsel of: enforceability and irrevocability of the licence, the patent licence and its termination clause, contributors under 18 and the guardian consent, and the effect on version 1.1 assignments (including whether click-through assignments were valid, and the fallback licence).
2. Written approval of the final texts by Botshare LTD's director.
3. The activation steps in [CLA.md](CLA.md), in order. No contributor is treated as covered by version 2.0 before a CLA Assistant record of that contributor's acceptance exists, dated on or after the activation date.

## At activation

1. Notify contributors: what changes, that earlier contributions stay under version 1.1, and that the next pull request asks for a new acceptance.
2. Send organizations with a signed version 1.1 corporate agreement the version 2.0 corporate agreement for signature. Each stays under version 1.1 until both parties have signed.
3. Obtain guardian consent for every contributor under 18 before merging further work from them, with the box for earlier contributions ticked where they have any.
4. Recheck every open external pull request. A pull request whose author has not accepted version 2.0 is not merged, unless Botshare LTD decides and records that it merges under version 1.1 with the author's agreement.
5. Update the contribution, licensing and notice files in the other OpenAMRobot repositories that still describe assignment only.

## After activation

- Do not switch CLA Assistant back to version 1.1. Correct a non-material error as 2.0.1; a material change is a new version that needs acceptance.
- One month later, reconcile the CLA Assistant export with merged pull requests and record any gap.

## Separate from this agreement

People who work for Botshare LTD for pay, as employees or contractors, are covered by their own written agreements with Botshare LTD, not by the contributor agreement.
5 changes: 2 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ are in [AGENTS.md](AGENTS.md).

## 2. Set up

1. Sign the contributor agreement once: see [CLA.md](CLA.md).
1. Accept the contributor agreement: see [CLA.md](CLA.md). Contributors under 18 need the guardian consent described there first.
2. Fork the repository and create **one branch per work package**.
3. Sign off every commit: `git commit -s`. The sign-off certifies the [DCO](DCO.md) with your
own name and e-mail.
Expand Down Expand Up @@ -108,8 +108,7 @@ A maintainer merges; approval or a green check alone does not accept a contribut
## Legal, conduct and contact

Contributions are governed by the [IP Policy](IP_POLICY.md), the
[Individual](INDIVIDUAL_CONTRIBUTOR_AGREEMENT.md) or
[Corporate](CORPORATE_CONTRIBUTOR_AGREEMENT.md) Contributor Agreement, the
contributor agreement version you accepted ([CLA.md](CLA.md)), the
[AI contribution policy](AI_CONTRIBUTION_POLICY.md) and the
[third-party policy](THIRD_PARTY_POLICY.md). Identify any material you did not create
yourself with its source and licence. Do not submit secrets, personal data or confidential
Expand Down
Loading