Maintainers.txt: clarify Reviewer requirements and responsibilities

The current language for "Package Reviewer" only vaguely hints that
Package Reviewers should be able to provide guidance and directions.
Make this more obvious.

Cc: Andrew Fish <afish@apple.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Leif Lindholm <leif.lindholm@linaro.org>
Cc: Liming Gao <liming.gao@intel.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Philippe Mathieu-Daude <philmd@redhat.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
Reviewed-by: Andrew Fish <afish@apple.com>
Reviewed-by: Philippe Mathieu-Daude <philmd@redhat.com>
This commit is contained in:
Laszlo Ersek 2019-02-27 22:10:45 +01:00
parent 89910a39dc
commit c9e1e28b61
1 changed files with 4 additions and 1 deletions

View File

@ -20,7 +20,10 @@ Descriptions of section entries:
M: Package Maintainer: Cc address for patches and questions. Responsible
for reviewing and pushing package changes to source control.
R: Package Reviewer: Cc address for patches and questions. Reviewers help
maintainers review code, but don't have push access.
maintainers review code, but don't have push access. A designated Package
Reviewer is reasonably familiar with the Package (or some modules
thereof), and/or provides testing or regression testing for the Package
(or some modules thereof), in certain platforms and environments.
W: Web-page with status/info
T: SCM tree type and location. Type is one of: git, svn.
S: Status, one of the following: