Loading...
Searching...
No Matches
Contributor License Agreement — MeshKit

Version 1.2 — October 2026

Thank you for your interest in contributing to MeshKit, maintained by the Technical Manager of the project (currently @cbuahin). This Contributor License Agreement ("CLA") clarifies the intellectual property rights granted with contributions to the project. By signing this CLA you confirm that you have the legal authority to grant these rights, and that the Technical Manager may rely on them.

This CLA does not transfer your copyright to the Technical Manager. You retain full ownership of your contributions. The CLA grants a license that enables the project to be distributed, maintained, and relicensed in the future without requiring additional consent from every contributor.

The Project is currently distributed to the public under the Apache License, Version 2.0 (see LICENSE). Contributions accepted into the Project are made available under those terms, together with the attribution notices recorded in NOTICE. The relicensing right granted in Section 2 below operates in addition to, and does not revoke, that outbound license: anything already released under the Apache License, Version 2.0 stays available under it.

The Technical Manager role may transfer over time per the succession process described in CONTRIBUTING.md §3. Rights granted under this CLA persist through any such transition and vest in whoever holds the Technical Manager role at the time they are exercised.


1. Definitions

  • "You" — the individual, or the legal entity on whose behalf an individual is signing, submitting a contribution.
  • "Contribution" — any original work of authorship, including source code, documentation, tests, configuration, data, or any other material, intentionally submitted to the project by You via a pull request, patch, issue attachment, or any other means.
  • "Project" — the MeshKit software repository hosted at https://github.com/HydroCouple/Meshkit.
  • "Technical Manager" — the current holder of the Technical Manager role for the Project, as defined in CONTRIBUTING.md §2. The current Technical Manager is @cbuahin.

2. Grant of Copyright License

Subject to the terms of this CLA, You hereby grant to the Technical Manager a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to:

  • reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works;
  • relicense Your Contributions under any license, including but not limited to the Apache License 2.0, GPLv3, LGPL, AGPL, MIT, or a commercial license, at the Technical Manager's sole discretion and without further notice to You.

This grant is at least as broad as the copyright license in Section 2 of the Apache License, Version 2.0, so the Technical Manager may distribute Your Contributions under the Project's current outbound license without further action by You.

The relicensing right is granted specifically to preserve the Technical Manager's ability to adapt the project's licensing terms over time (for example, to offer a dual open-source/commercial licensing model) without being required to seek individual consent from each contributor.


3. Grant of Patent License

Subject to the terms of this CLA, You hereby grant to the Technical Manager and to recipients of software distributed by the Technical Manager a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer Your Contributions, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution alone or by combination of Your Contribution with the Project.

If any entity institutes patent litigation against You or any other party alleging that Your Contribution constitutes patent infringement, any patent licenses granted to that entity under this CLA for that Contribution shall terminate as of the date such litigation is filed. This Section mirrors the patent grant and defensive termination provisions of Section 3 of the Apache License, Version 2.0.


4. Copyright Retention

You retain full copyright ownership of Your Contributions. This CLA grants a license as described above; it does not transfer or assign your copyright.


5. Representations and Warranties

By submitting a Contribution, You represent and warrant that:

  1. You are the author. You are the sole author of the Contribution, or you have the legal right to submit it on behalf of all co-authors.
  2. You have authority to grant this license. The license grant in Sections 2 and 3 does not violate any agreement you have with a third party, and no third party has any claim over your Contribution that would restrict the grant.
  3. Third-party content is disclosed. If Your Contribution includes any third-party code, data, or assets, you have identified them clearly in the pull request description, confirmed their licenses are compatible with the Apache License, Version 2.0, and added any attribution those licenses require to NOTICE.
  4. Employer authorization. If you are employed and your Contribution relates to your employer's business or was created using employer resources, your employer has either (a) authorized you to make this Contribution and granted the necessary rights, or (b) signed a Corporate CLA (see Section 6) covering this Contribution.

