From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wr1-f43.google.com (mail-wr1-f43.google.com [209.85.221.43]) by mx.groups.io with SMTP id smtpd.web10.34797.1601294214069529289 for ; Mon, 28 Sep 2020 04:56:54 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@nuviainc-com.20150623.gappssmtp.com header.s=20150623 header.b=rvPX8+LY; spf=pass (domain: nuviainc.com, ip: 209.85.221.43, mailfrom: leif@nuviainc.com) Received: by mail-wr1-f43.google.com with SMTP id e16so1020605wrm.2 for ; Mon, 28 Sep 2020 04:56:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuviainc-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=nLAEZ0ktycyMRS12F1SLCcXLXgSlxEDgr90/B3IM3Tc=; b=rvPX8+LYKuxUaHIJvfGzqAE3bftYRHcobXaZu4D6cufHeg1cavlDDb9i/OZhmMJ49N edfkZDlUT3l084nk3jWwrBkL8M9K4VnPzMFvffVP0/bIliGqkx7mZhQ9ij/M7dqT7fC9 K07sxALM56Znwx35VneNtCLT0qk8yIqMHyQEVkjLrjqBqKHKwkitDgNcVgnEN488/CW6 IhU0d3TmatB6S3clWj70ppMEjG0gFEt3ud34QUvcE2QB7Pt9xSwLNo5EIzEHsbxzbcIB kJGFlb0BbpC4kGtTAuiyDEoN5YhQSs/sUv+xWJiUPs7rqyH0iU0majoozoo84G/O2ip8 cpkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=nLAEZ0ktycyMRS12F1SLCcXLXgSlxEDgr90/B3IM3Tc=; b=GF54OVnSMbi29/+WkFj0SPxphe6dYplcko18piM9vmK9Iuq+yMCPIkgZg4eH8Iw9pN awfxpdmoxeHlQjs64YxhzX50uwWAzSrwqbMHDuM855/itOg62J+PGj7S0t25aDUWIr6e o2HcoKCI0tC0aVj69Zjw5NIZphkUBXQkZfRFP1QJ5h3LMiNWj0NahTJMSaVK3USNKMfT gh9RvSJ5/c82H6TkWswgD33r+LFYagk0eSAaw/jvTZHZbFT6+Uj+qvhfzHZqREq+9WuE ItIDYxvIKNprXEex/ps2G32AW/Z1MFUujcwvJR9XSZWntP2V/oDUv9ScM1PlhYk2T6vq 1INA== X-Gm-Message-State: AOAM532FxyPBxPWwoyArs51Uij8H+UyWgkMqmPgwRyKmi0VVe5/ty27F VwM5jsOCom9hKDskImuWHg4DMuk4k+JN9EqOBO8HVE0t+YP6pp2/HfBBtSg8xyqxZjWj8b3CQGs w9G7DtBtysBSB4/XvPpWlSzNYlpRdin4Ft9JsyimA4gCBc/sZmYBt3XLC0t+PDElTaN8G X-Google-Smtp-Source: ABdhPJyeuyM8yDWMJ92NaEMitRWfC9xqEpW/kB3QWBvFJcrZWjNRxwjr5gWQcGFO5KzfkVef2ZakUA== X-Received: by 2002:a5d:69c2:: with SMTP id s2mr1273917wrw.389.1601294211982; Mon, 28 Sep 2020 04:56:51 -0700 (PDT) Return-Path: Received: from vanye ([2001:470:1f09:12f0:b26e:bfff:fea9:f1b8]) by smtp.gmail.com with ESMTPSA id 91sm1239811wrq.9.2020.09.28.04.56.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 28 Sep 2020 04:56:51 -0700 (PDT) Date: Mon, 28 Sep 2020 12:56:44 +0100 From: "Leif Lindholm" To: devel@edk2.groups.io, gaoliming@byosoft.com.cn Cc: jiewen.yao@intel.com, "'Guptha, Soumya K'" , announce@edk2.groups.io, lersek@redhat.com, "'Kinney, Michael D'" , 'Andrew Fish' Subject: =?UTF-8?B?UmU6IOWbnuWkjTogW2VkazItZGV2ZWxdIFRpYW5vY29yZSBjb21tdW5pdHkgcGFnZSBvbiB3aG8gd2UgYXJlIC0gcGxlYXNlIHJldmlldw==?= Message-ID: <20200928115644.GZ5623@vanye> References: <16383D375E5994D7.27235@groups.io> <005f01d69476$81768bd0$8463a370$@byosoft.com.cn> MIME-Version: 1.0 In-Reply-To: <005f01d69476$81768bd0$8463a370$@byosoft.com.cn> User-Agent: Mutt/1.10.1 (2018-07-13) Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Hi Liming, On Sun, Sep 27, 2020 at 10:32:55 +0800, gaoliming wrote: > 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 mostly > know edk2 one or more packages (modules). So, they can take Maintainer role. > 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. > > Soumya: > > Here are my 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 fully review one patch set in one week, es for the feature or > the complex change. My take on this is as follows (speaking as someone who has failed this rule many times): This document is a guideline. In some cases we are not yet in a position to be more timely about this. That's where we need more reviewers to help out. Whether they are official designated reviewers or not. If some parts of the codebase always take long time to get review feedback for, that is a sign of a problem that needs to be addressed. I agree that for a very invasive change, we may not be able to give a detailed reply early on. But in those cases, we should convey that feedback *very* early on. > Role of a Contributor/developer. We need to highlight the role & > responsibility for the incompatible change. If the contributor proposes the > incompatible change, he needs to coordinate with the impacted platform > maintainer and make the 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. This is a good point. The details may need more discussion. > Last, this page also needs to include release maintainer Definition and > Role. The release 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 also send the announcement of soft feature freeze, hard feature > freeze and the stable tag completement to edk2 community. This is also a good point. Best Regards, Leif > Thanks > > Liming > > 发件人: bounce+27952+65655+4905953+8761045@groups.io > 代表 Yao, Jiewen > 发送时间: 2020年9月26日 13:33 > 收件人: devel@edk2.groups.io; Yao, Jiewen ; Guptha, > Soumya K ; announce@edk2.groups.io > 主题: Re: [edk2-devel] Tianocore community page on who we are - please > review > > > > 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/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 > ocess> 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 > > 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 > 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-Pro > cess 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 > ocess> 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 > > 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 - 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 > > > > > > > > > >