You're viewing docs for v1.0.0-rc.1. View the latest release

Contributor License Agreements

CyberBoar accepts contributions after the required Contributor License Agreements (CLAs) have been signed and accepted by the Project Owner. Signing is handled privately by email; a maintainer verifies coverage before merging a pull request. A pull-request checkbox is not a signature.

ContributorAgreement
Every individual contributorIndividual CLA, CyberBoar ICLA 1.0
An employer or other company that owns the contributionCorporate CLA, CyberBoar CCLA 1.0, in addition to each contributor’s Individual CLA

The Project Owner is the individual identified in the agreements by the CyberBoarDev account and its numeric user ID. This does not identify the GitHub organization as a company or grant rights to everyone with repository access.

What the agreements cover

Contributors retain copyright. The agreements grant copyright and patent licenses, including the right to sublicense contributions. Contributions may be distributed in the AGPL-licensed CyberBoar project and in separately licensed commercial products. Signing does not require a contribution to be accepted or merged.

Issues and proposals are welcome without a signed CLA. Report vulnerabilities privately under SECURITY.md.

Signing

  1. Read the full agreement at a specific commit of this repository. Keep that full commit SHA with the copy you sign, along with the agreement version printed in the document. Do not use a mutable main URL as the only record of the terms.
  2. Complete the Individual CLA and save the entire agreement, including its terms and signature, as a PDF. Include your GitHub account so the signed agreement can be matched to your contributions. If an employer owns the work, also arrange for an authorized representative to sign the Corporate CLA and list the contributing employees in Schedule A.
  3. Sign the PDF using a drawn or electronic signature. Alternatively, attach a detached GPG signature and provide the verification key and fingerprint. A typed name, PR comment, commit sign-off or Git commit signature alone is not the signing process used here.
  4. Email the signed agreement to dev@cyberboar.io from the email address in the form. Include your GitHub profile and pull-request URL. Do not copy public mailing lists or attach the agreement to an issue or pull request. Keep a copy.
  5. Wait for a private acceptance reply. A maintainer confirms CLA coverage on the pull request without publishing the signed form or its personal information. If you already have an accepted agreement covering the contribution, identify the earlier acceptance in your email instead of signing again.

Signing copies and correspondence stay outside the public repository. To correct contact details or employee authorizations, contact dev@cyberboar.io privately. Do not send identity documents or personal information unrelated to the agreement.

See the maintainer procedure for acceptance and merge checks.

Origin and changes

These agreements are adapted from the Apache Software Foundation’s Individual CLA v2.2 and Software Grant and Corporate CLA r190612. Apache explicitly permits reuse and modification of its CLAs. The adaptations are not Apache agreements and do not imply Apache endorsement.

The adaptations identify the CyberBoar recipient by its public GitHub account, replace Apache contact and signing instructions with the private email process above, and replace Apache-specific profile fields with GitHub account information and an agreement source revision. Apache’s nonprofit-status and bylaws commitment does not apply to this project and is omitted. Its copyright and patent grant clauses, contributor representations and disclaimer are retained. The corporate agreement includes both Schedule A and the optional software grant in Schedule B.

This summary does not replace the terms of the signed agreements.