[coreboot-gerrit] Change in coreboot[master]: MAINTAINERS: Clarify this is about active upstream development

[Nico Huber (Code Review)]

Nico Huber has uploaded this change for review. ( https://review.coreboot.org/29471


Change subject: MAINTAINERS: Clarify this is about active upstream development
......................................................................

MAINTAINERS: Clarify this is about active upstream development

<vendor> seems to be confused about the meaning of our maintainers list.
I get the feeling some use it to organize corporate internal teams and
branches, adding names to the list that don't show up in Gerrit and even
if, often don't react to reviewing requests (within months). Maybe they
even don't know that this is about coreboot.org?

To clarify this:

  o Add an introductory paragraph mentioning development on coreboot.org.
  o Explicitly state that maintainers should be registered to Gerrit.
  o If a topic is tagged as `Supported`, expect that somebody reacts to
    review requests.

Change-Id: I9ee038dc5ee1f4993ba1d230ef6e737f20e2ff8a
Signed-off-by: Nico Huber <nico.huber at secunet.com>
---
M MAINTAINERS
1 file changed, 12 insertions(+), 2 deletions(-)



  git pull ssh://review.coreboot.org:29418/coreboot refs/changes/71/29471/1

diff --git a/MAINTAINERS b/MAINTAINERS
index b7031c5..46b588a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1,6 +1,14 @@
 
 
-	List of maintainers and how to submit coreboot changes
+		    List of upstream coreboot maintainers
+		     and how to submit coreboot changes
+
+This represents the list of maintainers that work on the upstream coreboot
+code base (on coreboot.org).  Maintainers are assigned to topics and when
+applicable to subtrees of the source tree. You'll find some subtrees that
+don't have a maintainer. If you are looking for reviewers for such a sub-
+tree, it's often a good choice to look at the git history who worked on it
+lastly.
 
 Please try to follow the guidelines below.  This will make things
 easier on the maintainers.  Not all of these guidelines matter for every
@@ -65,6 +73,7 @@
 Descriptions of section entries:
 
 	M: Maintainer: FullName <address at domain>
+	   Should be registered to Gerrit (https://review.coreboot.org/).
 	R: Designated reviewer: FullName <address at domain>
 	   These reviewers should be CCed on patches.
 	L: Mailing list that is relevant to this area
@@ -73,7 +82,8 @@
 	T: SCM tree type and location.
 	   Type is one of: git, hg, quilt, stgit, topgit
 	S: Status, one of the following:
-	   Supported:	Someone is actually paid to look after this.
+	   Supported:	Someone is actually paid to look after this and can
+			be expected to react to review requests.
 	   Maintained:	Someone actually looks after it.
 	   Odd Fixes:	It has a maintainer but they don't have time to do
 			much other than throw the odd patch in. See below..

-- 
To view, visit https://review.coreboot.org/29471
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings

Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-MessageType: newchange
Gerrit-Change-Id: I9ee038dc5ee1f4993ba1d230ef6e737f20e2ff8a
Gerrit-Change-Number: 29471
Gerrit-PatchSet: 1
Gerrit-Owner: Nico Huber <nico.h at gmx.de>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.coreboot.org/pipermail/coreboot-gerrit/attachments/20181105/c8386119/attachment-0001.html>