Skip to content

Contributor License Agreement

Contributions to ifc-lite need a signed LTplus AG Contributor License Agreement (CLA). This page explains what it does and why we ask.

What you agree to

The CLA is a license, not a copyright transfer. You keep ownership of your work and can still use it however you like.

You give LTplus AG, which maintains ifc-lite, a broad license to your contributions. That includes the right to license them under other terms, including commercial licenses to customers who cannot use MPL-2.0 code. In return, LTplus promises in section 5 to keep your contributions publicly available under the Mozilla Public License 2.0 or another OSI-approved open source license, and to keep your name on them.

The CLA also includes a patent license and the usual statements that the work is yours to contribute. Read CLA.md in full before signing. It is short.

Why we ask

ifc-lite stays open source under MPL-2.0. Some companies want to build on it under different terms, and selling them that license helps pay for the project. Under MPL-2.0 alone, LTplus would need permission from every contributor each time, which doesn't scale for a project that merges hundreds of changes a month. Signing once settles it for your past and future contributions.

How to sign

When you open a pull request, the CLA check tells you whether you have signed. If you haven't, it posts a comment. Reply on the pull request with exactly:

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

The check turns green, and you won't be asked again for later pull requests. Everyone who authored a commit in the pull request signs for themselves.

If someone else's commits are in your pull request, they need to sign too. The check can only match commits to people through GitHub accounts, so a commit made with an email that isn't linked to any account blocks it. Add that email to your GitHub account and comment recheck, or re-author the commits with a linked email.

People named in a Co-authored-by: line sign too. Write the trailer with the co-author's GitHub noreply address (ID+login@users.noreply.github.com, shown in their GitHub email settings) so the check can match it to their account. A co-author line with any other email blocks the check until that person has signed by email or PDF. AI coding assistants named as co-authors need no signature.

You can also sign by email or as a signed PDF. CLA.md describes both routes. Use one of them if your country requires a handwritten signature for this kind of agreement.

Contributing for an employer or your own company

If your contribution was made as part of your job, or belongs to a company you own, the company has to agree too. Ask in the pull request and we'll send the corporate form.

What is recorded

Signing records your GitHub username and account ID, the CLA version and a hash of its text, the date, and links to your pull request and comment. The record is public, on the cla-signatures branch of this repository.

Email and PDF signatures are kept privately in LTplus company records. For the check to recognise them, a maintainer adds an entry to the public record with only your GitHub account ID and the route, never your name or the signed document. A commit email is recorded instead only for commits whose email isn't linked to any GitHub account.

New versions of the CLA

If the CLA text changes, its version number changes, and the check asks everyone to sign the new version on their next pull request. Signatures for earlier versions keep covering the contributions made under them.

Contributions made before the CLA

Contributions made before this check existed were made under MPL-2.0 only. LTplus is contacting those contributors individually.