From f40e614a22ca70a967522438e1b9994421af3dc0 Mon Sep 17 00:00:00 2001
From: Marin Jankovski <maxlazio@gmail.com>
Date: Mon, 15 May 2017 16:48:09 +0200
Subject: [PATCH] Add the maintainers policy on issue triaging.

---
 CONTRIBUTING.md | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1426ccf8db..9b6f9e8133 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -17,6 +17,15 @@ This can be the case when installation and `gitlab-ctl reconfigure` run went wit
 
 ## Maintainer documentation
 
+Maintainers of this project will try to address issues in a timely manner.
+Maintainers, however, cannot guarantee that they would be able to address
+all incoming issues as soon as they are raised nor can guarantee to provide an
+answer to all raised issues.
+
+If your issue is closed due to inactivity (from either side), please check
+whether the issue persists in the latest version. If that is the case, feel free
+to reopen the issue or create a new one with a link to the old issue.
+
 ### Issue description templates
 
 Issue description template will show this message to
@@ -72,7 +81,7 @@ Request includes more tests. This is to ensure that the test coverage grows with
 development.
 
 When in rush to fix something (eg. security issue, bug blocking the release),
-writing specs can be skipped. However, an issue to implement the tests 
+writing specs can be skipped. However, an issue to implement the tests
 **must be** created and assigned to the person who originally wrote the code.
 
 To run tests, execute the following command (you may have to run `bundle install` before running it)
-- 
GitLab