helm/CONTRIBUTING.md

# Contributing Guidelines

The Kubernetes Helm project accepts contributions via GitHub pull requests. This document outlines the process to help get your contribution accepted.

## Reporting a Security Issue

Most of the time, when you find a bug in Helm, it should be reported
using [GitHub issues](github.com/kubernetes/helm/issues). However, if
you are reporting a _security vulnerability_, please email a report to
[helm-security@deis.com](mailto:helm-security@deis.com). This will give
us a chance to try to fix the issue before it is exploited in the wild.

## Contributor License Agreements

We'd love to accept your patches! Before we can take them, we have to jump a couple of legal hurdles.

Please fill out either the individual or corporate Contributor License Agreement (CLA).

  * If you are an individual writing original source code and you're sure you own the intellectual property, then you'll need to sign an [individual CLA](http://code.google.com/legal/individual-cla-v1.0.html).
  * If you work for a company that wants to allow you to contribute your work, then you'll need to sign a [corporate CLA](http://code.google.com/legal/corporate-cla-v1.0.html).

Follow either of the two links above to access the appropriate CLA and instructions for how to sign and return it. Once we receive it, we'll be able to accept your pull requests.

***NOTE***: Only original source code from you and other people that have signed the CLA can be accepted into the main repository.

## How to Submit a Proposal

Submit proposals through the issue queue. The title of your issue should start with `PROPOSAL:`.

## How to Contribute a Patch

1. If you haven't already done so, sign a Contributor License Agreement (see details above).
1. Fork the desired repo, develop and test your code changes.
1. Submit a pull request.

Coding conventions and standards are explained in the official
developer docs:
https://github.com/kubernetes/helm/blob/master/docs/developers.md

### Merge Approval

Helm collaborators may add "LGTM" (Looks Good To Me) or an equivalent comment to indicate that a PR is acceptable. Any change requires at least one LGTM.  No pull requests can be merged until at least one Helm collaborator signs off with an LGTM.

If the PR is from a Helm collaborator, then he or she should be the one to merge and close it. This keeps the commit stream clean and gives the collaborator the benefit of revisiting the PR before deciding whether or not to merge the changes.

## Support Channels

Whether you are a user or contributor, official support channels include:

- GitHub issues: https://github.com/kubenetes/helm/issues/new
- Slack: #Helm room in the [Kubernetes Slack](http://slack.kubernetes.io/)

Before opening a new issue or submitting a new pull request, it's helpful to search the project - it's likely that another user has already reported the issue you're facing, or it's a known issue that we're already aware of.
docs(README): udate core docs pre-merge 9 years ago			`# Contributing Guidelines`

			`The Kubernetes Helm project accepts contributions via GitHub pull requests. This document outlines the process to help get your contribution accepted.`

fix(CONTRIBUTING): add guidelines for security issues Closes #662 9 years ago			`## Reporting a Security Issue`

			`Most of the time, when you find a bug in Helm, it should be reported`
			`using [GitHub issues](github.com/kubernetes/helm/issues). However, if`
			`you are reporting a _security vulnerability_, please email a report to`
			`[helm-security@deis.com](mailto:helm-security@deis.com). This will give`
			`us a chance to try to fix the issue before it is exploited in the wild.`

docs(README): udate core docs pre-merge 9 years ago			`## Contributor License Agreements`

			`We'd love to accept your patches! Before we can take them, we have to jump a couple of legal hurdles.`

			`Please fill out either the individual or corporate Contributor License Agreement (CLA).`

			`* If you are an individual writing original source code and you're sure you own the intellectual property, then you'll need to sign an [individual CLA](http://code.google.com/legal/individual-cla-v1.0.html).`
			`* If you work for a company that wants to allow you to contribute your work, then you'll need to sign a [corporate CLA](http://code.google.com/legal/corporate-cla-v1.0.html).`

			`Follow either of the two links above to access the appropriate CLA and instructions for how to sign and return it. Once we receive it, we'll be able to accept your pull requests.`

			`*NOTE*: Only original source code from you and other people that have signed the CLA can be accepted into the main repository.`

chore(docs): add how to submit proposals 8 years ago			`## How to Submit a Proposal`

			Submit proposals through the issue queue. The title of your issue should start with `PROPOSAL:`.

			`## How to Contribute a Patch`
docs(README): udate core docs pre-merge 9 years ago
			`1. If you haven't already done so, sign a Contributor License Agreement (see details above).`
			`1. Fork the desired repo, develop and test your code changes.`
			`1. Submit a pull request.`

docs(developer): update developer documentation Closes #840 9 years ago			`Coding conventions and standards are explained in the official`
			`developer docs:`
			`https://github.com/kubernetes/helm/blob/master/docs/developers.md`

docs(README): udate core docs pre-merge 9 years ago			`### Merge Approval`

			`Helm collaborators may add "LGTM" (Looks Good To Me) or an equivalent comment to indicate that a PR is acceptable. Any change requires at least one LGTM. No pull requests can be merged until at least one Helm collaborator signs off with an LGTM.`

			`If the PR is from a Helm collaborator, then he or she should be the one to merge and close it. This keeps the commit stream clean and gives the collaborator the benefit of revisiting the PR before deciding whether or not to merge the changes.`

			`## Support Channels`

			`Whether you are a user or contributor, official support channels include:`

			`- GitHub issues: https://github.com/kubenetes/helm/issues/new`
			`- Slack: #Helm room in the [Kubernetes Slack](http://slack.kubernetes.io/)`

			`Before opening a new issue or submitting a new pull request, it's helpful to search the project - it's likely that another user has already reported the issue you're facing, or it's a known issue that we're already aware of.`