public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <quic_llindhol@quicinc.com>
To: Rebecca Cran <rebecca@bsdio.com>, <devel@edk2.groups.io>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Moving edk2-platforms reviews to GitHub Pull Requests
Date: Mon, 1 Jul 2024 21:13:39 +0100	[thread overview]
Message-ID: <28301d08-9e6b-4a2d-ba78-8e714345bd30@quicinc.com> (raw)
In-Reply-To: <71e26999-15bb-4b74-b884-e20480ba92f6@bsdio.com>

(Dropping direct cc:s)

On 2024-07-01 20:16, Rebecca Cran wrote:
> Now that edk2 has been using PRs for a few weeks, I'd like to propose 
> enabling the same workflow for edk2-platfoms.
> 
> As maintainers or reviewers of platforms in the edk2-platforms repo, I'd 
> like to get any feedback on moving from email-based reviews to GitHub 
> Pull Requests and any concerns or issues people might have with it.

My only concern is wrt reviewer assignment.

There are a few ways we can consider that - for example:
- leave contribution workflow up to each maintainer (for now)
- switch fully and expect maintainers to dutifully trawl the PR queue
- Move to CODEOWNERS for edk2-platforms (which has less complex wildcard
   use than edk2)

Best Regards,

Leif



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119749): https://edk2.groups.io/g/devel/message/119749
Mute This Topic: https://groups.io/mt/106986207/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  parent reply	other threads:[~2024-07-01 20:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 19:16 [edk2-devel] Moving edk2-platforms reviews to GitHub Pull Requests Rebecca Cran
2024-07-01 19:19 ` Paul via groups.io
2024-07-02  1:14   ` Chang, Abner via groups.io
2024-07-01 20:13 ` Leif Lindholm [this message]
2024-07-02 10:20 ` Marvin Häuser
2024-07-03 14:19 ` Rebecca Cran
2024-07-04  3:21   ` Chang, Abner via groups.io

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=28301d08-9e6b-4a2d-ba78-8e714345bd30@quicinc.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