|
| 1 | +# Contributing to project ovh-documentation-toolkit |
| 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 follow the coding style rules |
| 7 | +2. your code must be documented |
| 8 | +3. your work must be signed (see below) |
| 9 | +4. you may contribute through GitHub Pull Requests |
| 10 | + |
| 11 | +All contributions are welcome. However, keeping in mind the primary goal |
| 12 | +of this project, which is to provide a stylekit for the _OVH_ brand, we |
| 13 | +**strongly recommend** that you submit a RFC pull request or reach out |
| 14 | +to the [UX team on Gitter](https://gitter.im/ovh/ux) to discuss your |
| 15 | +proposal first. |
| 16 | + |
| 17 | +# Coding style rules |
| 18 | + |
| 19 | +* Use the [BEM CSS selector naming convention](https://en.bem.info/methodology/naming-convention/). |
| 20 | +* Lint your code with stylelint: `npm run lint`. |
| 21 | +* Test your build: `npm run build`. |
| 22 | + |
| 23 | +# Submitting Modifications |
| 24 | + |
| 25 | +The contributions should be submitted through Github Pull Requests and |
| 26 | +follow the DCO which is defined below. |
| 27 | + |
| 28 | +# Licensing for new files |
| 29 | + |
| 30 | +ovh-documentation-toolkit is licensed under a modified BSD-3-Clause license. Anything |
| 31 | +contributed to ovh-documentation-toolkit must be released under this license. |
| 32 | + |
| 33 | +When introducing a new file into the project, please make sure it has a |
| 34 | +copyright header making clear under which license it's being released. |
| 35 | + |
| 36 | +# Developer Certificate of Origin (DCO) |
| 37 | + |
| 38 | +To improve tracking of contributions to this project we will use a |
| 39 | +process modeled on the modified DCO 1.1 and use a "sign-off" procedure |
| 40 | +on patches that are being emailed around or contributed in any other |
| 41 | +way. |
| 42 | + |
| 43 | +The sign-off is a simple line at the end of the explanation for the |
| 44 | +patch, which certifies that you wrote it or otherwise have the right |
| 45 | +to pass it on as an open-source patch. The rules are pretty simple: |
| 46 | +if you can certify the below: |
| 47 | + |
| 48 | +``` |
| 49 | +By making a contribution to this project, I certify that: |
| 50 | +
|
| 51 | + (a) The contribution was created in whole or in part by me and I have |
| 52 | + the right to submit it under the open source license indicated in |
| 53 | + the file; or |
| 54 | +
|
| 55 | + (b) The contribution is based upon previous work that, to the best of |
| 56 | + my knowledge, is covered under an appropriate open source License |
| 57 | + and I have the right under that license to submit that work with |
| 58 | + modifications, whether created in whole or in part by me, under |
| 59 | + the same open source license (unless I am permitted to submit |
| 60 | + under a different license), as indicated in the file; or |
| 61 | +
|
| 62 | + (c) The contribution was provided directly to me by some other person |
| 63 | + who certified (a), (b) or (c) and I have not modified it. |
| 64 | +
|
| 65 | + (d) The contribution is made free of any other party's intellectual |
| 66 | + property claims or rights. |
| 67 | +
|
| 68 | + (e) I understand and agree that this project and the contribution are |
| 69 | + public and that a record of the contribution (including all |
| 70 | + personal information I submit with it, including my sign-off) is |
| 71 | + maintained indefinitely and may be redistributed consistent with |
| 72 | + this project or the open source license(s) involved. |
| 73 | +``` |
| 74 | + |
| 75 | +then you just add a line saying |
| 76 | + |
| 77 | +``` |
| 78 | +Signed-off-by: Random J Developer <[email protected]> |
| 79 | +``` |
| 80 | + |
| 81 | +using your real name (sorry, no pseudonyms or anonymous contributions.) |
| 82 | + |
| 83 | + |
| 84 | +# Setup your environment |
| 85 | + |
| 86 | +Please refer to the [README](README.md). |
| 87 | + |
| 88 | +## NPM |
| 89 | + |
| 90 | +For those using npm instead of yarn here is a list of equivalences: <https://yarnpkg.com/en/docs/migrating-from-npm> |
| 91 | + |
| 92 | +## Commits |
| 93 | + |
| 94 | +All commits in this project must follow this specific message convention: <https://gist.github.com/stephenparish/9941e89d80e2bc58a153> |
0 commit comments