From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Andrew Fish <afish@apple.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
Liming Gao <liming.gao@intel.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [PATCH] Maintainers.txt: clarify Reviewer requirements and responsibilities
Date: Thu, 28 Feb 2019 11:41:08 +0100 [thread overview]
Message-ID: <50b68bd7-ba8b-e2a3-f653-7f54979fe1b4@redhat.com> (raw)
In-Reply-To: <20190227212157.20107-1-lersek@redhat.com>
On 2/27/19 10:21 PM, Laszlo Ersek wrote:
> 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>
> ---
>
> Notes:
> - this is clearly a political patch; feel free to disagree
> - I'm proposing this for the next development cycle
>
> Maintainers.txt | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/Maintainers.txt b/Maintainers.txt
> index 7772926b2fb1..ed090aeb4bdb 100644
> --- a/Maintainers.txt
> +++ b/Maintainers.txt
> @@ -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.
Definitively an improvement, thanks for clarifying this.
Reviewed-by: Philippe Mathieu-Daude <philmd@redhat.com>
> W: Web-page with status/info
> T: SCM tree type and location. Type is one of: git, svn.
> S: Status, one of the following:
>
next prev parent reply other threads:[~2019-02-28 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 21:21 [PATCH] Maintainers.txt: clarify Reviewer requirements and responsibilities Laszlo Ersek
2019-02-28 1:12 ` Gao, Liming
2019-02-28 1:14 ` Andrew Fish
2019-02-28 10:41 ` Philippe Mathieu-Daudé [this message]
2019-03-08 20:13 ` Laszlo Ersek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50b68bd7-ba8b-e2a3-f653-7f54979fe1b4@redhat.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox