Skip to content

legal: propose contributor-retained-rights ICLA v2.0 (not in force) - #93

Closed
BotshareAI wants to merge 3 commits into
mainfrom
legal/contributor-retained-rights-v2-proposal
Closed

BotshareAI wants to merge 3 commits into
mainfrom
legal/contributor-retained-rights-v2-proposal

Conversation

@BotshareAI

@BotshareAI BotshareAI commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Purpose

Propose a contributor-ownership-retaining licence: individual and corporate contributors keep title to rights they own, while Botshare LTD receives a perpetual, irrevocable, worldwide, royalty-free, non-exclusive, transferable, sublicensable grant for use, modification, commercial exploitation and appropriate licensing. Respect authorship and Background IP, preserve asset-specific project licensing and enforce third-party provenance.

Legal status

DRAFT ONLY — not yet in force. Current ICLA v1.1 and CCLA v1.1 remain operative, including their assignment terms. This PR changes no active agreement, CLA Assistant configuration or contributor consent. The final legal text and electronic acceptance flow require Cyprus-qualified IP counsel review, founder approval and new affirmative acceptance. Existing assignments cannot be retroactively undone.

Draft files

  • INDIVIDUAL_CONTRIBUTOR_LICENSE_AGREEMENT_v2.0_DRAFT.md
  • CORPORATE_CONTRIBUTOR_LICENSE_AGREEMENT_v2.0_DRAFT.md
  • CONTRIBUTOR_LICENSE_TRANSITION_v2.0_DRAFT.md

What the transition must do

  1. Legal review including patent rights, background materials, moral rights and sublicensing.
  2. Approve and publish immutable final v2.0 text.
  3. Configure the external CLA Assistant and ensure no v1.1 acceptance is mistaken for v2.0.
  4. Update operative CLA.md, IP_POLICY.md, CONTRIBUTING.md, DCO.md, corporate workflows and checks in one coordinated, reviewed rollout.
  5. Test individual and corporate PR flows with actual affirmative consent.
  6. Keep originals and history for v1.1, map each pending contribution to the valid accepted version.

Verification / Integration Gate

Read current default-branch ICLA v1.1, CCLA v1.1, CLA.md, IP_POLICY.md, THIRD_PARTY_POLICY.md, CONTRIBUTING.md and DCO.md (19 Nov). These are new proposal documents only; no active governance changed. Legal tests/CLA Assistant checks cannot be validated on a draft; treat all legally operative effects as NOT VERIFIED. Do not merge as an operative policy change, publish as effective, or solicit signatures before counsel and founder approval.

Request

Founder and Cyprus-qualified IP counsel: adopt/adapt/reject. Then authorize a separate reviewed rollout.

@Manas-arumalla

Copy link
Copy Markdown

Thanks for the draft. It addresses my concern with v1.1: ownership stays with the contributor (§2), Background Material is covered (§4), and attribution (§6) works for me. Before accepting, a few questions:

  1. §7(c), "materially AI-assisted content is disclosed with provenance": what form should this take? I'd suggest a PR-level statement (the PR template's checkbox plus a sentence on which parts were AI-assisted and that the contributor reviewed and tested them) rather than per-commit tool trailers. And what counts as "materially": code or text substantially generated by a tool, as opposed to autocomplete or spelling?
  2. §4: if Background Material is used but not copied into a PR (for example a local script that depends on my own openarm-control), is naming it in the PR enough?
  3. §1/§10: once I accept v2.0, does it cover my open drafts (#100, #111)? I haven't accepted v1.1.

@BotshareAI

Copy link
Copy Markdown
Contributor Author

Thank you for the careful read and the three questions. They are now answered in the text itself, in #95, which replaces this draft with a clean, signed-off history and brings the corporate agreement and the related policies in line.

  1. AI disclosure. Your suggestion is adopted: a statement in the pull request description (which parts, which tool, and that you reviewed and tested them). No per-commit trailers. "Materially" means a tool generated a substantial part of the code, text, design or data; autocomplete, spelling and formatting aids do not count.
  2. Background material that is used but not copied in. Naming it in the pull request with its location and licence is enough, and it is not licensed by the agreement. Only material that is actually included in a contribution is licensed, on the same terms as the contribution.
  3. Open drafts. Version 2.0 covers every contribution merged after your acceptance of it is recorded, including pull requests opened earlier. Since you have not accepted version 1.1, nothing of yours falls under it.

Status: version 2.0 is not active yet. It still goes through a legal check, and CLA Assistant keeps presenting version 1.1 until then, so please do not sign there for now. Your drafts can stay as drafts in the meantime. If anything in #95 does not work for you, comments there are very welcome.

Closing this one in favour of #95.

@BotshareAI BotshareAI closed this Nov 22, 2026
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