From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by mx.groups.io with SMTP id smtpd.web12.2636.1576015552127767763 for ; Tue, 10 Dec 2019 14:05:52 -0800 Authentication-Results: mx.groups.io; dkim=fail reason="body hash did not verify" header.i=@intel.onmicrosoft.com header.s=selector2-intel-onmicrosoft-com header.b=M/aL2aBG; spf=pass (domain: intel.com, ip: 192.55.52.136, mailfrom: maciej.rabeda@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Dec 2019 14:05:52 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,301,1571727600"; d="scan'208";a="413270826" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga005.fm.intel.com with ESMTP; 10 Dec 2019 14:05:51 -0800 Received: from fmsmsx162.amr.corp.intel.com (10.18.125.71) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 10 Dec 2019 14:05:51 -0800 Received: from FMSEDG002.ED.cps.intel.com (10.1.192.134) by fmsmsx162.amr.corp.intel.com (10.18.125.71) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 10 Dec 2019 14:05:51 -0800 Received: from NAM02-BL2-obe.outbound.protection.outlook.com (104.47.38.53) by edgegateway.intel.com (192.55.55.69) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 10 Dec 2019 14:05:51 -0800 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UJaRzmFfEZgmK/yqoWjQ5G4/3ge1gYF8MiA6ukxRpT0ERsHyhrO8uTJSgkd7vobgHmc+gP1lIGaEvosCuPBTqz4yiC7pPlHnJnHnv4yl+n8xm0Gadr07dVVKvCVHbDAVKMYEmtAi/H3ATvs5SgD+1Xgm54lzAdKeoRnlQ36zbENAE36qOICUjcEqaW0FnLqayKx9wIgEbSEf9+dv0FRhUNToQ/J+O/NgR5MrGhSOc/NnTNOD0v8SszfQrfDyxpcnhvFAjyzAtpzUKNnPTd/UiL8wVPReDHgrfzBMWFAlP5sinm3p2G1+3oxC/QMbNaoFRWvs5qBRa4HWGwqAHedCDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Gw+8DLi9+6pLC2MkcC3zg8FMwtmmebZnnDCyEJ7XJWs=; b=kXW4MGIPgkExTRBGGMjaDgbQ1+W+u+7RrfDJfOCUVYgdCx9fJm8y85ZvGBEhV7RSo12MZiKWff9lEOc99NNk9cT2azjsezHMb4OA5IWA61yO+OEaSQMD1yFxI+f0IvFCsWpl2z7+yIPbobGXpRiVul34X/d5XiRRTtYRLcxbpTs5RAdbHAFUlitd9x6Km1j3i+Lc6HqVhbq8SyDuiTEzjxJIXR6kWAT57/cuSLzM0Lez+QHwkC3wA+a48F4vw74Tg3hP5O6wfIDjq02lcKk96rpvuQMC+AcMeyFQnpmuIcQcfcYzQZ+qKGxVgPFv3GNYC7DN5vAj7eKti4e3482EpQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel.onmicrosoft.com; s=selector2-intel-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Gw+8DLi9+6pLC2MkcC3zg8FMwtmmebZnnDCyEJ7XJWs=; b=M/aL2aBGwv9I28bntT6Mz7KQLNqVZpodpyGAluksM5zWxxHtQRkop7Rku2ovEOS5QE6SRGDOI2WxaYPftv5ew+sgMvyHu7ABfXMMEJv/mh/s9c0wfi8pY7VFVxfmkbWAxrGvxYPYljkL+LTy0OriE9h7Zg564EZlLJe1kRajJxA= Received: from BYAPR11MB3527.namprd11.prod.outlook.com (20.177.226.90) by BYAPR11MB3253.namprd11.prod.outlook.com (20.177.127.95) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2495.22; Tue, 10 Dec 2019 22:05:48 +0000 Received: from BYAPR11MB3527.namprd11.prod.outlook.com ([fe80::710d:6e83:7ce:6f3c]) by BYAPR11MB3527.namprd11.prod.outlook.com ([fe80::710d:6e83:7ce:6f3c%6]) with mapi id 15.20.2516.017; Tue, 10 Dec 2019 22:05:48 +0000 From: "Rabeda, Maciej" To: "Kinney, Michael D" , "devel@edk2.groups.io" , "lersek@redhat.com" , "Wu, Jiaxin" , Maciej Rabeda , "Gao, Liming" CC: "Fu, Siyuan" Subject: Re: [edk2-devel] [PATCH] Maintainers.txt: Update reviewer email address Thread-Topic: [edk2-devel] [PATCH] Maintainers.txt: Update reviewer email address Thread-Index: AQHVrFJuxG2GIZdga0mj8hME+xvvEqey30WAgAAwaYCAAAsbAIAABKoggAA03oCAACcDwIAAN5IAgAAAYYCAAAMKAIAAO+lA Date: Tue, 10 Dec 2019 22:05:48 +0000 Message-ID: References: <20191206162855.2155-1-maciej.rabeda@linux.intel.com> <895558F6EA4E3B41AC93A00D163B727416FBF2B4@SHSMSX107.ccr.corp.intel.com> <077c152f-22f8-ce29-ccaa-10874d5e8381@redhat.com> <4f871fba-6347-e0d0-20ce-bfef476a3f05@redhat.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNzM4NjAzYjAtOGFkMC00NGM0LTgwMGUtMzQ4NzZjY2I3MzQ3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiVTFPMWVQOXdDaVAyMEI0SmliNE9rYkpiVTZUSVhTMTNvaDMraktyUE9rSDQ5XC9UQWJYazRzNDVhY0o4bDhUS1cifQ== dlp-reaction: no-action dlp-version: 11.2.0.6 authentication-results: spf=none (sender IP is ) smtp.mailfrom=maciej.rabeda@intel.com; x-originating-ip: [192.198.151.191] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: d0044ac4-1a57-4c97-07e0-08d77dbd1d28 x-ms-traffictypediagnostic: BYAPR11MB3253: x-ld-processed: 46c98d88-e344-4ed4-8496-4ed7712e255d,ExtAddr x-ms-exchange-transport-forked: True x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-forefront-prvs: 02475B2A01 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(366004)(13464003)(199004)(189003)(966005)(66446008)(66946007)(86362001)(53546011)(8676002)(76116006)(66556008)(64756008)(52536014)(15650500001)(26005)(186003)(66476007)(5660300002)(6506007)(7696005)(8936002)(71200400001)(33656002)(498600001)(9686003)(55016002)(81166006)(6636002)(110136005)(81156014)(2906002)(4326008);DIR:OUT;SFP:1102;SCL:1;SRVR:BYAPR11MB3253;H:BYAPR11MB3527.namprd11.prod.outlook.com;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;A:1;MX:1; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: SdWJzLnS2MwJlt/fPHhp3g8098Ir9shol/DvfJfPwDEAHZLCiQ4KT23DKElDWJcjYQqTW9sdMMgW/JOm8ru8ni0mO0tm4E4daR4sPtk8SqudBUAezf5ZtkVNTs7ORjtGTkBRQsgmaKuQz/tLr/+/dXga3c15OSyZwLiXdc5qmoVHC7QzIIWst/K5CtvzfHdAB0m3Z57y78OzPD2d6NckWpg369UoB3C58ZMUXVt1m3BttRRajdD6lPHG1hFRN4BqVBdk53aMn/j8exuEY17RQaY1XROAVb6+s43LnfEpFMELgjPCXdS2wOaiW/FxFM+3t6fjj5HA1TIEvXqMmx3ywd/kOw2ML5MwXZg4QEJMwTXxr28Ii+zAifr0USWSMcmPBSeDaOA4+bZEMRu7kRypPd8SYIKYbhLsw3o5KONXPRLFijR01LpcG/NSpryX2FxjK4zCaw825wCF47z5eL2U0zj6HoAHy+8a2Dk1OED7gehFQ6uYGI3L8fLyVICHTRrwvz7tSgRtsT7/Jnr8bPvbQixA6vcWbGQkNia4EJOTORg= MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: d0044ac4-1a57-4c97-07e0-08d77dbd1d28 X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Dec 2019 22:05:48.6279 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: /xgX68iBZH+qKgGmy3GAqO4JeFdhiIdz174tBP3tNo629ojergyuh7nU5Tt79/PtXn8aM7qd7ZCMrhufx76SCw== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3253 Return-Path: maciej.rabeda@intel.com X-OriginatorOrg: intel.com Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Mike, Laszlo, Jiaxin, I think everything is clear now, thanks for explanations! I will produce a v2 of the patch with updated email address and role. We'll keep 2 maintainers for NetworkPkg for the time being. Thanks! Maciej -----Original Message----- From: Kinney, Michael D =20 Sent: Tuesday, December 10, 2019 19:28 To: devel@edk2.groups.io; lersek@redhat.com; Rabeda, Maciej ; Wu, Jiaxin ; Maciej Rabeda ; Gao, Liming ; Kinney, Michael D Cc: Fu, Siyuan Subject: RE: [edk2-devel] [PATCH] Maintainers.txt: Update reviewer email a= ddress Hi Maciej, Once a patch review is complete that updates Maintainers.txt with a new ma= intainer, one of the existing maintainers should submit a PR to get Maintai= ner.txt updated in edk2/master. In the corner case where none of the exist= ing maintainers are available to submit this PR, one of the stewards can su= pport this PR. At that point, the new maintainer needs to be added to the TianoCore EDK I= I Maintainers Team so the new maintainer has The ability to set the 'push' = label on PRs they want merged into edk2/master. The new maintainer should send an email to the mailing list requesting mem= bership in the TianoCore EDK II Maintainers team. Thanks, Mike > -----Original Message----- > From: devel@edk2.groups.io On Behalf Of Laszlo=20 > Ersek > Sent: Tuesday, December 10, 2019 10:17 AM > To: Rabeda, Maciej ; devel@edk2.groups.io;=20 > Wu, Jiaxin ; Maciej Rabeda=20 > ; Kinney, Michael D=20 > ; Gao, Liming > Cc: Fu, Siyuan > Subject: Re: [edk2-devel] [PATCH] Maintainers.txt: > Update reviewer email address >=20 > 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=20 > >> 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=20 > 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. >=20 > Seems like there is a subgroup (?) called=20 > "tianocore/edk-ii-maintainers". >=20 > Thanks > Laszlo >=20 > >> 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 > > >=20 >=20 >=20 -------------------------------------------------------------------- Intel Technology Poland sp. z o.o. ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wyd= zial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-3= 16 | Kapital zakladowy 200.000 PLN. Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresat= a i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej w= iadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakie= kolwiek przegladanie lub rozpowszechnianie jest zabronione. This e-mail and any attachments may contain confidential material for the = sole use of the intended recipient(s). If you are not the intended recipien= t, please contact the sender and delete all copies; any review or distribut= ion by others is strictly prohibited.