From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.byosoft.com.cn (mail.byosoft.com.cn [58.240.74.242]) by mx.groups.io with SMTP id smtpd.web12.5271.1601173982313827932 for ; Sat, 26 Sep 2020 19:33:04 -0700 Authentication-Results: mx.groups.io; dkim=missing; spf=none, err=permanent DNS error (domain: byosoft.com.cn, ip: 58.240.74.242, mailfrom: gaoliming@byosoft.com.cn) Received: from DESKTOPS6D0PVI ([58.246.60.130]) (envelope-sender ) by 192.168.6.13 with ESMTP for ; Sun, 27 Sep 2020 10:32:55 +0800 X-WM-Sender: gaoliming@byosoft.com.cn X-WM-AuthFlag: YES X-WM-AuthUser: gaoliming@byosoft.com.cn From: "gaoliming" To: , , "'Guptha, Soumya K'" , Cc: , "'Leif Lindholm \(Nuvia address\)'" , "'Kinney, Michael D'" , "'Andrew Fish'" References: <16383D375E5994D7.27235@groups.io> In-Reply-To: Subject: =?UTF-8?B?5Zue5aSNOiBbZWRrMi1kZXZlbF0gVGlhbm9jb3JlIGNvbW11bml0eSBwYWdlIG9uIHdobyB3ZSBhcmUgLSBwbGVhc2UgcmV2aWV3?= Date: Sun, 27 Sep 2020 10:32:55 +0800 Message-ID: <005f01d69476$81768bd0$8463a370$@byosoft.com.cn> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQHwLRIG9ZiwLFukWDf+vDJNOEkqVQHpoYseAgD3EmypKTDIMA== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0060_01D694B9.8F9B2B60" Content-Language: zh-cn ------=_NextPart_000_0060_01D694B9.8F9B2B60 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Jiewen: Now, we have reviewer and maintainer role. Reviewer takes role 1~4. Maintainer takes role 1~7. If the people know edk2 process well, they most= ly know edk2 one or more packages (modules). So, they can take Maintainer rol= e. If the people only focus on the technical review, they can take reviewer role. I would suggest there is at lease one Maintainer for each package. There are more reviewers for each package. =20 Soumya: Here are my comments.=20 Guidelines for a Maintainer. Never let a pending request get older than = a calendar week. This requirement is too strict to the maintainer or reviewe= r. The maintainer or reviewer should try to give the response in one week. Bu= t, they may not fully review one patch set in one week, es for the feature or the complex change.=20 Role of a Contributor/developer. We need to highlight the role & responsibility for the incompatible change. If the contributor proposes th= e incompatible change, he needs to coordinate with the impacted platform maintainer and make the agreement who will follow up to update the impacte= d platforms before he requests to merge his patch set. The impacted platform= s include all ones in Edk2 and Edk2Platforms.=20 =20 Last, this page also needs to include release maintainer Definition and Role. The release maintainer is to create the quarterly stable tag. He tak= es the role to collect the feature planning for each stable tag, schedule the release date, and create the stable tag with the release notes on tag page= . He will also send the announcement of soft feature freeze, hard feature freeze and the stable tag completement to edk2 community.=20 =20 Thanks Liming =B7=A2=BC=FE=C8=CB: bounce+27952+65655+4905953+8761045@groups.io =B4=FA=B1=ED Yao, Jiewen =B7=A2=CB=CD=CA=B1=BC=E4: 2020=C4=EA9=D4=C226=C8=D5 13:33 =CA=D5=BC=FE=C8=CB: devel@edk2.groups.io; Yao, Jiewen ; Guptha, Soumya K ; announce@edk2.groups.io =D6=F7=CC=E2: Re: [edk2-devel] Tianocore community page on who we are - pl= ease review =20 Some other thought is about maintainer=A1=AFs role definition: =20 The role of a maintainer is to: 1. Maintainer assignments to packages and source file name patterns are provided in the " Maintainer= s. 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 packages. Participate in triaging and analyzing bugs filed for their assigned packages. 3. Responsible for reviewing patches and answering questions from contributors, on the edk2-devel mailing list https://edk2.groups.io/g/devel/. 4. Responsible for coordinating patch review with co-maintainers and reviewers 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. =20 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 persons. 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 righ= t thing in right way. For example, to avoid mistake during check in, 5~7 can be done by a role named =A1=B0integrator=A1=B1. =20 My dream is that check-in process is just one click button. But it seems w= e are still far from it=A1=AD =20 My two cents. =20 Thank you Yao Jiewen =20 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 >; announce@edk2.groups.io =20 Subject: Re: [edk2-devel] Tianocore community page on who we are - please review =20 Thanks Soumya. I think this is a good start. =20 Recently we are discussing the maintainer=A1=AFs work in EDKII mailing lis= t, with title =A1=B0more development process failure=A1=B1. =20 I feel the process mentioned in https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-P= ro cess is not clear enough to follow, especially for the maintainer who is n= ot full time working on EDKII. =20 I wish we can have this opportunity to revisit the =A1=B0Follow the EDK II development process=A1=B1 and make =A1=B0the process=A1=B1 simpler and clearer. =20 Then all maintainers can sign to follow one rule. The rule we define and t= he rule we agree with. =20 Thank you Yao Jiewen =20 =20 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.groups.io =20 Subject: [edk2-devel] Tianocore community page on who we are - please revi= ew =20 Dear Community members,=20 =20 I have drafted a document =A1=B0who we are=A1=B1, explaining Tianocore com= munity structure, members of the community, their role and the current developmen= t process. I have drafted this document with the help of the Tianocore Stewards.=20 We view this as a living document, as our development processes evolve, I will keep this document updated.=20 =20 Please review the draft version of the document (link below) and provide your 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.=20 =20 Link: https://github.com/tianocore/tianocore.github.io/wiki/Who-we-are =20 Thanks, Soumya =20 Soumya Guptha TianoCore Community Manager =20 ------=_NextPart_000_0060_01D694B9.8F9B2B60 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Jiewen:

 Now, we have reviewer and maintai= ner role. Reviewer takes role 1~4. Maintainer takes role 1~7. If the people= know edk2 process well, they mostly know edk2 one or more packages (module= s). So, they can take Maintainer role. If the people only focus on the tech= nical review, they can take reviewer role. I would suggest there is at leas= e one Maintainer for each package. There are more reviewers for each packag= e.

 

