|
| 1 | +# Contributing to OVH Functions |
| 2 | + |
| 3 | +This project accepts contributions. In order to contribute, you should |
| 4 | +pay attention to a few things: |
| 5 | + |
| 6 | +1. your code must be fully documented |
| 7 | +2. your work must be signed |
| 8 | +3. GitHub Pull Requests |
| 9 | + |
| 10 | +## Submitting Modifications: |
| 11 | + |
| 12 | +The contributions should be github Pull Requests. The guidelines are the same |
| 13 | +as the patch submission for the Linux kernel except for the DCO which |
| 14 | +is defined below. The guidelines are defined in the |
| 15 | +'SubmittingPatches' file, available in the directory 'Documentation' |
| 16 | +of the Linux kernel source tree. |
| 17 | + |
| 18 | +It can be accessed online too: |
| 19 | + |
| 20 | +https://www.kernel.org/doc/Documentation/SubmittingPatches |
| 21 | + |
| 22 | +You can submit your patches via GitHub |
| 23 | + |
| 24 | +## Licensing for new files: |
| 25 | + |
| 26 | +Functions is licensed under a (modified) BSD license. Anything contributed to |
| 27 | +OVH Functions must be released under this license. |
| 28 | + |
| 29 | +When introducing a new file into the project, please make sure it has a |
| 30 | +copyright header making clear under which license it''s being released. |
| 31 | + |
| 32 | +## Developer Certificate of Origin: |
| 33 | + |
| 34 | +``` |
| 35 | +To improve tracking of contributions to this project we will use a |
| 36 | +process modeled on the modified DCO 1.1 and use a "sign-off" procedure |
| 37 | +on patches that are being contributed. |
| 38 | +
|
| 39 | +The sign-off is a simple line at the end of the explanation for the |
| 40 | +patch, which certifies that you wrote it or otherwise have the right |
| 41 | +to pass it on as an open-source patch. The rules are pretty simple: |
| 42 | +if you can certify the below: |
| 43 | +
|
| 44 | +By making a contribution to this project, I certify that: |
| 45 | +
|
| 46 | +(a) The contribution was created in whole or in part by me and I have |
| 47 | + the right to submit it under the open source license indicated in |
| 48 | + the file; or |
| 49 | +
|
| 50 | +(b) The contribution is based upon previous work that, to the best of |
| 51 | + my knowledge, is covered under an appropriate open source License |
| 52 | + and I have the right under that license to submit that work with |
| 53 | + modifications, whether created in whole or in part by me, under |
| 54 | + the same open source license (unless I am permitted to submit |
| 55 | + under a different license), as indicated in the file; or |
| 56 | +
|
| 57 | +(c) The contribution was provided directly to me by some other person |
| 58 | + who certified (a), (b) or (c) and I have not modified it. |
| 59 | +
|
| 60 | +(d) The contribution is made free of any other party''s intellectual |
| 61 | + property claims or rights. |
| 62 | +
|
| 63 | +(e) I understand and agree that this project and the contribution are |
| 64 | + public and that a record of the contribution (including all |
| 65 | + personal information I submit with it, including my sign-off) is |
| 66 | + maintained indefinitely and may be redistributed consistent with |
| 67 | + this project or the open source license(s) involved. |
| 68 | + then you just add a line saying |
| 69 | +``` |
| 70 | +Signed-off-by: Random J Developer <random@developer.org> |
| 71 | +``` |
| 72 | + using your real name (sorry, no pseudonyms or anonymous contributions.) |
| 73 | +
|
0 commit comments