From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by mx.groups.io with SMTP id smtpd.web10.5640.1601098384941645104 for ; Fri, 25 Sep 2020 22:33:05 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@intel.onmicrosoft.com header.s=selector2-intel-onmicrosoft-com header.b=SrctZKSv; spf=pass (domain: intel.com, ip: 192.55.52.115, mailfrom: jiewen.yao@intel.com) IronPort-SDR: ahRu1IFugfOlNk1Ry/9atoZ2ApmKt2RRSfcrGt1+stnGdbvs87XyhXHgzc1F5tfRcGL1jQAcGE FhhJrS3nBA5Q== X-IronPort-AV: E=McAfee;i="6000,8403,9755"; a="160950203" X-IronPort-AV: E=Sophos;i="5.77,303,1596524400"; d="scan'208,217";a="160950203" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Sep 2020 22:33:03 -0700 IronPort-SDR: 1vxc77/OdHmcdPOlHrstC1rbshnq8Zc3dSovep8UQ7AXIoYUOp/7jtloINeF/PBFLjAJCc5bhf kd876b6K8FJw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,303,1596524400"; d="scan'208,217";a="292188162" Received: from orsmsx603.amr.corp.intel.com ([10.22.229.16]) by fmsmga007.fm.intel.com with ESMTP; 25 Sep 2020 22:33:03 -0700 Received: from orsmsx601.amr.corp.intel.com (10.22.229.14) by ORSMSX603.amr.corp.intel.com (10.22.229.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Fri, 25 Sep 2020 22:33:03 -0700 Received: from ORSEDG601.ED.cps.intel.com (10.7.248.6) by orsmsx601.amr.corp.intel.com (10.22.229.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5 via Frontend Transport; Fri, 25 Sep 2020 22:33:03 -0700 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (104.47.57.174) by edgegateway.intel.com (134.134.137.102) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1713.5; Fri, 25 Sep 2020 22:33:02 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Uw/OdpiV48AsyDbJzvSq9fD45um3HBQU85bzfXN7pVMdJG2YkQAN6y8gRx8OK41oTKZ+fF+/4cdqgjp+6r6yLAYygKXg5OeAtpmFEf8JDQlM9Ha7XROF1svFpGkObBIeDWI7FB5OletLZDwwBUNQbsOuoWAD/XqeSpyKFvw4nd3EODqreF8XN+kVhjKpFoEWTxO0P9wKtyE1EsV8FBIpsU67qr3rSUB0sU/X12/5iY2nEUHsPe9l7VbsC+CC+EhAXcUSnpmZ0cJQ6TyGJh1S7sYaDAB9vIa0XtIeiEE4F89vBsD+Xt0ZihFqsrpNOYQ2zq9UfxYO/LNtcGZf/AxlaQ== 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=061MP7Ibq6AFuFo+ez5tYxY98yQdKilt6L3ToDYx3zc=; b=N+iUk+G6EFimlt9dJQ5XvfefL386Q48jzoEHbuRWzBiFrsE2mfnKwRjP+bf+qOGjx8q5buvJH9K48NEXLzCd8jq0CmhQx+YeZWmIx7ttTxsPAPmT7bAAXkYHhez0g73WCla/QLA7VHGihT8LS+4m6/VE9c/tLP/US0DCuZfzLnYeAf50GZMjVYm1FBqDrOe3YkaqvNjXFgwUEJmdp9LU+yKiQeTGxB2fcZuYpA0b7LjyylyL/+Hj6c1seG4hrUL828gVO/csloUYp/gCEh7TPTwbcEQpIkWUnT1VMQ1g91sePeT4ZNWhZl6t6YnUpz3RU2EBBJ0m0GAoPH/FQWfQmw== 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=061MP7Ibq6AFuFo+ez5tYxY98yQdKilt6L3ToDYx3zc=; b=SrctZKSvZdbk5SSWOHd6R08Sjytpc4ozz/EArWl4qMxv014A4HoSLHGvXDU2cwrjEs9JGPA7C+CHQz209YvAXdHkC8b4c3oDsrc6CNZa+ASuoAhg+ABTnqXWh6Tj+kiVG/yyI+Y/hjwQ4meVx6j4RXbhnMaVNB7NZG/X5ZdI1Is= Received: from CY4PR11MB1288.namprd11.prod.outlook.com (2603:10b6:903:23::8) by CY4PR11MB0055.namprd11.prod.outlook.com (2603:10b6:910:76::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16; Sat, 26 Sep 2020 05:32:57 +0000 Received: from CY4PR11MB1288.namprd11.prod.outlook.com ([fe80::8948:caa4:ca1a:23ac]) by CY4PR11MB1288.namprd11.prod.outlook.com ([fe80::8948:caa4:ca1a:23ac%10]) with mapi id 15.20.3412.024; Sat, 26 Sep 2020 05:32:57 +0000 From: "Yao, Jiewen" To: "devel@edk2.groups.io" , "Yao, Jiewen" , "Guptha, Soumya K" , "announce@edk2.groups.io" Subject: Re: [edk2-devel] Tianocore community page on who we are - please review Thread-Topic: [edk2-devel] Tianocore community page on who we are - please review Thread-Index: AdaTi5w7FAcVBMjNSpCYPmFHBqzGAAANihBwAADEr9A= Date: Sat, 26 Sep 2020 05:32:57 +0000 Message-ID: References: <16383D375E5994D7.27235@groups.io> In-Reply-To: <16383D375E5994D7.27235@groups.io> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-version: 11.5.1.3 dlp-product: dlpe-windows dlp-reaction: no-action authentication-results: edk2.groups.io; dkim=none (message not signed) header.d=none;edk2.groups.io; dmarc=none action=none header.from=intel.com; x-originating-ip: [101.80.124.211] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 532ffae2-33eb-41b2-297d-08d861dda05e x-ms-traffictypediagnostic: CY4PR11MB0055: x-ms-exchange-transport-forked: True x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: aj9ypYuPJZNXfRX1uHYYaLOn15gMktdIiAzxbfGHt3K0LGy84wYdclV/dhgBAhQt1BZFqdZCMGOwBfeDpMMn2Xhjk610LpkDDSDMxFE3cvELfQtrcChywRmEXH+42bQ6QKQn88fa+cyuxOVYjMPIBHME3oadE9KMilfSX4AfgDPa0f0gP0kn/l7+0EeIqcwzwZN0H09xqeWpVhJo25fDf/aBb3PDV73qNjxMAcuRTexi4tgMOdCCx9XzJZ1FhRwyGCddyvKzqWJDosNeSm467PeAOZIaLgj2zn0caAGX/27PZrc//OrAfoy/O5hm9IpQuihesulX8IHE8a7El2D5pztLb/bNeW3O/Z7OGddT/M3vwGXBPLRLF+aQhHaY+id++oV78+8pdgph9a++fZutbruvnY+fc53pRmoEgL5PdDyf8NruGDMAgbXGAWqTspzLW0LgQt81StPnmFUi/3kbFQ== x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:CY4PR11MB1288.namprd11.prod.outlook.com;PTR:;CAT:NONE;SFS:(4636009)(376002)(39860400002)(136003)(346002)(366004)(396003)(71200400001)(76236003)(66556008)(26005)(2906002)(76116006)(66946007)(166002)(66476007)(66446008)(5660300002)(966005)(110136005)(8936002)(6506007)(53546011)(52536014)(7696005)(186003)(64756008)(316002)(33656002)(8676002)(83380400001)(9686003)(478600001)(55016002)(450100002)(86362001);DIR:OUT;SFP:1102; x-ms-exchange-antispam-messagedata: OWkGu5j6a6Y6jtGyKmGgdicqzCiGZUjlAk7cIgVpQ3Lz57H+1SDElx2oo8aRZX7V9jm+2ZvZOFqabjo3kL9aJ6XYY65ophPVyLnquSmFGjOu9yprCADF+7OZ627AoBhwII9jc93HaZjYD8sVYuuD2Her0lNJ4SNDYVQ10GwdHLVjN8DKq0SR3gvnFBFfvwOmqOIJtJ+AxIcJOOjC4EN7eb86D5azF0u7hAnnAz752nE+FKLSsmSjITMxysitJi7EdDkjUvR5HU0z7APmrFZPx4Z95NL/pS9GQgjH57guEaXyuQBWb78kI7qmWZ3np6HLMyMOWsJQVRP9S/H60M8R12cB11VTvgj26dW4Kd23BRujZP9wqV/mEsFh1npIEWegeuIpbciMyfBdI2/PVOD00ZrdrExAyj6wBlRjH0NHM8SjA+86oud5/+65FB9e2BwM/BNe+rNvEzVh/Z6zJMNaNqUgNn2qWPPQiWS4k+vR7HMnGWQbtw4kfUos1FYnVD+RaMnxLYjNYxJ1k5F6/sD+dTSMNYrVxcJr6LLcxTOeHzDIM/tZIm/cqoHiXB/C0ixXkDXp0rEduYbOJG0MEa58o/YtkAf14tdMpm1QQyuj717xwdxca308RkZqhNdv21ZvfWfYaFGnllfzM3ZqGsGNkg== MIME-Version: 1.0 X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: CY4PR11MB1288.namprd11.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 532ffae2-33eb-41b2-297d-08d861dda05e X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Sep 2020 05:32:57.7658 (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: 9y9gcYLsdPgdU9dJqnEqlF59FaBvMzmpzhJtWHBM1umgb+XGgH3yjaGLNlLAqbLbGnE3GFXk1xaZhsKlX48uJQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR11MB0055 Return-Path: jiewen.yao@intel.com X-OriginatorOrg: intel.com Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_CY4PR11MB12886380EB18A4353047B8F08C370CY4PR11MB1288namp_" --_000_CY4PR11MB12886380EB18A4353047B8F08C370CY4PR11MB1288namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Some other thought is about maintainer's role definition: The role of a maintainer is to: 1. Maintainer assignments to packages and source file name patterns are= provided in the "Maintainers.txt" file. 2. Subscribe to the "edk2-bugs" mailing list https://edk2.groups.io/g/b= ugs, which propagates TianoCore Bugzilla https://bugzilla.tianocore.org/ ac= tions via email. Keep a close eye on new issues reported for their assigned= packages. Participate in triaging and analyzing bugs filed for their assig= ned packages. 3. Responsible for reviewing patches and answering questions from contr= ibutors, on the edk2-devel mailing list https://edk2.groups.io/g/devel/. 4. Responsible for coordinating patch review with co-maintainers and re= viewers of the same package. 5. Has push / merge access to the merge branch. 6. Responsible for merging approved patches into the master branch. 7. Follow the EDK II development process. IMHO, the 1~4 need technical expertise, while 5~7 need process expertise. Logically, the can be two separated roles and be done by two different per= sons. A people who has strong technical expertise might NOT be the best person t= o do the integration, and vice versa. I hope we can let right person do rig= ht thing in right way. For example, to avoid mistake during check in, 5~7 can be done by a role n= amed "integrator". My dream is that check-in process is just one click button. But it seems w= e are still far from it... My two cents. Thank you Yao Jiewen From: devel@edk2.groups.io On Behalf Of Yao, Jiewen Sent: Saturday, September 26, 2020 1:09 PM To: devel@edk2.groups.io; Guptha, Soumya K ; an= nounce@edk2.groups.io Subject: Re: [edk2-devel] Tianocore community page on who we are - please = review Thanks Soumya. I think this is a good start. Recently we are discussing the maintainer's work in EDKII mailing list, wi= th title "more development process failure". I feel the process mentioned in https://github.com/tianocore/tianocore.git= hub.io/wiki/EDK-II-Development-Process is not clear enough to follow, espec= ially for the maintainer who is not full time working on EDKII. I wish we can have this opportunity to revisit the "Follow the EDK II deve= lopment process" and make "the process" simpler and clearer. Then all maintainers can sign to follow one rule. The rule we define and t= he rule we agree with. Thank you Yao Jiewen From: devel@edk2.groups.io > On Behalf Of Soumya Guptha Sent: Saturday, September 26, 2020 6:35 AM To: announce@edk2.groups.io; devel@edk2.gr= oups.io Subject: [edk2-devel] Tianocore community page on who we are - please revi= ew Dear Community members, I have drafted a document "who we are", explaining Tianocore community str= ucture, members of the community, their role and the current development pr= ocess. I have drafted this document with the help of the Tianocore Stewards= . We view this as a living document, as our development processes evolve, I = will keep this document updated. Please review the draft version of the document (link below) and provide y= our feedback. Please send it to me, no need to reply all. I appreciate your input by Friday, Oct 2. After this, I plan on make it li= ve on our TianoCore wiki site. Link: https://github.com/tianocore/tianocore.github.io/wiki/Who-we-are Thanks, Soumya Soumya Guptha TianoCore Community Manager --_000_CY4PR11MB12886380EB18A4353047B8F08C370CY4PR11MB1288namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Some other thought is about maintainer’s role= definition:

 

