mirror of
https://github.com/valitydev/opendistro-security-ssl.git
synced 2024-11-06 08:55:15 +00:00
Update contributing
Update contributing links
This commit is contained in:
parent
eea61fc0d3
commit
f3430eeb19
@ -11,7 +11,7 @@ information to effectively respond to your bug report or contribution.
|
|||||||
|
|
||||||
We welcome you to use the GitHub issue tracker to report bugs or suggest features.
|
We welcome you to use the GitHub issue tracker to report bugs or suggest features.
|
||||||
|
|
||||||
When filing an issue, please check [existing open](https://github.com/OpenDistro/elasticsearch-security-ssl/issues), or [recently closed](https://github.com/OpenDistro/elasticsearch-security-ssl/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already
|
When filing an issue, please check [existing open](https://github.com/open-distro-for-elasticsearch/security-ssl/issues), or [recently closed](https://github.com/open-distro-for-elasticsearch/security-ssl/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already
|
||||||
reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
|
reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
|
||||||
|
|
||||||
* A reproducible test case or series of steps
|
* A reproducible test case or series of steps
|
||||||
@ -41,22 +41,20 @@ GitHub provides additional document on [forking a repository](https://help.githu
|
|||||||
|
|
||||||
|
|
||||||
## Finding contributions to work on
|
## Finding contributions to work on
|
||||||
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/OpenDistro/elasticsearch-security-ssl/labels/help%20wanted) issues is a great place to start.
|
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/open-distro-for-elasticsearch/security-ssl/labels/help%20wanted) issues is a great place to start.
|
||||||
|
|
||||||
|
|
||||||
## Code of Conduct
|
## Code of Conduct
|
||||||
This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
|
|
||||||
For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
|
This project has adopted an [Open Source Code of Conduct](https://opendistro.github.io/for-elasticsearch/codeofconduct.html).
|
||||||
opensource-codeofconduct@amazon.com with any additional questions or comments.
|
|
||||||
|
|
||||||
|
|
||||||
## Security issue notifications
|
## Security issue notifications
|
||||||
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
|
|
||||||
|
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public GitHub issue.
|
||||||
|
|
||||||
|
|
||||||
## Licensing
|
## Licensing
|
||||||
|
|
||||||
See the [LICENSE](https://github.com/OpenDistro/elasticsearch-security-ssl/blob/master/LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
|
See the [LICENSE](./LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
|
||||||
|
|
||||||
We may ask you to sign a Contributor License Agreement (CLA) for larger changes.
|
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user