From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"pedro.falcato@gmail.com" <pedro.falcato@gmail.com>
Cc: Andrew Fish <afish@apple.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
"Warkentin, Andrei" <andrei.warkentin@intel.com>,
"West, Catharine" <catharine.west@intel.com>,
"Bi, Dandan" <dandan.bi@intel.com>,
"Daniel Schaefer" <git@danielschaefer.me>,
David Woodhouse <dwmw2@infradead.org>,
"De, Debkumar" <debkumar.de@intel.com>,
"Dong, Eric" <eric.dong@intel.com>,
"Jiang, Guomin" <guomin.jiang@intel.com>,
"Wu, Hao A" <hao.a.wu@intel.com>,
James Bottomley <jejb@linux.ibm.com>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
Julien Grall <julien@xen.org>, Peter Grehan <grehan@freebsd.org>,
"Zhang, Qi1" <qi1.zhang@intel.com>,
"Ng, Ray Han Lim" <ray.han.lim.ng@intel.com>,
"Stefan Berger" <stefanb@linux.ibm.com>,
"Hou, Wenxing" <wenxing.hou@intel.com>,
"Lu, Xiaoyu1" <xiaoyu1.lu@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [Patch 1/1] Maintainers.txt: Update based on active community members
Date: Mon, 30 Oct 2023 22:18:54 +0000 [thread overview]
Message-ID: <CO1PR11MB492947C2597B0375B1E38ECFD2A1A@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <17ced86a-cbdd-e9b6-3011-4185840c0ab9@redhat.com>
Hi Laszlo,
I do not support orphaned categories and that option should be
removed from Maintainer.txt. One of the motivations to get
Maintainers.txt updated is to work on the set of tasks related to
using GitHub PRs for code review. If a component is orphaned,
then nobody would be assigned to a PR in that area and the PR
would be stuck and would eventually be deleted for no activity.
A terrible experience for a submitter.
If there is a feature for which there is no longer any support,
then I recommend we find a way to remove it from the head of the
repository. The feature is still available in the history and
in previous releases when it was supported.
If there is a future need for the feature and there are those that
are willing to support it, it can always be resurrected from the
history.
If it is a critical feature that will break the entire project
if it is removed, then we must find community members that are
willing to own it.
The immediate backup for this scenario is the EDK II Stewards, but
They may not have the background on the specific feature to maintain
it well. For example, I am currently helping with the NetworkPkg
because there are no maintainers and I have been recruiting without
success.
I would like the see the SignedCapulePkg removed. There are a
couple platforms in edk2-platforms that depend on it. There is
another task to review the actively supported platforms in
edk2-platforms. If those platforms are removed, then SignedCapulsePkg
could be safely removed from the head of edk2.
SourceLevelDebugPkg has a similar issues of no maintainers. The
platforms maintained in edk2 repo do not depend on it to do source
level debug. It is more of a physical platform debug capability.
Perhaps this feature should be moved to the edk2-platform. There
was a brief discuss at the UEFI Plugfest to update this debug
feature because the current one depends on very old tools.
Mike
> -----Original Message-----
> From: Laszlo Ersek <lersek@redhat.com>
> Sent: Monday, October 30, 2023 4:29 AM
> To: Kinney, Michael D <michael.d.kinney@intel.com>; Yao, Jiewen
> <jiewen.yao@intel.com>; devel@edk2.groups.io; pedro.falcato@gmail.com
> Cc: Andrew Fish <afish@apple.com>; Leif Lindholm
> <quic_llindhol@quicinc.com>; Warkentin, Andrei
> <andrei.warkentin@intel.com>; West, Catharine
> <catharine.west@intel.com>; Bi, Dandan <dandan.bi@intel.com>; Daniel
> Schaefer <git@danielschaefer.me>; David Woodhouse
> <dwmw2@infradead.org>; De, Debkumar <debkumar.de@intel.com>; Dong,
> Eric <eric.dong@intel.com>; Jiang, Guomin <guomin.jiang@intel.com>;
> Wu, Hao A <hao.a.wu@intel.com>; James Bottomley <jejb@linux.ibm.com>;
> Wang, Jian J <jian.j.wang@intel.com>; Justen, Jordan L
> <jordan.l.justen@intel.com>; Julien Grall <julien@xen.org>; Peter
> Grehan <grehan@freebsd.org>; Zhang, Qi1 <qi1.zhang@intel.com>; Ng, Ray
> Han Lim <ray.han.lim.ng@intel.com>; Stefan Berger
> <stefanb@linux.ibm.com>; Hou, Wenxing <wenxing.hou@intel.com>; Lu,
> Xiaoyu1 <xiaoyu1.lu@intel.com>
> Subject: Re: [edk2-devel] [Patch 1/1] Maintainers.txt: Update based on
> active community members
>
> On 10/30/23 06:31, Kinney, Michael D wrote:
> > There is a very good discussion here on the roles and responsibility
> > and potential suggestions for changes to the Wiki page that document
> > those roles and responsibilities.
> >
> > May I suggest that someone start a new thread that discusses
> > the proposed changes to the Wiki page and leave this thread for the
> > review of the changes to Maintainers.txt?
>
> These are connected topics, but yes, back to "Maintainers.txt" -- do
> you
> feel that "S: Orphan" sections are acceptable in general? They're a
> first (AFAICT) for edk2's "Maintainers.txt"; we've always had the
> mechanism documented (since the creation of "Maintainers.txt", or so),
> but we never seem to have put it to use.
>
> Laszlo
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#110345): https://edk2.groups.io/g/devel/message/110345
Mute This Topic: https://groups.io/mt/102245264/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-10-30 22:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 19:23 [edk2-devel] [Patch 1/1] Maintainers.txt: Update based on active community members Michael D Kinney
2023-10-29 2:16 ` Pedro Falcato
2023-10-29 8:05 ` Yao, Jiewen
2023-10-29 13:48 ` Laszlo Ersek
2023-10-29 14:09 ` Laszlo Ersek
2023-10-29 15:42 ` Yao, Jiewen
2023-10-29 16:01 ` James Bottomley
2023-10-29 16:25 ` Yao, Jiewen
2023-10-29 17:22 ` Michael D Kinney
2023-10-30 2:40 ` Yao, Jiewen
2023-10-30 10:44 ` Laszlo Ersek
2023-10-29 18:29 ` Pedro Falcato
2023-10-29 13:30 ` Laszlo Ersek
2023-10-29 19:01 ` Pedro Falcato
2023-10-30 11:25 ` Laszlo Ersek
2023-10-30 2:54 ` Yao, Jiewen
2023-10-30 5:31 ` Michael D Kinney
2023-10-30 11:29 ` Laszlo Ersek
2023-10-30 22:18 ` Michael D Kinney [this message]
2023-10-31 10:16 ` Laszlo Ersek
2023-10-30 7:38 ` Ng, Ray Han Lim
2023-10-29 21:58 ` Stefan Berger
2023-10-30 4:51 ` Peter Grehan
2023-10-30 7:35 ` Wu, Hao A
2023-10-30 10:51 ` Julien Grall
2023-10-31 4:08 ` Andrei Warkentin
2023-10-31 6:25 ` Jordan Justen
2023-10-31 10:24 ` Laszlo Ersek
2023-11-05 1:22 ` Michael D Kinney
2023-11-05 10:28 ` Laszlo Ersek
2023-10-31 12:27 ` Leif Lindholm
2023-11-04 23:25 ` 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=CO1PR11MB492947C2597B0375B1E38ECFD2A1A@CO1PR11MB4929.namprd11.prod.outlook.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