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"<https://github.com/tianocore/edk2/blob/master/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 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<https://github.com/tianocore/tianocore.github.io/wiki/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 persons.
A people who has strong technical expertise might NOT 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.groups.io> On Behalf Of Yao, Jiewen
Sent: Saturday, September 26, 2020 1:09 PM
To: devel@edk2.groups.io; Guptha, Soumya K <soumya.k.gup...@intel.com>; 
annou...@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, with 
title "more development process failure".

I feel the process mentioned in 
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Process
 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<https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Process>"
 and make "the process" simpler and clearer.

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

Thank you
Yao Jiewen


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


Dear Community members,



I have drafted a document "who we are", explaining Tianocore community 
structure, members of the community, their role and the current development 
process. 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 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 live on 
our TianoCore wiki site.



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

Thanks,
Soumya

Soumya Guptha
TianoCore Community Manager





-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#65655): https://edk2.groups.io/g/devel/message/65655
Mute This Topic: https://groups.io/mt/77127763/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Reply via email to