From: "Wu, Hao A" <hao.a.wu@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "lersek@redhat.com" <lersek@redhat.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
Andrew Fish <afish@apple.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Gao, Liming" <liming.gao@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Zeng, Star" <star.zeng@intel.com>
Subject: [RFC] Fine-grained review ownership for MdeModulePkg
Date: Mon, 10 Jun 2019 08:06:23 +0000 [thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A093C8E49BD@SHSMSX104.ccr.corp.intel.com> (raw)
Hello all,
Driven by the issue raised and discussions with thread:
https://edk2.groups.io/g/devel/topic/31907735#42076
This RFC proposal is raised to work out a fine-grained review ownership
for MdeModulePkg.
The goal is to update the 'MdeModulePkg' section in file Maintainers.txt
to resemble the format like the 'OvmfPkg' section. Several reviewers will
be listed to take the ownership to review patches for a specific feature
in the package.
In order to get the list of reviewers, a 2-step process will be adopted:
1. Work out a list that contains major features in MdeModulePkg.
2. Call for owners for every item in the list.
For 1, a coarse feature list is:
Acpi
Bds
Capsule
Compress
Console
Core (PeiCore, DxeCore, PiSmmCore, etc. Mainly content in MdeModulePkg/Core/ folder)
Device (peripheral & storage)
Disk
EBC
HII
MemoryManagement (include memory test, memory allocation, memory profile, etc.)
PCD
PCI bus
Reset
S3 (including LockBox)
SMBIOS
SMM
Status Code
UI
Variable
Misc (all the components that do not fit in the above items)
Once we think the granularity of the above list is fine and there is no
significant feature missing, I will update such list to include the
modules that belong to a specific feature. So adjustments can be done to
work out the final feature list.
The proposal here is far from mature, so any feedback/suggestion will be
appreciated.
Best Regards,
Hao Wu
next reply other threads:[~2019-06-10 8:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 8:06 Wu, Hao A [this message]
2019-06-11 9:51 ` [RFC] Fine-grained review ownership for MdeModulePkg Leif Lindholm
2019-06-11 15:41 ` Laszlo Ersek
2019-06-19 5:09 ` Wu, Hao A
2019-06-19 9:35 ` Leif Lindholm
2019-06-20 15:43 ` [edk2-devel] " Laszlo Ersek
2019-06-24 1:16 ` Wu, Hao A
2019-06-24 20:29 ` Laszlo Ersek
2019-06-24 22:58 ` Yao, Jiewen
2019-07-16 13:53 ` Leif Lindholm
2019-07-17 1:47 ` Wu, Hao A
2019-06-20 22:23 ` rebecca
2019-06-21 0:11 ` Wu, Hao A
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B80AF82E9BFB8E4FBD8C89DA810C6A093C8E49BD@SHSMSX104.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox