Maintainers.txt: Add Package Reviewer role

Although everyone is encouraged to review patches and add their
Reviewed-by reply for a patch, with the Package Reviewer role we
identify additional community members that will be Cc'd for patches
made to a package.

A distinction between a Package Maintainer and Reviewer is that
Maintainers will always have source control push access to the package
whereas Reviewers will not. (The Reviewer may have push access if they
are also Package Maintainer for another package.)

Currently we have an limit of 2 Package Maintainers per package, but
the Package Maintainers for each package decide how to manage the
Package Reviewer list.

Cc: Andrew Fish <afish@apple.com>
Cc: Leif Lindholm <leif.lindholm@linaro.org>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Jordan Justen <jordan.l.justen@intel.com>
Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
Reviewed-by: Michael D Kinney <michael.d.kinney@intel.com>
Reviewed-by: Andrew Fish <afish@apple.com>

diff --git a/Maintainers.txt b/Maintainers.txt
index b032bc7f243f81cc0d2f64efaabcd02f768723ea..fd5c97605619731f312a130dd60d39cb4a42047e 100644 (file)
--- a/Maintainers.txt
+++ b/Maintainers.txt
@@ -5,7 +5,8 @@ This file provides information about the primary maintainers for
 EDK II.\r
 \r
 In general, you should not privately email the maintainer. You should\r
-email the edk2-devel list, but you can also Cc the maintainer.\r
+email the edk2-devel list, and Cc the package maintainers and\r
+reviewers.\r
 \r
 Descriptions of section entries:\r
 \r
@@ -13,6 +14,8 @@ Descriptions of section entries:
      Patches and questions should be sent to the email list.\r
   M: Package Maintainer: Cc address for patches and questions. Responsible\r
      for reviewing and pushing package changes to source control.\r
+  R: Package Reviewer: Cc address for patches and questions. Reviewers help\r
+     maintainers review code, but don't have push access.\r
   W: Web-page with status/info\r
   T: SCM tree type and location.  Type is one of: git, svn.\r
   S: Status, one of the following:\r