6. Corporate Contributors

If you are submitting a Contribution on behalf of a company, organization, or other legal entity ("Organization"), or if Section 5, item 4 applies to your Contribution, the Organization must also sign the Corporate Contributor License Agreement (CCLA). The CCLA text is at CCLA.md. It covers all individuals the Organization designates as authorized to submit Contributions on its behalf.

The CCLA does not replace this Individual CLA. Individuals must sign both.

To submit a CCLA, complete Schedules A, B, and C of CCLA.md and either email the completed agreement to the Technical Manager at support@hydrocouple.org or open a GitHub Discussion titled [CCLA] <Organization Name> in the Project's Discussions tab. The CCLA takes effect when acknowledged in writing by the Technical Manager.

Merge policy. Where Section 5, item 4 applies, Contributions may be developed and reviewed openly at any time and are held in review, but will not be merged into any branch of the Project until a CCLA covering them is on file or the Organization has provided written authorization. This requirement applies uniformly to all contributors, including the Technical Manager. It was adopted on October 3, 2026 and applies to merges after that date.


7. Moral Rights

To the fullest extent permitted by applicable law, You waive and agree not to assert any moral rights you may have in Your Contributions against the Technical Manager or recipients of the software, including rights of integrity and rights of attribution beyond those provided in AUTHORS.md.


8. No Warranty

Your Contributions are provided on an "AS IS" basis, without warranties or conditions of any kind, either express or implied, including, without limitation, any warranties or conditions of title, non-infringement, merchantability, or fitness for a particular purpose.


9. How to Sign

Individual Contributors

First-time contributors must sign this CLA before their pull request can be merged. Signing is done through GitHub or by email — no PDF is required.

Using the CLA Assistant GitHub Action (recommended):

The project is adopting the CLA Assistant GitHub Action to automate CLA signing, but it is not yet enabled on this repository. Until it is, sign by pull request comment or by email as described below. Once it is enabled, the action will post a comment on your first pull request asking you to sign. When you reply with the comment shown below, it will record your GitHub username, the pull request, and the date and time of your signature in .github/cla-signatures.json in this repository.

Alternatively, you may sign manually by posting the following comment on your pull request:

I have read the CLA Document and I hereby sign the CLA.

Your GitHub username and the date of the comment serve as your electronic signature and are recorded permanently in the pull request history.

By email. A contributor may also sign by sending an email from the contributor's personal email address to support@hydrocouple.org, stating the contributor's name, GitHub username, the Project repository, the CLA version, and the sentence "I have read the CLA Document and I hereby sign the CLA," or attaching a signed copy of this CLA. The signature, the date the email was received, and the Maintainer who recorded it are entered in CLA-SIGNATORIES.md, and the recording Maintainer also enters the signature in the CLA Assistant record.

Returning Contributors

Once you have signed the CLA, it covers all future Contributions to this project. You do not need to sign again for subsequent pull requests.


10. Applicability to Prior Contributions

If you have previously submitted Contributions to this project before this CLA was established, those Contributions are deemed covered by this CLA as of the date you sign it, provided you have the authority to grant the licenses described herein for those prior Contributions.


11. Governing Law

This CLA shall be governed by and construed in accordance with the laws of the Commonwealth of Kentucky, without regard to its conflict of law provisions.


12. Contact

Questions about this CLA should be directed to the Technical Manager via GitHub:


13. Public Domain Material

Portions of the Project, the robust geometric predicates in vendor/predicates, were placed in the public domain by their author, Jonathan Richard Shewchuk. Nothing in this CLA asserts, or asks You to assert, copyright over that material. If Your Contribution modifies or extends public domain material, the licenses granted above apply only to Your own original changes; the underlying public domain material remains free of any such restriction. See NOTICE and vendor/predicates/LICENSE for the provenance statement.


This CLA is maintained by the Technical Manager of MeshKit (currently @cbuahin). Last updated: November 2026.