summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--MAINTAINERS20
1 files changed, 17 insertions, 3 deletions
diff --git a/MAINTAINERS b/MAINTAINERS
index b7031c54e5..825147f843 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 to see who worked
+on it last.
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,8 @@ trivial patch so apply some common sense.
Descriptions of section entries:
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>
These reviewers should be CCed on patches.
L: Mailing list that is relevant to this area
@@ -73,8 +83,12 @@ Descriptions of section entries:
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.
- Maintained: Someone actually looks after it.
+ Supported: Someone is continuously paid to look after this and
+ 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
much other than throw the odd patch in. See below..
Orphan: No current maintainer [but maybe you could take the