public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: "Wu, Hao A" <hao.a.wu@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"lersek@redhat.com" <lersek@redhat.com>,
	"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: Re: [RFC] Fine-grained review ownership for MdeModulePkg
Date: Tue, 11 Jun 2019 10:51:50 +0100	[thread overview]
Message-ID: <20190611095150.l7vmqyn3ln4gmvyq@bivouac.eciton.net> (raw)
In-Reply-To: <B80AF82E9BFB8E4FBD8C89DA810C6A093C8E49BD@SHSMSX104.ccr.corp.intel.com>

Hi Wu Hao,

I am working on a proposal (and proof-of-concept) machine readable
Maintainers.txt format, and a GetMaintainer.py script, based on the
format used by QEMU.

One of the key features of that format is the F: tag, which specifes a
filesytem path (with wildcard support).

While this is just an RFC in progress (to be sent out later in week),
if you could take that into account, and figure out which paths
correspond to which areas of responsibility, that would make a test
run of the script much easier.

For my part, I would suggest adding (not just for MdeModulePkg)
F: */ARM/*
F: */AARCH64/*
as maintained by myself and Ard.

Best Regards,

Leif

On Mon, Jun 10, 2019 at 08:06:23AM +0000, Wu, Hao A wrote:
> 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
> 
> 

  reply	other threads:[~2019-06-11  9:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10  8:06 [RFC] Fine-grained review ownership for MdeModulePkg Wu, Hao A
2019-06-11  9:51 ` Leif Lindholm [this message]
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=20190611095150.l7vmqyn3ln4gmvyq@bivouac.eciton.net \
    --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