The role of a maintainer is to:

  1. Maintainer assignments to packages and source file name patterns are pro= vided in the "Maintainers.txt"=  file.
  2. Subscribe to the "edk2-bugs" mailing list https://edk2.groups.io/= g/bugs, which propagates TianoCore Bugzilla https://bugzilla.tianocore.org/ actions via email. Keep a close eye on new issues reported for their assigned pac= kages. Participate in triaging and analyzing bugs filed for their assigned = packages.
  3. Responsible for reviewing patches and answering questions from contribut= ors, on the edk2-devel mailing list https://edk2.groups.io/g/devel/= Responsible for coordinating patch review with co-maintainers and review= ers of the same package.
  4. Has push / merge access to the merge branch.
  5. Responsible for merging approved patches into the master branch.
  6. Follow the EDK II development process.

 

IMHO, the 1~4 need technical expertise, while 5~7 n= eed process expertise.

Logically, the can be two separated roles and be do= ne by two different persons.

A people who has strong technical expertise might N= OT be the best person to do the integration, and vice versa. I hope we can = let right person do right thing in right way.

For example, to avoid mistake during check in, 5~7 = can be done by a role named “integrator”.

 

My dream is that check-in process is just one click= button. But it seems we are still far from it…

 

My two cents.

 

Thank you

