| PyCrypto Code Submission Requirements - Rev. D |
| |
| Last updated: 2010-11-29 |
| |
| In an effort to further clarify PyCrypto's licensing terms, anyone submitting |
| code to PyCrypto must be able to certify the following (taken from the Linux |
| kernel's SubmittingPatches file): |
| |
| Developer's Certificate of Origin 1.1 |
| |
| By making a contribution to this project, I certify that: |
| |
| (a) The contribution was created in whole or in part by me and I |
| have the right to submit it under the open source license |
| indicated in the file; or |
| |
| (b) The contribution is based upon previous work that, to the best |
| of my knowledge, is covered under an appropriate open source |
| license and I have the right under that license to submit that |
| work with modifications, whether created in whole or in part |
| by me, under the same open source license (unless I am |
| permitted to submit under a different license), as indicated |
| in the file; or |
| |
| (c) The contribution was provided directly to me by some other |
| person who certified (a), (b) or (c) and I have not modified |
| it. |
| |
| (d) I understand and agree that this project and the contribution |
| are public and that a record of the contribution (including all |
| personal information I submit with it, including my sign-off) is |
| maintained indefinitely and may be redistributed consistent with |
| this project or the open source license(s) involved. |
| |
| In addition, all new code contributed to PyCrypto must be dedicated to the |
| public domain as follows: |
| |
| The contents of this file are dedicated to the public domain. To the extent |
| that dedication to the public domain is not available, everyone is granted a |
| worldwide, perpetual, royalty-free, non-exclusive license to exercise all |
| rights associated with the contents of this file for any purpose whatsoever. |
| No rights are reserved. |
| |
| === EOF === |
