CLA.md
Rama main · réplica de lectura del repositorio original.
# Skiff Contributor License Agreement — Individual
**Version 1.1**
Thank you for contributing to Skiff. This agreement sets out the terms under
which your contribution is accepted. It is based on the Apache Software
Foundation's Individual Contributor License Agreement, the most widely used
agreement of its kind, with additions that reflect this project's specific
situation.
Please read it. It is meant to be understandable without a lawyer.
---
## The short version
- **You keep the copyright in everything you write.** Nothing is assigned away.
You can reuse your own contribution anywhere else, for anything, forever.
- **You give the Project Owner permission to use your contribution**, including
in versions of Skiff that are not open source and are sold commercially.
- **You confirm the work is actually yours to give** — not your employer's, not
copied from elsewhere, and not something you lack the right to submit.
- **In return, the Project Owner commits** that contributions accepted into the
open-source project stay available under the open-source license. This
agreement adds a permission; it does not take the project closed.
The third point is the one that matters most. If it isn't true, say so before
opening the pull request rather than after.
---
## Why this exists
Skiff is licensed under the **GNU Affero General Public License v3.0**. There is
also a commercial edition planned, which will not be open source.
The AGPL is deliberately strict: code contributed under it cannot be used in a
closed-source product without the contributor's permission. That is a good
property, and it is why Skiff is licensed that way — it stops anyone taking
Skiff, closing it, and selling it.
But it applies to the maintainer too. Without this agreement, a single accepted
pull request would mean the maintainer could never use that code in a commercial
edition without going back and asking you individually. With a hundred
contributors that becomes impossible, and the commercial edition intended to
fund the open-source work quietly stops being viable.
This agreement solves that once, up front, instead of by chasing people down
years later. It is the same arrangement used by MongoDB, Grafana, GitLab,
Sentry and Elastic, among many others.
**What this agreement does not do:** it does not let anyone take your
contribution out of the open-source project. Skiff stays open source under the
AGPL. See section 10, which puts that commitment in the agreement itself rather
than leaving it as a promise.
---
## The agreement
By submitting a Contribution to this project, You accept and agree to the
following terms and conditions for Your present and future Contributions.
### 1. Definitions
**"You"** or **"Your"** means the individual submitting the Contribution. If You
are submitting on behalf of an employer or other legal entity, see section 19 —
a separate corporate agreement is required.
**"Project Owner"** means Priyanshu, the copyright holder and maintainer of
Skiff, together with any successor, assignee, or legal entity to which the
Skiff project or its rights are transferred, as described in section 13.
**"Project"** means Skiff, in all of its editions, whether open source or not,
including any product, service, or derivative work built from it.
**"Contribution"** means any original work of authorship, including any
modification of or addition to an existing work, and including any associated
documentation, configuration, test, design, or artwork, that is intentionally
submitted by You to the Project Owner for inclusion in, or documentation of,
the Project. "Submitted" means any form of electronic, verbal, or written
communication sent to the Project Owner or its representatives, including but
not limited to communication on source code repositories, issue trackers,
discussion forums, and mailing lists, but excluding communication that is
conspicuously marked or otherwise designated in writing by You as
**"Not a Contribution"**.
### 2. Grant of copyright license
Subject to the terms of this agreement, You grant to the Project Owner and to
recipients of software distributed by the Project Owner 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 Contribution and such derivative works.
**This license expressly includes the right to license and distribute Your
Contribution, and derivative works of it, under license terms of the Project
Owner's choosing, including proprietary, closed-source and commercial terms,
and to do so without any obligation to publish source code and without any
payment or accounting to You.**
**You retain all right, title and interest in and to Your Contribution.** This
is a license, not an assignment. Nothing here limits Your ability to use Your
own Contribution however You wish, including in other projects, under other
licenses, or commercially.
### 3. Grant of patent license
Subject to the terms of this agreement, You grant to the Project Owner and to
recipients of software distributed by the Project Owner a perpetual, worldwide,
non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this
section) patent license to make, have made, use, offer to sell, sell, import,
and otherwise transfer Your Contribution.
This 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 work to which it was submitted.
If any entity institutes patent litigation against You or any other entity
alleging that Your Contribution, or the work to which You contributed,
constitutes direct or contributory patent infringement, then any patent licenses
granted to that entity under this agreement terminate as of the date such
litigation is filed.
### 4. Moral rights
To the fullest extent permitted by applicable law, You waive, and agree not to
assert or enforce against the Project Owner or its licensees, any moral rights,
rights of attribution or integrity, or similar rights You may have in Your
Contribution — including any rights arising under section 57 of the Indian
Copyright Act, 1957 or equivalent provisions in other jurisdictions.
Where such rights cannot be waived under applicable law, You agree not to assert
them in a way that would prevent the Project Owner from exercising the licenses
granted in sections 2 and 3.
This does not mean You go uncredited. It means the Project Owner can modify,
refactor, translate, or relicense Your Contribution without needing Your
approval each time.
### 5. Your representations
You represent and warrant that:
**(a) Original work.** Each Contribution is Your original creation, or You have
the right to submit it under the terms of this agreement.
**(b) Authority.** You are legally entitled to grant the licenses in sections 2
and 3, and doing so does not breach any agreement You are party to.
**(c) Employer rights.** If Your employer or any other party has rights to
intellectual property You create — including anything You write using company
equipment, on company time, using company confidential information, or within
the scope of Your employment or engagement — You have either received written
permission to make the Contribution on their behalf, or they have waived such
rights, or they have executed the corporate agreement described in section 19.
**If you are unsure whether this applies to you, ask your employer before
contributing.** This is the single most common source of dispute in
open-source projects.
**(d) No conflicting obligations.** Your Contribution is not subject to any
license, contract, non-disclosure obligation, or court order that conflicts
with the licenses granted here.
**(e) Third-party rights.** To the best of Your knowledge, Your Contribution
does not violate any third party's copyrights, trademarks, patents, trade
secrets, or other intellectual property rights.
**(f) No malicious code.** Your Contribution does not knowingly contain any
back door, malicious code, undisclosed telemetry, or intentional security
weakness. Given what Skiff does, this is not a formality.
**(g) AI-assisted contributions.** If any part of Your Contribution was
generated with the assistance of an AI coding tool, You represent that You have
reviewed and understood it, that You have the right to submit it under this
agreement, and that You are not aware of it reproducing third-party code in a
way that would conflict with sections 5(a) or 5(e). You do not need to disclose
that You used such a tool; You do need the representation to be true.
### 6. Third-party material
If You wish to submit work that is not Your original creation, You may submit it
separately from any Contribution, identifying the complete details of its source
and of any license or other restriction of which You are personally aware, and
conspicuously marking the work as **"Submitted on behalf of a third party:
[name here]"**.
### 7. Feedback, ideas and suggestions
Any feedback, ideas, suggestions, bug reports, or feature requests You provide
about the Project may be used by the Project Owner without restriction,
attribution, or compensation. This section exists so that discussion in issues
and forums does not create ambiguity about who may act on an idea. It does not
apply to code, which is covered by sections 2 and 3.
### 8. Prior contributions
This agreement applies to **all** Contributions You have submitted to the
Project, including any submitted before You accepted this agreement, as well as
all Contributions You submit afterwards. If You do not intend a prior
Contribution to be covered, You must say so in writing at the time You sign.
### 9. No obligation on the Project Owner
The decision to include Your Contribution in the Project is entirely at the
discretion of the Project Owner. This agreement does not obligate the Project
Owner to use, distribute, maintain, or support Your Contribution, and Your
Contribution may be modified or removed at any time.
### 10. The Project Owner's commitment to you
The Project Owner commits that any Contribution accepted into an open-source
edition of Skiff will continue to be made available under an OSI-approved
open-source license.
This does not restrict the licenses granted in sections 2 and 3 — the Project
Owner may additionally license Your Contribution on any terms, including
proprietary ones. It means only that the open-source edition of Skiff does not
become closed, and that Your work remains available to the community You gave it
to.
### 11. No trademark rights
This agreement grants no rights to use the name "Skiff", any Skiff logo, or any
other trade name, trademark, service mark, or product name of the Project Owner,
except as required for reasonable and customary use in describing the origin of
the work.
### 12. No warranty
Unless required by applicable law or agreed to in writing, You provide Your
Contribution 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. This does not limit the representations You make in section
5, which are given as representations rather than warranties of quality.
### 13. Assignment and successors
The Project Owner may assign this agreement, and the licenses granted under it,
to any successor in interest to the Project — including a company incorporated
by the Project Owner to hold the Project, an acquirer of the Project, or a
foundation to which the Project is donated — without needing Your further
consent.
This exists so that incorporating a company or transferring the Project later
does not require re-collecting every signature. Your rights under section 10
bind any such successor.
You may not assign this agreement.
### 14. Notification
You agree to notify the Project Owner promptly of any facts or circumstances of
which You become aware that would make the representations in section 5
inaccurate in any respect.
### 15. Electronic acceptance
You agree that accepting this agreement by an electronic method — including
posting the acceptance sentence set out below as a comment on a pull request, or
clicking an acceptance control — constitutes Your signature, is intended by You
to have the same legal effect as a handwritten signature, and is admissible as
evidence.
You agree not to contest the validity or enforceability of this agreement solely
on the grounds that it was accepted electronically or that it does not bear a
handwritten signature. This is intended to take effect as an electronic record
and electronic signature under the Information Technology Act, 2000 and any
equivalent legislation applicable to You.
The record of Your acceptance — Your account identifier, the date, and the pull
request on which You accepted — is retained by the Project Owner as evidence of
this agreement.
### 16. Term and survival
The licenses granted in sections 2 and 3 are irrevocable and perpetual. They
survive any termination of this agreement, any withdrawal of Your participation
in the Project, and any removal of Your Contribution from the Project.
Once a Contribution has been submitted and accepted, You cannot later withdraw
the permission granted here. This is deliberate: software that could have its
foundations removed retroactively cannot be relied on by anyone.
### 17. Severability, waiver, entire agreement
If any provision of this agreement is held unenforceable, that provision shall
be modified to the minimum extent necessary to make it enforceable, and the
remaining provisions shall remain in full force. In particular, if the scope of
any license granted here is held to be excessive, that license shall be
construed as granting the broadest scope permitted by law.
No failure or delay by the Project Owner in exercising any right under this
agreement operates as a waiver of it.
This agreement, together with the applicable open-source license of the Project,
constitutes the entire agreement between You and the Project Owner concerning
Your Contributions, and supersedes any prior understanding on that subject.
### 18. Governing law and jurisdiction
This agreement is governed by and construed in accordance with the laws of
India, without regard to its conflict of law provisions. The courts at
Ahmedabad, Gujarat, India shall have exclusive jurisdiction over any dispute
arising out of or relating to this agreement.
### 19. Corporate contributions
If You are contributing in the course of employment, or on behalf of a company
or other legal entity, that entity must sign the
[Corporate Contributor License Agreement](./CLA-CORPORATE.md) in addition to
this one. Open an issue and it can be arranged — it is a short document and
usually a matter of one email to whoever handles contracts.
If you are contributing in your personal time, on your own equipment, and
outside the scope of your employment, this individual agreement is enough.
---
## How to sign
You do not sign a document or send anything by email.
When you open your first pull request, a bot will comment asking you to confirm.
Reply on that pull request with exactly:
```
I have read the CLA Document and I hereby sign the CLA
```
Your account identifier, the date, and the pull request are recorded. It is a
one-time step — later pull requests are recognised automatically.
---
## Questions
If anything here worries you, open an issue and ask before contributing. A
question about the agreement is not an imposition; it is a reasonable thing to
want cleared up before granting permissions. It will not be held against your
pull request.