Yao Jiewen

 

From: devel@edk2.groups.io <devel@edk2.gr= oups.io> On Behalf Of Yao, Jiewen
Sent: Saturday, September 26, 2020 1:09 PM
To: devel@edk2.groups.io; Guptha, Soumya K <soumya.k.guptha@inte= l.com>; announce@edk2.groups.io
Subject: Re: [edk2-devel] Tianocore community page on who we are - = please review

 

Thanks Soumya. I think this is a good start.

 

Recently we are discussing the maintainer’s w= ork in EDKII mailing list, with title “more development process failu= re”.

 

I feel the process mentioned in https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-P= rocess is not clear enough to follow, especially for the maintainer who= is not full time working on EDKII.

 

I wish we can have this opportunity to revisit the = “Follow the EDK II development = process” and make “the process” simpler and clearer.

 

Then all maintainers can sign to follow one rule. T= he rule we define and the rule we agree with.

 

Thank you

Yao Jiewen

 

 

From: devel@edk2.groups.io <deve= l@edk2.groups.io> On Behalf Of Soumya Guptha
Sent: Saturday, September 26, 2020 6:35 AM
To: announce@edk2.groups= .io; devel@edk2.groups.io
Subject: [edk2-devel] Tianocore community page on who we are - plea= se review

 

Dear Community members,

 

I have drafted a document “who we are̶= 1;, explaining Tianocore community structure, members of the community, the= ir role and the current development process. I have drafted this document w= ith the help of the Tianocore Stewards.

We view this as a living document, as our develo= pment processes evolve, I will keep this document updated.

 

Please review the draft version of the document = (link below) and provide your feedback. Please send it to me, no need to re= ply all.

I appreciate your input by Friday, Oct 2. After = this, I plan on make it live on our TianoCore wiki site.

 

Link: https://github.com/tianocore/tianocore.github.io/wiki/Who-we-are<= /o:p>

 

Thanks,

Soumya

 

Soumya Guptha
TianoCore Community Manager

 

--_000_CY4PR11MB12886380EB18A4353047B8F08C370CY4PR11MB1288namp_--