Add COC and Contribution docs

Signed-off-by: Frank Jogeleit <frank.jogeleit@web.de>

CODE_OF_CONDUCT.md

@@ -0,0 +1,36 @@
+# Kyverno Community Code of Conduct v1.0
+
+## Contributor Code of Conduct
+
+As contributors and maintainers of this project, and in the interest of fostering
+an open and welcoming community, we pledge to respect all people who contribute
+through reporting issues, posting feature requests, updating documentation,
+submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free experience for
+everyone, regardless of level of experience, gender, gender identity and expression,
+sexual orientation, disability, personal appearance, body size, race, ethnicity, age,
+religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery
+* Personal attacks
+* Trolling or insulting/derogatory comments
+* Public or private harassment
+* Publishing other's private information, such as physical or electronic addresses, without explicit permission
+* Other unethical or unprofessional conduct.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are not
+aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers
+commit themselves to fairly and consistently applying these principles to every aspect
+of managing this project. Project maintainers who do not follow or enforce the Code of
+Conduct may be permanently removed from the project team.
+
+This code of conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior in Kubernetes may be reported by contacting the project maintainer(s).
+
+This Code of Conduct is adapted from the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) and the [Contributor Covenant](https://www.contributor-covenant.org/), [version 1.2.0](https://www.contributor-covenant.org/version/1/2/0/code-of-conduct/).

CONTRIBUTING.md

@@ -0,0 +1,95 @@
+# Contributing Guidelines for Kyverno
+
+We welcome all contributions, suggestions, and feedback, so please do not hesitate to reach out!
+
+Before you contribute, please take a moment to review and agree to abide by our community [Code of Conduct](/CODE_OF_CONDUCT.md).
+
+- [Contributing Guidelines for Policy Reporter](#contributing-guidelines-for-policy-reporter)
+  - [Ways you can contribute](#ways-you-can-contribute)
+    - [Report issues](#report-issues)
+    - [Fix or Improve Documentation](#fix-or-improve-documentation)
+    - [Submit Pull Requests](#submit-pull-requests)
+  - [How to Create a PR](#how-to-create-a-pr)
+  - [Engage with us](#engage-with-us)
+  - [Developer Certificate of Origin (DCO) Sign off](#developer-certificate-of-origin-dco-sign-off)
+
+## Ways you can contribute
+
+### Report issues
+
+Issues to Policy Reporter help improve the project in multiple ways including the following:
+
+- Report potential bugs
+- Request a feature
+
+### Fix or Improve Documentation
+
+The [Policy Reporter Documentation](https://kyverno.github.io/policy-reporter/), like the main Policy Reporter codebase, is stored in its own [git repo](https://github.com/kyverno/policy-reporter-docs).
+
+### Submit Pull Requests
+
+[Pull requests](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) (PRs) allow you to contribute back the changes you've made on your side enabling others in the community to benefit from your hard work. They are the main source by which all changes are made to this project and are a standard piece of GitHub operational flows.
+
+Once you wish to get started contributing to the code base, please refer to our [local development mode](https://kyverno.github.io/policy-reporter/core/development) for local setup guide.
+
+## How to Create a PR
+
+Head over to the project repository on GitHub and click the **"Fork"** button. With the forked copy, you can try new ideas and implement changes to the project.
+
+1. **Clone the repository to your device:**
+
+Get the link of your forked repository, paste it in your device terminal and clone it using the command.
+
+```sh
+git clone https://hostname/YOUR-USERNAME/YOUR-REPOSITORY
+```
+
+2. **Create a branch:**
+
+Create a new brach and navigate to the branch using this command.
+
+```sh
+git checkout -b <new-branch>
+```
+
+Great, it's time to start hacking! You can now go ahead to make all the changes you want.
+
+3. **Stage, Commit, and Push changes:**
+
+Now that we have implemented the required changes, use the command below to stage the changes and commit them.
+
+```sh
+git add .
+```
+
+```sh
+git commit -s -m "Commit message"
+```
+
+The `-s` signifies that you have signed off the commit.
+
+Go ahead and push your changes to GitHub using this command.
+
+```sh
+git push
+```
+
+## Engage with us
+
+The website has the most updated information on [how to engage with the Kyverno community](https://kyverno.io/community/) including its maintainers and contributors.
+
+## Developer Certificate of Origin (DCO) Sign off
+
+For contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project, we are requiring everyone to acknowledge this by signing their work which indicates you agree to the DCO found [here](https://developercertificate.org/).
+
+To sign your work, just add a line like this at the end of your commit message:
+
+```sh
+Signed-off-by: Random J Developer <random@developer.example.org>
+```
+
+This can easily be done with the `-s` command line option to append this automatically to your commit message.
+
+```sh
+git commit -s -m 'This is my commit message'
+```