|  | 
| 1 | 1 | ## Contributing to this Project | 
| 2 | 2 | 
 | 
| 3 | 3 | OpenSearch is a community project that is built and maintained by people just like **you**.  | 
| 4 |  | -[This document](https://github.com/opensearch-project/.github/blob/main/CONTRIBUTING.md) explains how you can contribute to this and related projects. | 
|  | 4 | +[This document](https://github.com/opensearch-project/.github/blob/main/CONTRIBUTING.md) explains how you can contribute to this and related projects. | 
|  | 5 | + | 
|  | 6 | +## Developer Certificate of Origin | 
|  | 7 | + | 
|  | 8 | +OpenSearch is an open source product released under the Apache 2.0 license (see either [the Apache site](https://www.apache.org/licenses/LICENSE-2.0) or the [LICENSE.txt file](LICENSE.txt)). The Apache 2.0 license allows you to freely use, modify, distribute, and sell your own products that include Apache 2.0 licensed software. | 
|  | 9 | + | 
|  | 10 | +We respect intellectual property rights of others and we want to make sure all incoming contributions are correctly attributed and licensed. A Developer Certificate of Origin (DCO) is a lightweight mechanism to do that. | 
|  | 11 | + | 
|  | 12 | +The DCO is a declaration attached to every contribution made by every developer. In the commit message of the contribution, the developer simply adds a `Signed-off-by` statement and thereby agrees to the DCO, which you can find below or at [DeveloperCertificate.org](http://developercertificate.org/). | 
|  | 13 | + | 
|  | 14 | +``` | 
|  | 15 | +Developer's Certificate of Origin 1.1 | 
|  | 16 | +
 | 
|  | 17 | +By making a contribution to this project, I certify that: | 
|  | 18 | +
 | 
|  | 19 | +(a) The contribution was created in whole or in part by me and I | 
|  | 20 | +    have the right to submit it under the open source license | 
|  | 21 | +    indicated in the file; or | 
|  | 22 | +
 | 
|  | 23 | +(b) The contribution is based upon previous work that, to the | 
|  | 24 | +    best of my knowledge, is covered under an appropriate open | 
|  | 25 | +    source license and I have the right under that license to | 
|  | 26 | +    submit that work with modifications, whether created in whole | 
|  | 27 | +    or in part by me, under the same open source license (unless | 
|  | 28 | +    I am permitted to submit under a different license), as | 
|  | 29 | +    Indicated in the file; or | 
|  | 30 | +
 | 
|  | 31 | +(c) The contribution was provided directly to me by some other | 
|  | 32 | +    person who certified (a), (b) or (c) and I have not modified | 
|  | 33 | +    it. | 
|  | 34 | +
 | 
|  | 35 | +(d) I understand and agree that this project and the contribution | 
|  | 36 | +    are public and that a record of the contribution (including | 
|  | 37 | +    all personal information I submit with it, including my | 
|  | 38 | +    sign-off) is maintained indefinitely and may be redistributed | 
|  | 39 | +    consistent with this project or the open source license(s) | 
|  | 40 | +    involved. | 
|  | 41 | + ``` | 
|  | 42 | + | 
|  | 43 | +We require that every contribution to OpenSearch is signed with a Developer Certificate of Origin. Additionally, please use your real name. We do not accept anonymous contributors nor those utilizing pseudonyms. | 
|  | 44 | + | 
|  | 45 | +Each commit must include a DCO which looks like this | 
|  | 46 | + | 
|  | 47 | +``` | 
|  | 48 | +Signed-off-by: Jane Smith <jane.smith@email.com> | 
|  | 49 | +``` | 
|  | 50 | + | 
|  | 51 | +You may type this line on your own when writing your commit messages. However, if your user.name and user.email are set in your git configs, you can use `-s` or `– – signoff` to add the `Signed-off-by` line to the end of the commit message. | 
0 commit comments