[PATCH] doc: Add maintainer process

[Alexander Smirnov <asmirnov@ilbers.de>]

This patch adds basic maintainer process description, that has been
used so far since the project start.

Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
---
 doc/maintainer.md | 47 +++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 47 insertions(+)
 create mode 100644 doc/maintainer.md

diff --git a/doc/maintainer.md b/doc/maintainer.md
new file mode 100644
index 0000000..ddaf39b
--- /dev/null
+++ b/doc/maintainer.md
@@ -0,0 +1,47 @@
+# Introduction
+
+Isar maintainer is the person who keeps project development in compliance
+with contributing process definition. The purpose of this document is to
+describe the maintainer process in Isar project.
+
+# Responsibilities
+
+## Feedback on Contributions
+
+Isar maintainer should review each contribution that has been sent to
+mailing list and provide the feedback. Feedback could be on of the
+following categories:
+
+ - Contribution accepted: If no quality and design issues were found.
+
+ - Change request: If some small quality or design issues were found, the
+   maintainer requests next version with resolved issues.
+
+ - Contribution rejected: If there are major design issues or general
+   benefit from the contribution is ambiguous.
+
+During the review, the maintainer may ask additional questions to clarify
+the details.
+
+## Repository Branches
+
+There are two official branches in Isar, intended to increase project
+quality:
+
+ - next: The accepted contributions from mailing list are merged to this
+   branch. Basic CI checks should be run after each merge. This branch
+   could be forced.
+
+ - master: After passing full-cycle testing of next branch, it should be
+   merged to master. Master branch should contain stable releases only, so
+   all the features officially supported by current Isar version (including
+   features from previous releases) should be tested.
+
+The next branch is intended to be merged into master monthly. Maintainer
+could perform a merge to master before the ordinary window if next branch
+contains urgent patch series (bug fixes or critical features).
+
+## Issues at GitHub
+
+For each issue has been found in master and next branches the maintainer
+should create GitHub issue.
-- 
2.9.4