Descripe contribution workflow
Describe how to contribute via GitHub, and whom to contact if your contribution
gets lost.
@@ -18,6 +18,60 @@ This short page shall help to get started with the projects and topics
surrounding them
+## Contributing to KubeVirt
+
+### Our workflow
+
+Contributing to KubeVirt shall be as simple as possible. Have a question? Want
+to diskuss something ? Want to contribute something? Just open an
+[Issue](https://github.com/kubevirt/kubevirt/issues), a [Pull
+Request](https://github.com/kubevirt/kubevirt/pulls), or send a mail to our
+[Google Group](https://groups.google.com/forum/#!forum/kubevirt-dev).
+
+If you spot a bug or want to change something pretty simple, just go
+ahead and open an Issue and/or a Pull Request, including your changes
+at [kubevirt/kubevirt](https://github.com/kubevirt/kubevirt).
+
+For bigger changes, please create a tracker Issue, describing what you want to
+do. Then either as the first commit in a Pull Request, or as an independent
+Pull Request, provide an **informal** design proposal of your intended changes.
+The location for such propoals is
+[/docs](https://github.com/kubevirt/kubevirt/tree/master/docs) in the KubeVirt
+core repository. Make sure that all your Pull Requests link back to the
+relevant Issues.
+
+### Getting started
+
+To make yourself comfortable with the code, you might want to work on some
+Issues marked with one or more of the following labels
+[beginner](https://github.com/kubevirt/kubevirt/issues?q=is%3Aissue+is%3Aopen+label%3Abeginner),
+[help
+wanted](https://github.com/kubevirt/kubevirt/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22)
+or [bug](https://github.com/kubevirt/kubevirt/labels/bug). Any help is highly
+appreciated.
+
+### Testing
+
+**Untested features do not exist**. To ensure that what we code really works,
+relevant flows should be covered via unit tests and functional tests. So when
+thinking about a contribution, also think about testability.
+
+### Getting your code reviewed/merged
+
+Maintainers are here to help you enabling your use-case in a reasonable amount
+of time. The maintainers will try to review your code and give you productive
+feedback in a reasonable amount of time. However, if you are blocked on a
+review, or your Pull Request does not get the attention you think it deserves,
+reach out for us via Comments in your issues, or ping us on IRC [#kubevirt @irc.freenode.net](https://kiwiirc.com/client/irc.freenode.net/kubevirt).
+
+Maintainers are:
+
+ * @admiyo
+ * @berrange
+ * @fabiand
+ * @rmohr
+ * @stu-gott
+
## Projects & Communities
### [Kubernetes](http://kubernetes.io/)
