Contributor License Agreement (CLA)
Combines a contributor license agreement with a branch naming convention and a signing procedure for pull requests.
What this file does
Combines a contributor license agreement with a branch naming convention and a signing procedure for pull requests.
When to use it
- You need a CLA for an open-source project
- You want to enforce a branch naming pattern like feat/CW-<number>/<desc>
- You require contributors to sign a license on their first PR
Contributor License Agreement (CLA)
Contributing to ControlWeave
Thank you for your interest in contributing to ControlWeave! This document covers both the Contributor License Agreement and how to get started.
Getting Started
-
Fork the repository
-
Create a feature branch following our naming convention:
feat/CW-<issue-number>/<short-description>Examples:
feat/CW-42/add-gdpr-framework fix/CW-15/pagination-offset-bug docs/CW-7/improve-setup-guide -
Make your changes following the guidelines in CONTRIBUTING.md
-
Open a Pull Request — the CLA bot will ask you to sign on your first PR
For full development setup and coding standards, see CONTRIBUTING.md.
Contributor License Agreement
ControlWeave Community Edition
This Contributor License Agreement ("CLA") applies to any contribution you make to ControlWeave Community Edition ("the Project"), maintained by sherifconteh-collab.
1. Definitions
- "Contribution" means any code, documentation, or other material submitted to the Project via pull request, issue, or other mechanism.
- "You" (or "Contributor") means the individual or legal entity making the Contribution.
2. Grant of License
By submitting a Contribution, you grant to the Project maintainers a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable license to use, reproduce, modify, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute your Contribution and any derivative works under the terms of the AGPL-3.0 License.
3. Representations
You represent that:
- You are legally entitled to grant the above license.
- Each Contribution is your original creation or you have the right to submit it.
- Your Contribution does not violate any third-party intellectual property rights.
- If your employer has rights to intellectual property that you create, you have received permission to make the Contribution on behalf of that employer, or your employer has waived such rights for the Contribution.
4. No Obligation
You understand that the decision to include your Contribution in the Project is entirely at the discretion of the Project maintainers. You are not expected to provide support for your Contribution unless you choose to do so.
5. How to Sign
To sign this CLA, comment on the relevant pull request with:
I have read the CLA Document and I hereby sign the CLA
Your signature will be recorded automatically.
Contact
For questions about this CLA or contributing, email contehconsulting@gmail.com.
What's inside
5 sections: getting started, branch naming, CLA definitions, grant terms, signing instructions
Change this for your project
- Replace
ControlWeavewith your project name - Replace
sherifconteh-collabwith your GitHub username or org - Replace
contehconsulting@gmail.comwith your contact email - Replace
CW-<issue-number>with your own issue tracker prefix
Where it goes
Keep it in your repository where the agent or team that needs it will read it.
Worth borrowing
- Branch naming convention that ties to issue numbers and a project prefix
- CLA signing via a pull request comment that a bot records
Related Documents
Dev Setup Install Instructions
Walks through setting up a conda environment, installing dependencies, and configuring MinKNOW for simulated Flongle replay and adaptive sampling.
canvas_dev_setup
Guides developers through setting up a local Canvas LMS instance with Apache and integrating it with the Wiki Education Dashboard via LTI 1.3.
My current setup (2026 edition)
Documents a developer's personal IDE, terminal, macOS, iOS, hardware, and tooling choices in 2026.
dev_setup
Explains how to install, run, test, profile, and contribute to the Vimflowy project locally.