The CLA for students #

Before you send code to the Exponential kernel, read this page. It explains the Contributor Licensing Agreement (CLA) in plain words for learners. It summarizes CONTRIBUTING.md; the agreement itself is what counts, and this page is not legal advice (Copyright assignment (CLA)).

Contents #

1. In one paragraph
2. When you need it
3. When you do not
4. How to sign
5. Questions students ask

In one paragraph #

7x and the Exponential Foundation require a signed CLA for every code contribution to the core kernel of Exponential, the repository se7enxweb/exponential, before it can be merged. "By signing the CLA and submitting a contribution to the core kernel, you assign (transfer) the copyright in that contribution to the Exponential Foundation and 7x. They become the copyright owners." You give up control: the Exponential Foundation and 7x may use, change, relicense and distribute the contribution in any way, including commercially, without asking or paying you, and you cannot withdraw it. Your own custom extensions are not affected.

When you need it #

• A pull request, patch, or code in an issue or mail to the core kernel: kernel/, lib/, bin/, design/, settings/, doc/, the extensions shipped inside it, and everything else in that repository.
• A pull request from someone without a signed CLA on file is reviewed, but not merged until the CLA has been received.
• An extension you hand over to 7x for inclusion in the project is covered the same way.

Note that doc/ is part of the kernel repository. Documentation fixes there are contributions to that repository.

When you do not #

• Your own extensions, site packages, designs and themes that you write, keep and license yourself, whether private or published in your own repository. The CLA page says: "if you have written a contribution and want to make it available on GitHub (https://github.com), you do not need to sign the CLA."
• A site you build and run with Exponential; that is governed by the GPL.
• Anything you mark in writing as "Not a Contribution".
• For "small patches or bugfixes via our bugsystem, in most cases we do not need you to sign a CLA" (CLA page). For pull requests to the kernel, CONTRIBUTING.md advises to sign anyway, since a merge needs a CLA on file and you sign only once.

How to sign #

From CONTRIBUTING.md:

1. Read the CLA page and download the agreement it links to.
2. Fill in section 2 (the copyright owner) and the signature block, and sign.
3. Deliver it to 7x by mail, a scan by e-mail, or fax, as the agreement says; if by e-mail, make sure it arrived.
4. Mention in your pull request that your CLA is signed; the pull request template has a checkbox.

"The CLA will be signed once for all your future contributions."

Questions students ask #

I am a student. Who owns what I write? Usually you. But if you write it as part of a job or an internship, your employer may have rights to it; then you need its permission, its waiver, or the company signs (as CONTRIBUTING.md summarizes the agreement). If your school or course has rules on intellectual property for course work, read them or ask your teacher before you assign copyright.

Can I keep my extension under my own name? Yes. Publish it in your own repository; the CLA does not apply. The GPL still applies when you hand an extension to others (Contribute extensions back).

Can I take a contribution back later? No. You cannot withdraw it or set conditions on it.

Does the CLA replace the GPL? No. Your contribution is released under the GPL like the rest of Exponential; for the kernel, the CLA additionally assigns its copyright to the Exponential Foundation and 7x.

Do I need it for a translation or a documentation fix? They are contributions to the kernel repository, and CONTRIBUTING.md lists "documentation files, translations" among the kinds of code the CLA page names. Sign it, or ask in your pull request.

Related pages #

• Contributing as a student
• Develop with Git
• Your first contribution, step by step
• Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.