Add development instructions (#20)

Author: Douglas Camata

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,43 @@
+---
+name: Bug report
+about: Create a bug report to help us improve
+title: '[name of the chart] <issue title>'
+labels: ''
+assignees: ''
+
+---
+
+<!-- Thanks for filing an issue! Before hitting the button, please answer these questions. It's helpful to search the existing GitHub issues first. 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
+
+Fill in as much of the template below as you can.  If you leave out information, we can't help you as well.
+
+Be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue.  If we're wrong, PLEASE feel free to reopen it and explain why.
+-->
+
+**Bug description**
+
+A clear and concise description of what the bug is.
+
+**Version of Helm and Kubernetes**
+
+The versino of Helm and Kubernetes where the problem occurs.
+
+**Which chart?**
+
+The chart name and version.
+
+**What happened?**
+
+Described what happened, as detailed as possible and necessary.
+
+**What you expected to happen?**
+
+Please avoid saying "It should just work".
+
+**How to reproduce it?**
+
+Steps to reproduce the problem, as minimally and precisely as possible.
+
+**Anything else we need to know?**
+
+Surprise us!

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,31 @@
+---
+name: Feature request
+about: Suggest an idea/feature for this project
+title: '[name of the chart] <issue title>'
+labels: ''
+assignees: ''
+
+---
+
+<!-- Thanks for filing an issue! Before hitting the button, please answer these questions. It's helpful to search the existing GitHub issues first. 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.
+
+Describe *in detail* the feature/behavior/change you'd like to see.
+
+Be ready for followup questions, and please respond in a timely manner. If we can't reproduce a bug or think a feature already exists, we might close your issue.  If we're wrong, PLEASE feel free to reopen it and explain why.
+-->
+
+**Is your feature request related to a problem? Please describe.**
+
+A clear and concise description of what the problem is, e.g. `I'm always frustrated when [...]`
+
+**Describe the solution you'd like**
+
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,40 @@
+<!--
+Thank you for contributing to New Relic's Helm charts. Before you submit this PR we'd like to
+make sure you are aware of our technical requirements:
+
+* https://github.com/newrelic-experimental/helm-charts/blob/master/CONTRIBUTING.md#technical-requirements
+
+For a quick overview across what we will look at reviewing your PR, please read
+our review guidelines:
+
+* https://github.com/newrelic-experimental/helm-charts/blob/master/REVIEW_GUIDELINES.md
+
+Following our best practices right from the start will accelerate the review process and
+help get your PR merged quicker.
+
+When updates to your PR are requested, please add new commits and do not squash the
+history. This will make it easier to identify new changes. The PR will be squashed
+anyways when it is merged. Thanks.
+
+For fast feedback, please @-mention maintainers that are listed in the Chart.yaml file.
+
+Please make sure you test your changes before you push them. Once pushed, a Github Action
+will run across your changes and do some initial checks and linting. These checks run
+very quickly. Please check the results. We would like these checks to pass before we
+even continue reviewing your changes.
+-->
+#### Is this a new chart
+
+#### What this PR does / why we need it:
+
+#### Which issue this PR fixes
+*(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*
+  - fixes #
+
+#### Special notes for your reviewer:
+
+#### Checklist
+[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
+- [ ] Chart Version bumped
+- [ ] Variables are documented in the README.md
+- [ ] Title of the PR starts with chart name (e.g. `[mychartname]`)

CHART_TESTING.md

@@ -0,0 +1,26 @@
+# Charts Testing
+
+## Pull Request Testing
+
+Pull request testing is done by running [Helm's Chart Testing Action](https://github.com/helm/chart-testing) automatically.
+It will lint the chart and install it in a cluster created using [Kubernetes in Docker (KIND)](https://github.com/kubernetes-sigs/kind).
+
+### Procedure
+
+The Helm's Chart Testing Action will run the [ct lint-and-install](https://github.com/helm/chart-testing/blob/master/doc/ct_lint-and-install.md) command.
+This is the main logic for validation of a pull request. It intends to only test charts that have changed in this PR.
+
+The testing logic has been extracted to the [chart-testing](https://github.com/helm/chart-testing) project. A go library provides the required logic to lint, install, and test charts.
+It is provided as a Docker image and can be run by anyone on their own charts.
+
+### Providing Custom Test Values
+
+Testing charts with default values may not be suitable in all cases. For instance, charts may require some values to be set which should not be part of the chart's default `values.yaml` (such as keys etc.). Furthermore, it is often desirable to test a chart with different configurations, reflecting different use cases (e.g. setting a password instead of using the default generated one, activating persistence instead of using the default emptyDir volume, etc.).
+
+In order to enable custom test values, create a directory `ci` in the chart's directory and add any number of `*-values.yaml` files to this directory. Only files with a suffix `-values.yaml` are considered. Instead of using the defaults, the chart is then installed and tested separately for each of these files using the `--values` flag.
+
+Please note that in order to test using the default values when using the `ci` directory, an empty values file must be present in the directory.
+
+For examples, you can take a look at existing tests in this repository (e.g. [Simple Nginx chart](charts/simple-nginx)).
+
+Please also note that it is a different concept than "[Helm Chart Test](https://github.com/helm/helm/blob/master/docs/chart_tests.md)", although the Helm Chart test, if defined, will be run by this test tool for each test values.

CODEOWNERS

@@ -4,3 +4,7 @@
 # NOTE: Github still doesn't support nested code owners.
 # Owners for charts go below this line using the following format:
 # charts/<CHART_NAME>/* @<GITHUB_USER>
+
+# Simple nginx chart for testing purposes
+
+charts/simple-nginx/* @douglascamata

CONTRIBUTING.md

@@ -0,0 +1,76 @@
+# Contributing Guidelines
+
+The Kubernetes Charts project accepts contributions via GitHub pull requests. This document outlines the process to help get your contribution accepted.
+
+## Contributor's License Agreement (CLA)
+
+To be able to contribute to the New Relic Helm charts repository you have to sign a CLA.
+The CLA signature process is handled by a bot and is presented to the contributor as a
+check in the pull request.
+
+If you didn't sign the CLA yet, follow the procedures in the comment of the bot to do
+so.
+
+## How to contribute to an existing chart
+
+1. Fork this repository, develop and test your chart's changes.
+1. Ensure your Chart changes follow the [technical](#technical-requirements) and [documentation](#documentation-requirements) guidelines, described below.
+1. Submit a pull request.
+1. Automated builds will run for testing and linting.
+1. A code review will automaticallly be requested by the owners of the chart.
+1. The PR is reviewed, merged and the chart is automatically released.
+
+***NOTE***: In order to make testing and merging of PRs easier, please submit changes to multiple charts in separate PRs.
+
+### Technical requirements
+
+* All Chart dependencies should also be submitted independently
+* Must pass the linter (`helm lint`)
+* Must successfully launch with default values (`helm install .`)
+    * All pods go to the running state (or NOTES.txt provides further instructions if a required value is missing).
+    * All services have at least one endpoint
+* Must include source GitHub repositories for images used in the Chart
+* Images should not have any major security vulnerabilities
+* Must be up-to-date with the latest stable Helm/Kubernetes features
+    * Use Deployments in favor of ReplicationControllers
+* Should follow Kubernetes best practices
+    * Include Health Checks wherever practical
+    * Allow configurable [resource requests and limits](http://kubernetes.io/docs/user-guide/compute-resources/#resource-requests-and-limits-of-pod-and-container)
+* Provide a method for data persistence (if applicable)
+* Support application upgrades
+* Allow customization of the application configuration
+* Provide a secure default configuration
+* Do not leverage alpha features of Kubernetes
+* Includes a [NOTES.txt](https://helm.sh/docs/topics/charts/#chart-license-readme-and-notes) explaining how to use the application after install
+* Follows [best practices](https://helm.sh/docs/chart_best_practices/)
+  (especially for [labels](https://helm.sh/docs/chart_best_practices/labels/)
+  and [values](https://helm.sh/docs/chart_best_practices/values/))
+
+### Documentation requirements
+
+* Must include an in-depth `README.md`, including:
+    * Short description of the Chart
+    * Any prerequisites or requirements
+    * Customization: explaining options in `values.yaml` and their defaults
+* Must include a short `NOTES.txt`, including:
+    * Any relevant post-installation information for the Chart
+    * Instructions on how to access the application or service provided by the Chart
+
+### Pull request approval and release process
+
+A Github Action will run to lint and test the chart's installation. More information abouut it
+can be found in the [Chart Testing documentation](CHART_TESTING.md).
+
+A maintainer of the chart will review the changes and eventually approve them. Any change requires at least one review.
+No pull requests can be merged until at least one maintainer reviews it. A good guide for what to review
+can be found in the [Review Guidelines](REVIEW_GUIDELINES.md).
+
+Once the Chart has been merged, the release will be automatically made by a Github Workflwo using the Github Pages of this repository.
+
+## Support Channels
+
+Whether you are a user or contributor, official support channels include:
+
+- GitHub issues: https://github.com/newrelic-experimental/charts/issues
+
+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.

README.md

@@ -0,0 +1,21 @@
+# New Relic Helm charts repository
+
+This repository intends to host official Helm charts for New Relic's products or other charts developed by New Relic.
+
+## Developing a chart
+
+You can use the Helm CLI to develop a chart in this repository.
+
+1. [Install Helm](https://helm.sh/docs/intro/install/)
+1. Add/modify the files for the desired chart
+1. Run `helm install dev-chart charts/<YOUR_CHART>` to install it locally.
+   Feel free to add different values to the chart if you wish so.
+1. Verify if the chart works as expected.
+1. Remove the installed chart with `helm uninstall dev-chart`.
+1. Create your pull request and follow the instructions below.
+
+### Contributing
+
+Please view [our contributing docs](CONTRIBUTING.md) for more information.
+
+