From: "Oliver Smith-Denny" <osde@linux.microsoft.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>,
"Bi, Dandan" <dandan.bi@intel.com>,
"Gao, Zhichao" <zhichao.gao@intel.com>,
"Ni, Ray" <ray.ni@intel.com>, "Wu, Jiaxin" <jiaxin.wu@intel.com>,
"Zeng, Star" <star.zeng@intel.com>,
"Guo, Gua" <gua.guo@intel.com>,
"Prakashan,
Krishnadas Veliyathuparambil"
<krishnadas.veliyathuparambil.prakashan@intel.com>,
"K N, Karthik" <karthik.k.n@intel.com>,
"RichardHo [何明忠]" <RichardHo@ami.com>,
"Rebecca Cran" <rebecca@bsdio.com>,
"Attar, AbdulLateef (Abdul Lateef)" <AbdulLateef.Attar@amd.com>,
"Nickle Wang" <nicklew@nvidia.com>
Subject: Re: [edk2-devel] Call or topics for April TianoCore Community Meeting
Date: Thu, 4 Apr 2024 10:23:47 -0700 [thread overview]
Message-ID: <949ab562-858c-4328-8cfb-931cfdf88577@linux.microsoft.com> (raw)
In-Reply-To: <CO1PR11MB492904E0B32EEA34248C2E07D23D2@CO1PR11MB4929.namprd11.prod.outlook.com>
On 4/3/2024 4:28 PM, Kinney, Michael D wrote:
> MdeModulePkg has many different reviewers for different subsets.
>
> We should also consider seeing if any of those reviewers that
> are responsible for different subsets of MdeModulePkg would be
> willing to be a backup maintainer for the MdeModulePkg.
>
> Zhiguang Liu <zhiguang.liu@intel.com> [LiuZhiguang001]
> Dandan Bi <dandan.bi@intel.com> [dandanbi]
> Zhichao Gao <zhichao.gao@intel.com> [ZhichaoGao]
> Ray Ni <ray.ni@intel.com> [niruiyu]
> Jiaxin Wu <jiaxin.wu@intel.com> [jiaxinwu]
> Star Zeng <star.zeng@intel.com> [lzeng14]
> Gua Guo <gua.guo@intel.com> [gguo11837463]
> Prakashan Krishnadas Veliyathuparambil <krishnadas.veliyathuparambil.prakashan@intel.com> [kprakas2]
> K N Karthik <karthik.k.n@intel.com> [karthikkabbigere1]
> Richard Ho <richardho@ami.com> [richardho]
> Rebecca Cran <rebecca@bsdio.com> [bcran]
> Abdul Lateef Attar <AbdulLateef.Attar@amd.com> [abdattar]
> Nickle Wang <nicklew@nvidia.com> [nicklela]
>
That seems reasonable to reach out to these folks as well.
We can take it as a data point on how long it takes one
of the existing submaintainers to respond to your email
:).
Thanks,
Oliver
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#117443): https://edk2.groups.io/g/devel/message/117443
Mute This Topic: https://groups.io/mt/105299780/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-04-04 17:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 7:07 [edk2-devel] Topics for March TianoCore Community Meeting Michael D Kinney
2024-03-07 4:42 ` Michael D Kinney
2024-04-03 0:12 ` [edk2-devel] Call or topics for April " Michael D Kinney
2024-04-03 17:25 ` Oliver Smith-Denny
2024-04-03 20:38 ` Michael D Kinney
2024-04-03 20:50 ` Michael Kubacki
2024-04-03 22:02 ` Oliver Smith-Denny
2024-04-03 23:28 ` Michael D Kinney
2024-04-04 17:23 ` Oliver Smith-Denny [this message]
2024-04-04 15:21 ` Pedro Falcato
2024-04-03 20:31 ` Michael D Kinney
2024-05-01 16:45 ` [edk2-devel] Call or topics for May " Michael D Kinney
2024-05-02 14:03 ` Rebecca Cran
2024-05-02 17:04 ` Oliver Smith-Denny
2024-05-02 17:29 ` Michael D Kinney
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=949ab562-858c-4328-8cfb-931cfdf88577@linux.microsoft.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