public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io, osde@linux.microsoft.com
Cc: michael.d.kinney@intel.com, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [edk2-devel] Call or topics for April TianoCore Community Meeting
Date: Thu, 4 Apr 2024 16:21:33 +0100	[thread overview]
Message-ID: <CAKbZUD0dScKNA4_ZC+dB8H2q6ZcmmjkgF+UumAc=UCOD8ii6rg@mail.gmail.com> (raw)
In-Reply-To: <09a5f512-53c9-4c5e-8497-3df1f0f40399@linux.microsoft.com>

On Wed, Apr 3, 2024 at 11:02 PM Oliver Smith-Denny
<osde@linux.microsoft.com> wrote:
>
> On 4/3/2024 1:38 PM, Michael D Kinney wrote:
> > Hi Oliver,
> >
> > I missed this response.  Did not show up in thread for some reason.
>
> No worries.
>
> >
> > But we can continue these topics on email.
> >
> > The TianoCore roles and responsibilities are documented here:
> >
> >       https://github.com/tianocore/tianocore.github.io/wiki/TianoCore-Who-we-are
> >
> > If there are maintainers are not following their responsibilities, then
> > please let us know and we can work together to find additional maintainers.
>
> Thanks, as I've mentioned in several of my last patches to MdeModulePkg,
> I think we need an additional top level maintainer there who is
> currently active. Liming has obviously been a huge part of edk2, but has
> many roles and has been quiet on MdeModulePkg patches for over a month.
> His input is greatly valued, but it seems he could use some help
> maintaining the package so we can keep up developer flow, I had multiple
> patches that contained items such as fixes for UEFI spec violations and
> boot breaks that were sitting with multiple reviews that were not
> getting the maintainer review and merging in.

We had a long discussion about this in this thread:
https://openfw.io/edk2-devel/CAKbZUD2TVXojT84gb6V89O7eFOAswyPG25i19YCnNfPFt0qeag@mail.gmail.com/

IIRC all it did was get Laszlo to do the lord's work for a few months,
but now he's gone :)

FWIW: I've been around for ~3 years, and maintainer response times
(for these "main" packages) have been *long* for those 3 years. As far
as I've heard, they've been awful for a lot longer, but I can't vouch
for that.
I'd suppose they'll continue to be high as long as upstream EDK2 plays
second or third fiddle to other firmware branches.

Personally, I have multiple patches out there with significant QoL
improvements that were simply ghosted, and I CBA to keep resending
them (nor do I care).

>
> I think it would be very valuable to have a second MdeModulePkg top
> level maintainer in any case, this covers areas such as DxeCore that
> are some of the most central and complex parts of the code base and
> bugs there need immediate resolution.
>
> I don't want to put him on the spot, but I would be tempted to
> nominate Ard, if he wants the added responsibility, as he is very
> knowledgeable in UEFI and one of the few people who actively reviews
> patches closely and timely. If he does not want the additional
> maintenance burden, then I would ask the stewards to help find
> a community member to take on this role with Liming.
>
> >
> > There is not much progress on PR process.  We need resources to work on the
> > list of action items documented here:
> >
> >       https://github.com/orgs/tianocore/projects/5
>
> Thanks for this pointer, I know the majority of active community
> members report in many different forums that moving to PRs is
> critical and I am confident that as a community we can make this
> happen.

It'd be nice (over this weird hybrid system of email + PR), but I'm
really not sure if it's critical. Email-based submission *works* (even
with all the Outlook awfulness some people have to go through), which
is why I've been resistant to adopting the same confusing hybrid
system of email patches + PR + the push tag (and then the CI flakes,
or uncrustify thinks my code is slightly misformatted even though I
used a slightly older uncrustify) to edk2-platforms.

-- 
Pedro


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#117440): https://edk2.groups.io/g/devel/message/117440
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]
-=-=-=-=-=-=-=-=-=-=-=-



  parent reply	other threads:[~2024-04-04 15:21 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
2024-04-04 15:21           ` Pedro Falcato [this message]
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='CAKbZUD0dScKNA4_ZC+dB8H2q6ZcmmjkgF+UumAc=UCOD8ii6rg@mail.gmail.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