Skip to main content

Contributor License Agreement (CLA)

Thank you for your interest in contributing to Framework M!

Before we can accept your contributions (code, documentation, or other materials), we need you to sign a Contributor License Agreement (CLA) to protect the project and its users. The CLA ensures that you retain the copyright to your contribution, but grant us the necessary rights to use, distribute, and build upon it under the project's open-source license.

Types of Agreements​

There are two forms of the CLA:

  • Individual Contributor License Agreement (ICLA): For individuals contributing on their own behalf.
  • Corporate Contributor License Agreement (CCLA): For individuals contributing on behalf of their employer or organization. This requires authorization from someone who has the authority to bind the organization.

How to Sign the CLA​

To legally bind your contributions to the Apache 2.0 license, we maintain a strict traceability mapping between your legal agreement (the Issue) and the programmatic proof (the Merge Request).

  1. Review the Agreement: Ensure you agree to the terms of the Apache 2.0 license and the standard CLA terms for open-source contributions.
  2. Open a CLA Issue (The Legal Trace): Go to the project's GitLab issue tracker and click New Issue.
  3. Select a Template:
    • Choose the ICLA template if you are contributing on your own behalf.
    • Choose the CCLA template if you are contributing on behalf of your organization.
  4. Agree and Submit: Fill out the requested details (your GitLab handle, name, and if CCLA, the GitLab handles of the covered employees) and check the "I AGREE" box. Submit the issue.
  5. Create the Merge Request (The Programmatic Proof): Create a new branch, manually add your agreed username to contributors.json, and open a Merge Request.
  6. Map the Trade: In your Merge Request description, explicitly link your CLA Issue (e.g., Closes #123).
  7. Approval: A project maintainer will verify your issue agreement matches the username in your contributors.json MR, and then merge it. Once merged, future code contributions will automatically pass the CLA verification pipeline.

By submitting a contribution to this project, you agree to license your work under the same terms as the project (Apache License 2.0) and you represent that you have the right to do so.