Skip to content

CLA.md

Latest commit

 

History

History
54 lines (35 loc) · 3.29 KB

CLA.md

File metadata and controls

54 lines (35 loc) · 3.29 KB
Raw

OpenAMRobot Contributor Agreement Process

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

Applicable agreement

  • Use the Individual Contributor Agreement when contributing in your own capacity.
  • Use the Corporate Contributor 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.

Individual contributor workflow

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

  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.
  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.

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;
  2. have an authorized representative sign it;
  3. identify the Authorized Contributors and GitHub usernames;
  4. send the agreement privately to info@botshare.ai with subject: OpenAMRobot Corporate Contributor Agreement — [legal entity]; and
  5. wait for Botshare LTD to confirm coverage before submitting or merging Contributions.

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 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.

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.

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.

Data protection

Contributor records are handled under the Contributor Privacy Notice. Public repositories must contain no signed agreements, residential addresses, identification documents, or private contact details.