add section about working on Flux issues
@@ -5,7 +5,24 @@ pull requests. This document outlines some of the conventions on development
workflow, commit message formatting, contact points and other resources to make
it easier to get your contribution accepted.
-We gratefully welcome improvements to documentation as well as to code.
+We gratefully welcome improvements to issues and documentation as well as to code.
+
+## Working on issues
+
+If you like Flux and want to get involved in the team, a great way to get started
+is reviewing our [blocked-needs-validation](https://github.com/weaveworks/flux/issues?q=is%3Aissue+is%3Aopen+label%3Ablocked-needs-validation) issues.
+
+The idea here is that new issues are first confirmed by somebody in the team,
+which might require asking for more information, testing with a fresh Flux
+environment and once confirmed (and more information added to the issue), removing
+the `blocked-needs-validation` label. Afterwards the issue can be worked on and
+fixed by the team.
+
+To set up Flux to test things, there's the [standalone install](site/get-started.md)
+and the [Helm install](site/helm-get-started.md), which might be helpful.
+
+Please talk to us on Slack, if you should get stuck anywhere. We appreciate
+any help and look forward welcoming you to the team!
## Certificate of Origin
