]> git.sur5r.net Git - i3/i3/commitdiff
docs: add section on finding issues to CONTRIBUTING 1788/head
authorTony Crisci <tony@dubstepdish.com>
Fri, 10 Jul 2015 04:04:20 +0000 (00:04 -0400)
committerTony Crisci <tony@dubstepdish.com>
Fri, 10 Jul 2015 04:04:20 +0000 (00:04 -0400)
CONTRIBUTING.md

index 1e1307614cc10e8f7ff14794ae6f44e9e4f9c3a2..39835c14f56a9cf3b552673c6e36fee17be31c85 100644 (file)
@@ -23,3 +23,10 @@ and https://github.com/i3/i3lock
 * Use the `next` branch for developing and sending your pull request.
 * Use `clang-format` to format your code.
 * Run the testsuite, see http://i3wm.org/docs/testsuite.html
+
+# Finding something to do
+
+* Find a [reproducible bug](https://github.com/i3/i3/issues?utf8=%E2%9C%93&q=is%3Aopen+label%3Areproducible+label%3Abug+) from the issue tracker. These issues have been reviewed and confirmed by a project contributor.
+* Find an [accepted enhancement](https://github.com/i3/i3/issues?utf8=%E2%9C%93&q=is%3Aopen+label%3Aaccepted+label%3Aenhancement) from the issue tracker. These have been approved and are ok to start working on.
+
+There's a very good [overview of the codebase](http://i3wm.org/docs/hacking-howto.html) available to get you started.