Soumya:

 Here are m= y comments.

  Guidelines for a Maintainer. Never let a pending request get older than a calendar week. This= requirement is too strict to the maintainer or reviewer. The maintainer or= reviewer should try to give the response in one week. But, they may not fu= lly review one patch set in one week, es for the feature or the complex cha= nge.

Role of a Contributor/developer. We need to highlight the role & responsibility for= the incompatible change. If the contributor proposes the incompatible chan= ge, he needs to coordinate with the impacted platform maintainer and make t= he agreement who will follow up to update the impacted platforms before he = requests to merge his patch set. The impacted platforms include all ones in= Edk2 and Edk2Platforms.

 

Last, this = page also needs to include release maintainer Definition and Role. The rele= ase maintainer is to create the quarterly stable tag. He takes the role to = collect the feature planning for each stable tag, schedule the release date= , and create the stable tag with the release notes on tag page. He will als= o send the announcement of soft feature freeze, hard feature freeze and the= stable tag completement to edk2 community.

 

Thanks<= /span>

Liming

=B7=A2=BC=FE=C8= =CB: bounce+27952+65655+4905953+8761045@groups.io <boun= ce+27952+65655+4905953+8761045@groups.io> =B4=FA=B1=ED Yao, Jiewen
=B7=A2=CB=CD=CA=B1=BC=E4: 2020=C4=EA9=D4=C226=C8=D5 13:33
=CA= =D5=BC=FE=C8=CB: devel@ed= k2.groups.io; Yao, Jiewen <jiewen.yao@intel.com>; Guptha, Soumya K &l= t;soumya.k.guptha@intel.com>; announce@edk2.groups.io
=D6= =F7=CC=E2: Re: [edk2-deve= l] Tianocore community page on who we are - please review=

 <= /o:p>

Some other thought = is about maintainer=A1=AFs role definition:

 

The role of a maintainer is to:=

  1. Maintainer assig= nments 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/bugs, wh= ich propagates TianoCore Bugzilla https://bugzilla.tianocore.org/ actions via email. Keep a close eye on new issues = reported for their assigned packages. Participate in triaging and analyzing= bugs filed for their assigned packages.
  3. Responsi= ble for reviewing patches and answering questions from contributors, on the= edk2-devel mailing list https://edk2.groups.io/g/devel/.
  4. Responsible for coordinating patch re= view with co-maintainers and reviewers 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 techn= ical expertise, while 5~7 need process expertise.

Logically, the can be two separated rol= es and be done by two different persons.

A people who has strong technical expertise migh= t NOT be the best person to do the integration, and vice versa. I hope we c= an let right person do right thing in right way.

For example, to avoid mistake during che= ck in, 5~7 can be done by a role named =A1=B0integrator=A1=B1.

 

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

 <= /span>

My two cents.<= /span>

 <= /p>

Thank you

<= p class=3DMsoNormal>Yao Jiewen

 

From: devel@edk2.groups.io <= ;devel@edk2.groups.io> On= Behalf Of Yao, Jiewen
Sent: Saturday, September 26, 2020 1:0= 9 PM
To: devel@edk2.group= s.io; Guptha, Soumya K <soumya.k.guptha@intel.com>; announce@edk2.groups.io
Subject: Re: [edk2-devel] Tianoco= re community page on who we are - please review

=

 

<= p class=3DMsoNormal>Thanks Soumya. I think this is a goo= d start.

=  

Recently we = are discussing the maintainer=A1=AFs work in EDKII mailing list, with title= =A1=B0more development process failure=A1=B1.

 

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 =A1=B0Follow the EDK II development = process=A1=B1 and make =A1=B0the process=A1=B1 simp= ler and clearer.

 

Then= all maintainers can sign to follow one rule. The rule we define and the ru= le we agree with.

 

Tha= nk you

Yao Jie= wen

 = ;

 =

From: devel@= edk2.groups.io <devel@edk2.g= roups.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 com= munity page on who we are - please review

=

 

Dear Community members,

 <= /p>

I have drafted a document =A1= = =B0who we are=A1=B1, explaining Tianocore community structure, members of = the community, their role and the current development process. I have draft= ed this document with the help of the Tianocore Stewards.

We view this as a living do= cument, as our development processes evolve, I will keep this document upda= ted.

=  

Please re= view the draft version of the document (link below) and provide your feedba= ck. 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 live on our TianoCore wiki site.

 <= /span>

Link: https://github= .com/tianocore/tianocore.github.io/wiki/Who-we-are

 

Thanks,

Soumya

 

Soumya Guptha
TianoCore Community Manager

 

------=_NextPart_000_0060_01D694B9.8F9B2B60--