diff options
| -rw-r--r-- | Misc/bugrelease.txt | 26 | ||||
| -rw-r--r-- | Misc/legalfaq.txt | 77 | ||||
| -rw-r--r-- | Misc/wetsign.txt | 70 |
3 files changed, 173 insertions, 0 deletions
diff --git a/Misc/bugrelease.txt b/Misc/bugrelease.txt new file mode 100644 index 0000000..19145ae --- /dev/null +++ b/Misc/bugrelease.txt @@ -0,0 +1,26 @@ +If you send us a minor contribution by email (bug fix, patch, +suggestion, or other minor enhancement), please incorporate the +following paragraphs in your email message. For more substantial +contributions, we may require a wet signature; see the separate form +(wetsign.txt). See the contribution policy FAQ (legalfaq.txt) for +more information. + +""" +I confirm that, to the best of my knowledge and belief, this +contribution is free of any claims of third parties under +copyright, patent or other rights or interests ("claims"). To +the extent that I have any such claims, I hereby grant to CNRI a +nonexclusive, irrevocable, royalty-free, worldwide license to +reproduce, distribute, perform and/or display publicly, prepare +derivative versions, and otherwise use this contribution as part +of the Python software and its related documentation, or any +derivative versions thereof, at no cost to CNRI or its licensed +users, and to authorize others to do so. + +I acknowledge that CNRI may, at its sole discretion, decide +whether or not to incorporate this contribution in the Python +software and its related documentation. I further grant CNRI +permission to use my name and other identifying information +provided to CNRI by me for use in connection with the Python +software and its related documentation. +""" diff --git a/Misc/legalfaq.txt b/Misc/legalfaq.txt new file mode 100644 index 0000000..0233149 --- /dev/null +++ b/Misc/legalfaq.txt @@ -0,0 +1,77 @@ +Frequently Asked Questions about CNRI's legal policy regarding +contributions to Python + +If you have a question that isn't answered here, please write +<guido@python.org> + +Q. What are the legal requirements for contributions to Python? + +CNRI's lawyers recommend that we collect legal agreements for all new +contributions. For small contributions, a simple two-paragraph note +in the email containing the contribution suffices (see +bugrelease.txt). For more substantial contribution, we require a +mailed signed copy of a simple form (see wetsign.txt). We have tried +to make the legal language as simple as possible. + +Q. Why does CNRI require this? + +In order to make it possible to protect Python against potential +infringements. Other organizations that distribute free software do +the similar things; for example, the GNU project requires a much more +strongly worded form, assigning all copyrights to the Free Software +Foundation, for all contributions to GNU software. + +Q. When is a contribution small enough to require only an email note? + +This is determined by us on a per-contribution basis. Up to 20 lines +of patches typically qualify as small; however if you manage to do +something truly spectacular in 20 lines or less we may ask you to send +in the signature form anyway. + +Q. I have contributed to Python in the past. Should I sign and mail +in a form now? + +Yes, please. We are in the process of getting wet signatures for all +major contributions to Python up to now. If you contributed a module +or more, we'll try to get in touch with you; you can save us the +effort and mail us the signed form right away! + +Q. Do I have to accurately list everything I contributed? + +No. If you made multiple contributions in the past, it is sufficient +to write in the form under "description" something like "everything +I've contributed until <date>." If you continue to make +significant contributions in the future, you can send us an update +form using a similar formulation every once in a while. + +Q. Can I send in a form to cover all my future contributions? + +No. However it's okay if you send in a form, say, once a year, +covering all your contributions from the last time you sent one in +until the date you sign the new form. + +Q. Does the form protect me against copyright or patent infringement +suits? + +If you infringe somebody's rights, no form in the world that you sign +can protect you. The form only protects CNRI, because the act of +collecting the forms shows that CNRI is doing "due diligence" +regarding asserting the origin of contributions. + +Q. Does the form protect me against claims from damage resulting from +use of my contribution? + +We have reluctantly added a paragraph wherein you disclaim all +warranties etc. You may see this as some form of protection. However +the law regarding such disclaimers is complicated and varies widely +between states and countries, and the particular disclaimer used on +the form may not cover you in all cases. + +Q. Does the form transfer my copyrights to CNRI? + +No. CNRI only gets certain non-exclusive rights. See the form for +the exact list of rights. + +Q. If I don't sign, will my past contributions be removed from Python? + +That is up to CNRI's lawyers to decide. diff --git a/Misc/wetsign.txt b/Misc/wetsign.txt new file mode 100644 index 0000000..d8c27bb --- /dev/null +++ b/Misc/wetsign.txt @@ -0,0 +1,70 @@ +Print this form, fill it out, sign it, and mail to CNRI at the +following address: + + Python Developers + Corporation for National Research Initiatives + 1895 Preston White Drive, Suite 101 + Reston, VA 20191 + USA + +For small contributions you may send a note with your contribution via +email instead (see bugrelease.txt). + + +PYTHON LICENSE AGREEMENT + +CONTRIBUTION DESCRIPTION: + + ________________________________________ + + ________________________________________ + + ________________________________________ + + ________________________________________ + + (use back if more space is required) + + +CNRI acknowledges, with thanks, the receipt by CNRI from Licensee of +the above-described Contribution ("Contribution") to the Python +software and its related documentation. + +Licensee confirms to CNRI that, to the best of Licensee's knowledge +and belief, the Contribution is free of any claims of parties other +than Licensee under copyright, patent or other rights or interests +("claims"). To the extent that Licensee has any such claims, Licensee +hereby grants to CNRI a nonexclusive, irrevocable, royalty-free, +worldwide license to reproduce, distribute, perform and/or display +publicly, prepare derivative versions, and otherwise use the +Contribution as part of the Python software and its related +documentation, or any derivative versions thereof, at no cost to CNRI +or its licensed users and without any accounting obligation to +Licensee of any kind, and to authorize others to do so. + +Licensee hereby acknowledges that CNRI may, at its sole discretion, +decide whether or not to incorporate the Contribution in the Python +software and its related documentation. Licensee further grants CNRI +permission to use Licensee's name and other identifying information +provided to CNRI by Licensee for use in connection with the Python +software and its related documentation. + +EXCEPT AS OTHERWISE PROVIDED HEREIN, LICENSEE MAKES NO REPRESENTATIONS +OR WARRANTIES, EXPRESS OR IMPLIED, WITH RESPECT TO THE ABOVE-DESCRIBED +CONTRIBUTION. BY WAY OF EXAMPLE, BUT NOT LIMITATION, LICENSEE MAKES +NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR +FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT SHALL LICENSEE BE +LIABLE TO USERS OF THE CONTRIBUTION FOR ANY INCIDENTAL, SPECIAL OR +CONSEQUENTIAL DAMAGES OR LOSS WHATSOEVER AS A RESULT OF USING, +MODIFYING OR DISTRIBUTING THE CONTRIBUTION, OR ANY DERIVATIVE THEREOF, +EVEN IF ADVISED OF THE POSSIBILITY THEREOF. + +READ AND AGREED, + +LICENSEE'S SIGNATURE: + +Date: + +Name (print): + +E-mail address: |