| Guido van Rossum | fd6aabb | 1999-11-05 15:21:08 +0000 | [diff] [blame] | 1 | Frequently Asked Questions about CNRI's legal policy regarding |
| 2 | contributions to Python |
| 3 | |
| 4 | If you have a question that isn't answered here, please write |
| 5 | <guido@python.org> |
| 6 | |
| 7 | Q. What are the legal requirements for contributions to Python? |
| 8 | |
| 9 | CNRI's lawyers recommend that we collect legal agreements for all new |
| 10 | contributions. For small contributions, a simple two-paragraph note |
| 11 | in the email containing the contribution suffices (see |
| 12 | bugrelease.txt). For more substantial contribution, we require a |
| 13 | mailed signed copy of a simple form (see wetsign.txt). We have tried |
| 14 | to make the legal language as simple as possible. |
| 15 | |
| 16 | Q. Why does CNRI require this? |
| 17 | |
| 18 | In order to make it possible to protect Python against potential |
| 19 | infringements. Other organizations that distribute free software do |
| 20 | the similar things; for example, the GNU project requires a much more |
| 21 | strongly worded form, assigning all copyrights to the Free Software |
| 22 | Foundation, for all contributions to GNU software. |
| 23 | |
| 24 | Q. When is a contribution small enough to require only an email note? |
| 25 | |
| 26 | This is determined by us on a per-contribution basis. Up to 20 lines |
| 27 | of patches typically qualify as small; however if you manage to do |
| 28 | something truly spectacular in 20 lines or less we may ask you to send |
| 29 | in the signature form anyway. |
| 30 | |
| 31 | Q. I have contributed to Python in the past. Should I sign and mail |
| 32 | in a form now? |
| 33 | |
| 34 | Yes, please. We are in the process of getting wet signatures for all |
| 35 | major contributions to Python up to now. If you contributed a module |
| 36 | or more, we'll try to get in touch with you; you can save us the |
| 37 | effort and mail us the signed form right away! |
| 38 | |
| 39 | Q. Do I have to accurately list everything I contributed? |
| 40 | |
| 41 | No. If you made multiple contributions in the past, it is sufficient |
| 42 | to write in the form under "description" something like "everything |
| 43 | I've contributed until <date>." If you continue to make |
| 44 | significant contributions in the future, you can send us an update |
| 45 | form using a similar formulation every once in a while. |
| 46 | |
| 47 | Q. Can I send in a form to cover all my future contributions? |
| 48 | |
| 49 | No. However it's okay if you send in a form, say, once a year, |
| 50 | covering all your contributions from the last time you sent one in |
| 51 | until the date you sign the new form. |
| 52 | |
| 53 | Q. Does the form protect me against copyright or patent infringement |
| 54 | suits? |
| 55 | |
| 56 | If you infringe somebody's rights, no form in the world that you sign |
| 57 | can protect you. The form only protects CNRI, because the act of |
| 58 | collecting the forms shows that CNRI is doing "due diligence" |
| 59 | regarding asserting the origin of contributions. |
| 60 | |
| 61 | Q. Does the form protect me against claims from damage resulting from |
| 62 | use of my contribution? |
| 63 | |
| 64 | We have reluctantly added a paragraph wherein you disclaim all |
| 65 | warranties etc. You may see this as some form of protection. However |
| 66 | the law regarding such disclaimers is complicated and varies widely |
| 67 | between states and countries, and the particular disclaimer used on |
| 68 | the form may not cover you in all cases. |
| 69 | |
| 70 | Q. Does the form transfer my copyrights to CNRI? |
| 71 | |
| 72 | No. CNRI only gets certain non-exclusive rights. See the form for |
| 73 | the exact list of rights. |
| 74 | |
| 75 | Q. If I don't sign, will my past contributions be removed from Python? |
| 76 | |
| 77 | That is up to CNRI's lawyers to decide. |