From 8f6113b70687fb2034f807e8b3ce2460fc19143f Mon Sep 17 00:00:00 2001
From: Marko Petric <marko.petric@cern.ch>
Date: Thu, 23 Mar 2017 14:55:19 +0100
Subject: [PATCH] Add some text about WIP and issue tracking

---
 .github/CONTRIBUTING.md | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index 02ecb9d3a..85bff44a0 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -6,13 +6,25 @@
 When making a `Pull Request` please explain what and why things were
 changed. Please include a short description in the
 BEGINRELEASENOTES/ENDRELEASENOTES block, which will appear in the
-doc/ReleaseNotes.md of the given package, once a new tag is made.
+doc/ReleaseNotes.md, once a new tag is made.
+
+We are happy if you create pull-requests also if you feature is not ready, yet.
+Please mar them as such by adding `[WIP]` to the start of the title. The purpose
+of this is, for example, that you want to let other people know you are working
+on a given issue. For these work-in-progress pull-request, we propose to have a
+check list of things that still need to be done.
+
+## Issue tracking
+
+Use the github issue tracker. Reference the issues that you are working on. If
+you notice an issue, consider first creating an issue and then refering to it in
+your pull-request and commit messages with `#[issue-id]`.
+
 
 ## Coding Conventions
 
  * Your code should not introduce any new warnings, and fix as many existing warnings as possible
 
-
 ## Git workflow
 
 For an explanation of the git(hub) workflow please see
-- 
GitLab