GNUBoot
/
coreboot-kgpe-d16
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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` or `Maintained`, expect that
    somebody reacts to review requests.

Change-Id: I9ee038dc5ee1f4993ba1d230ef6e737f20e2ff8a
Signed-off-by: Nico Huber <nico.huber@secunet.com>
Reviewed-on: https://review.coreboot.org/29471
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Angel Pons <th3fanbus@gmail.com>
Reviewed-by: David Guckian
This commit is contained in:
Nico Huber 2018-11-05 13:42:35 +01:00 committed by Nico Huber
parent d72d52a7e4
commit c9826d7934
1 changed files with 17 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
MAINTAINERS
View File

@ -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 to see who worked
on it last.
Please try to follow the guidelines below. This will make things Please try to follow the guidelines below. This will make things
easier on the maintainers. Not all of these guidelines matter for every easier on the maintainers. Not all of these guidelines matter for every
@ -65,6 +73,8 @@ trivial patch so apply some common sense.
Descriptions of section entries: Descriptions of section entries:
M: Maintainer: FullName <address@domain> M: Maintainer: FullName <address@domain>
Must be registered to Gerrit (https://review.coreboot.org/).
Should have experience with upstream coreboot development.
R: Designated reviewer: FullName <address@domain> R: Designated reviewer: FullName <address@domain>
These reviewers should be CCed on patches. These reviewers should be CCed on patches.
L: Mailing list that is relevant to this area L: Mailing list that is relevant to this area
@ -73,8 +83,12 @@ Descriptions of section entries:
T: SCM tree type and location. T: SCM tree type and location.
Type is one of: git, hg, quilt, stgit, topgit Type is one of: git, hg, quilt, stgit, topgit
S: Status, one of the following: S: Status, one of the following:
Supported: Someone is actually paid to look after this. Supported: Someone is continuously paid to look after this and
Maintained: Someone actually looks after it. a reaction to review requests can be expected
within a few days, a month at most.
Maintained: Someone actually looks after it and a reaction to
review requests can usually be expected within a
few weeks.
Odd Fixes: It has a maintainer but they don't have time to do Odd Fixes: It has a maintainer but they don't have time to do
much other than throw the odd patch in. See below.. much other than throw the odd patch in. See below..
Orphan: No current maintainer [but maybe you could take the Orphan: No current maintainer [but maybe you could take the