Contributor License Agreements

CyberBoar accepts contributions after the required Contributor License Agreements (CLAs) have been signed. Individuals sign on CLA assistant from their pull request; companies sign by email. A maintainer verifies coverage before merging a pull request. A pull-request checkbox is not a signature.

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

Individual CLA

1. Open a pull request. CLA assistant comments on it with a link to the agreement.
2. Sign in with the GitHub account the commits come from, fill in the form and select “I agree”. The pull request’s license/cla check turns green.
3. Later pull requests need no new signature unless the agreement changes.

Each commit author signs with their own account, co-authors included. A PR comment, commit sign-off or Git commit signature is not a signature. The form’s details are not published; see the privacy notice.

Corporate CLA

1. Read the Corporate CLA 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. An authorized representative completes the agreement, lists the contributing employees and their GitHub accounts in Schedule A, and saves the entire agreement, including its terms and signature, as a PDF.
3. Sign the PDF using a drawn or electronic signature. Alternatively, attach a detached GPG signature and provide the verification key and fingerprint.
4. Email the signed agreement to dev@cyberboar.io from the email address in the form. 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. Each listed employee also signs the Individual CLA on CLA assistant.

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.

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 and replace Apache contact and signing instructions with the processes above. The Individual CLA is signed electronically, so its signature block is replaced by a signing section. The Corporate CLA replaces 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.