Skip to content

Be a bit more strong with getting the CLA signed #153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 27, 2017
Merged

Be a bit more strong with getting the CLA signed #153

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions committing.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,11 +148,10 @@ and redistribute their code.
Contributor Licensing Agreements
--------------------------------

It's unlikely bug fixes will require a `Contributor Licensing Agreement`_
unless they touch a *lot* of code. For new features, it is preferable to
ask that the contributor submit a signed CLA to the PSF as the associated
comments, docstrings and documentation are far more likely to reach a
copyrightable standard.
Always get a `Contributor Licensing Agreement`_ (CLA) signed unless the
change has no possible intellectual property associated with it (e.g. fixing
a spelling mistake in documentation). Otherwise it is simply safer from a
legal standpoint to require the contributor to sign the CLA.

These days, the CLA can be signed electronically through the form linked
above, and this process is strongly preferred to the old mechanism that
Expand Down