From ff78e7f244fcee10fa2617dfa87eb351f8018e65 Mon Sep 17 00:00:00 2001 From: Christopher Ferris Date: Fri, 20 Oct 2017 17:52:58 -0400 Subject: [PATCH] Update maintainer policy Clarify criteria for removing a maintainer to include prolonged inactivity. Change-Id: I4289bba1706e6766459b778b223b7d4c74c30c7e Signed-off-by: Christopher Ferris --- docs/source/CONTRIBUTING.rst | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/source/CONTRIBUTING.rst b/docs/source/CONTRIBUTING.rst index 41ab640f399..4284448590e 100644 --- a/docs/source/CONTRIBUTING.rst +++ b/docs/source/CONTRIBUTING.rst @@ -75,7 +75,7 @@ hours. If not, please bump the issue with a comment and request that it be reviewed. You can also post to the relevant fabric channel in `Hyperledger Rocket Chat `__. For example, a doc bug should be broadcast to ``#fabric-documentation``, a database bug to ``#fabric-ledger``, -and so on... +and so on... Fixing issues and working stories --------------------------------- @@ -253,9 +253,12 @@ change set to the :doc:`MAINTAINERS.rst ` file. A nominated Contributor may become a Maintainer by a majority approval of the proposal by the existing Maintainers. Once approved, the change set is then merged and the individual is added to (or alternatively, removed from) the maintainers -group. Maintainers may be removed by explicit resignation, or for some -infraction of the `code of conduct `__ -or by consistently demonstrating poor judgement. +group. Maintainers may be removed by explicit resignation, for prolonged +inactivity (3 or more months), or for some infraction of the `code of conduct +`__ +or by consistently demonstrating poor judgement. A maintainer removed for +inactivity should be restored following a sustained resumption of contributions +and reviews (a month or more) demonstrating a renewed commitment to the project. Legal stuff -----------