public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: "Rabeda, Maciej" <maciej.rabeda@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Wu, Jiaxin" <jiaxin.wu@intel.com>,
	Maciej Rabeda <maciej.rabeda@linux.intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Gao, Liming" <liming.gao@intel.com>
Cc: "Fu, Siyuan" <siyuan.fu@intel.com>
Subject: Re: [edk2-devel] [PATCH] Maintainers.txt: Update reviewer email address
Date: Tue, 10 Dec 2019 19:16:37 +0100	[thread overview]
Message-ID: <4f871fba-6347-e0d0-20ce-bfef476a3f05@redhat.com> (raw)
In-Reply-To: <d6f4df7d-389f-5719-4698-a68279e9fc29@redhat.com>

On 12/10/19 19:15, Laszlo Ersek wrote:
> On 12/10/19 16:01, Rabeda, Maciej wrote:
>> Laszlo,
>>
>> Thanks for a thorough explanation of the process :)
>> It looks like one extra step for maintainership transition seems is identified: 
>> "However (AIUI), the mergify bot will reject and close any PR with the "push" label set if the PR was not submitted by a maintainer in the first place"
>>
>> For maintainer identification process, where does the mergify bot get the maintainer list from?
> 
> I *think* it is represented through membership in the "tianocore"
> organization on github.com.
> 
>   https://github.com/orgs/tianocore/people
> 
> I'm not sure but I imagine different people could have different
> permissions associated with them, in this org.

Seems like there is a subgroup (?) called "tianocore/edk-ii-maintainers".

Thanks
Laszlo

>> Do you know who should I ask to be added to that list?
> 
> If I remember correctly, Mike can manage such memberships / rights.
> 
> Thanks!
> Laszlo
> 


  reply	other threads:[~2019-12-10 18:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 16:28 [PATCH] Maintainers.txt: Update reviewer email address Maciej Rabeda
2019-12-10  5:37 ` Wu, Jiaxin
2019-12-10  8:35   ` [edk2-devel] " Rabeda, Maciej
2019-12-10  9:10     ` Laszlo Ersek
2019-12-10  9:32       ` Rabeda, Maciej
2019-12-10 12:36         ` Laszlo Ersek
2019-12-10 15:01           ` Rabeda, Maciej
2019-12-10 18:15             ` Laszlo Ersek
2019-12-10 18:16               ` Laszlo Ersek [this message]
2019-12-10 18:27                 ` Michael D Kinney
2019-12-10 22:05                   ` Rabeda, Maciej
2019-12-10 10:27       ` Philippe Mathieu-Daudé

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=4f871fba-6347-e0d0-20ce-bfef476a3f05@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