|
| 1 | +*********************************** |
| 2 | +Contributing code to fortnet-python |
| 3 | +*********************************** |
| 4 | + |
| 5 | +fortnet-python is an open source project, and everyone is welcome to contribute |
| 6 | +improvements and extensions, provided they are willing to provide their |
| 7 | +changes under the same license as fortnet-python itself (BSD-2-Clause). |
| 8 | + |
| 9 | + |
| 10 | +How to contribute |
| 11 | +================= |
| 12 | + |
| 13 | +The preferred method is to fork the project on `github |
| 14 | +<https://github.com/vanderhe/fortnet-python/>`_), make your changes and then |
| 15 | +create a pull request. Your changes should be based on the default branch. |
| 16 | + |
| 17 | + |
| 18 | +Attribution |
| 19 | +=========== |
| 20 | + |
| 21 | +Every contributor is welcome to be listed in the `AUTHORS.rst` file. List |
| 22 | +yourself by including a change to `AUTHORS.rst` in your pull |
| 23 | +request. Contributors should be ordered alphabetically by their family name. |
| 24 | + |
| 25 | + |
| 26 | +Developer certificate of origin |
| 27 | +=============================== |
| 28 | + |
| 29 | +When you contribute to the project, your contribution must align with the |
| 30 | +`Developer Certificate of Origin |
| 31 | +<https://developercertificate.org/>`_:: |
| 32 | + |
| 33 | + Developer Certificate of Origin |
| 34 | + Version 1.1 |
| 35 | + |
| 36 | + Copyright (C) 2004, 2006 The Linux Foundation and its contributors. |
| 37 | + 1 Letterman Drive |
| 38 | + Suite D4700 |
| 39 | + San Francisco, CA, 94129 |
| 40 | + |
| 41 | + Everyone is permitted to copy and distribute verbatim copies of this |
| 42 | + license document, but changing it is not allowed. |
| 43 | + |
| 44 | + |
| 45 | + Developer's Certificate of Origin 1.1 |
| 46 | + |
| 47 | + By making a contribution to this project, I certify that: |
| 48 | + |
| 49 | + (a) The contribution was created in whole or in part by me and I |
| 50 | + have the right to submit it under the open source license |
| 51 | + indicated in the file; or |
| 52 | + |
| 53 | + (b) The contribution is based upon previous work that, to the best |
| 54 | + of my knowledge, is covered under an appropriate open source |
| 55 | + license and I have the right under that license to submit that |
| 56 | + work with modifications, whether created in whole or in part |
| 57 | + by me, under the same open source license (unless I am |
| 58 | + permitted to submit under a different license), as indicated |
| 59 | + in the file; or |
| 60 | + |
| 61 | + (c) The contribution was provided directly to me by some other |
| 62 | + person who certified (a), (b) or (c) and I have not modified |
| 63 | + it. |
| 64 | + |
| 65 | + (d) I understand and agree that this project and the contribution |
| 66 | + are public and that a record of the contribution (including all |
| 67 | + personal information I submit with it, including my sign-off) is |
| 68 | + maintained indefinitely and may be redistributed consistent with |
| 69 | + this project or the open source license(s) involved. |
| 70 | + |
| 71 | + |
| 72 | +By issuing a pull request or contributing code in any other ways to the project, |
| 73 | +you explicitly declare that your contribution is in accordance with the |
| 74 | +Developer's Certificate of Origin as described above. |
| 75 | + |
| 76 | +Please, also make sure, that all of your git commits contain your real name and |
| 77 | +email address; pseudonyms and anonymous contributions unfortunately can not be |
| 78 | +accepted. |
0 commit comments