add some stuff to achieve silver badge (zalando#940)

add more to the contributing guide which is needed to reach silver cii badge

Signed-off-by: Sandor Szücs <[email protected]>

Author: szuecs

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior
+may be reported by contacting the project team at
+[email protected] and [email protected]. All complaints
+will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project
+team is obligated to maintain confidentiality with regard to the
+reporter of an incident.  Further details of specific enforcement
+policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -9,7 +9,8 @@ There are multiple ways of getting involved:
 - [Contribute code](#contribute-code)
 
 Below are a few guidelines we would like you to follow.
-If you need help, please reach out to us: [email protected]
+If you need help, please reach out to us: [community channels](https://github.com/zalando/skipper#community)
+
 
 ## Report a bug
 Reporting bugs is one of the best ways to contribute. Before creating a bug report, please check that an [issue](https://github.com/zalando/skipper/issues) reporting the same problem does not already exist. If there is an such an issue, you may add your information as a comment.
@@ -19,18 +20,22 @@ To report a new bug you should open an issue that summarizes the bug and set the
 If you want to provide a fix along with your bug report: That is great! In this case please send us a pull request as described in section [Contribute Code](#contribute-code).
 
 ## Suggest a feature
-To request a new feature you should open an [issue](https://github.com/zalando/skipper/issues/new) and summarize the desired functionality and its use case. Set the issue label to "feature".
+To request a new feature you should open an [issue](https://github.com/zalando/skipper/issues/new) and summarize the desired functionality and its use case. Set the issue label to "enhancement".
 
 ## Contribute code
 This is a rough outline of what the workflow for code contributions looks like:
 - Check the list of open [issues](https://github.com/zalando/skipper/issues). Either assign an existing issue to yourself, or create a new one that you would like work on and discuss your ideas and use cases.
 - Fork the repository on GitHub
-- Create a topic branch from where you want to base your work. This is usually master.
+- Create a topic branch, for example feature/foo fix/bar refactor/baz, from where you want to base your work. The base is usually master.
 - Make commits of logical units.
 - Write good commit messages (see below).
 - Push your changes to a topic branch in your fork of the repository.
 - Submit a pull request to [zalando/skipper](https://github.com/zalando/skipper)
 - Your pull request must receive a :thumbsup: from two [Maintainers](https://github.com/zalando/skipper/blob/master/MAINTAINERS)
+- Major changes need to include tests. Features need
+  additionally include documentation for developers as
+  [godoc](https://godoc.org/github.com/zalando/skipper) and add
+  [user documentation in markdown](https://opensource.zalando.com/skipper) in the docs/ directory.
 
 Thanks for your contributions!
 
@@ -43,3 +48,8 @@ Your commit messages ideally can answer two questions: what changed and why. The
 When creating a pull request, its comment should reference the corresponding issue id.
 
 **Have fun and enjoy hacking!**
+
+## Governance - final decisions
+
+The project owner and lead makes all final decisions, if there is a
+disagreement between contributors and maintainers.

readme.md

@@ -276,6 +276,8 @@ Blog posts:
 - [Building our own open source http routing
   solution](https://jobs.zalando.com/tech/blog/building-our-own-open-source-http-routing-solution/):
   Giving some context about why Skipper was created in the first place.
+- [Kubernetes in production @ ShopGun](https://itnext.io/kubernetes-in-production-shopgun-2c280f0c0923)
+- Hacker News [Skipper – An HTTP router and reverse proxy for service composition](https://news.ycombinator.com/item?id=18837936)
 
 Conference/Meetups talks