From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.81]) by mx.groups.io with SMTP id smtpd.web11.897.1576001806022428638 for ; Tue, 10 Dec 2019 10:16:46 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=L9FLz7pa; spf=pass (domain: redhat.com, ip: 207.211.31.81, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1576001805; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SDW/aQy7j2/kIamL48molok229RNB66DaV8cWvaPcaE=; b=L9FLz7papfDzlOi8r80ElkVp3F4/s83mhe3YMSyqzFNOhO1mCnlbFQ+52ETYsDHPZLw9O5 W2JsbN7+GwEHB02sZyl1W+4rOiGVHNsCTHqNehbdj3zYY98vZ8AgdhFSl9MCtQE8w2C7MX QTLkRcFXVi+gxx2rDyZOuwkjWuu/P6s= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-313-r5CLKm5iPNCiDOQkjzV9-Q-1; Tue, 10 Dec 2019 13:16:41 -0500 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 22C7E107ACC4; Tue, 10 Dec 2019 18:16:40 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-225.ams2.redhat.com [10.36.116.225]) by smtp.corp.redhat.com (Postfix) with ESMTP id 9CBDD60BE0; Tue, 10 Dec 2019 18:16:38 +0000 (UTC) Subject: Re: [edk2-devel] [PATCH] Maintainers.txt: Update reviewer email address From: "Laszlo Ersek" To: "Rabeda, Maciej" , "devel@edk2.groups.io" , "Wu, Jiaxin" , Maciej Rabeda , "Kinney, Michael D" , "Gao, Liming" Cc: "Fu, Siyuan" References: <20191206162855.2155-1-maciej.rabeda@linux.intel.com> <895558F6EA4E3B41AC93A00D163B727416FBF2B4@SHSMSX107.ccr.corp.intel.com> <077c152f-22f8-ce29-ccaa-10874d5e8381@redhat.com> Message-ID: <4f871fba-6347-e0d0-20ce-bfef476a3f05@redhat.com> Date: Tue, 10 Dec 2019 19:16:37 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-MC-Unique: r5CLKm5iPNCiDOQkjzV9-Q-1 X-Mimecast-Spam-Score: 0 Content-Language: en-US Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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 >