From: "Laszlo Ersek" <lersek@redhat.com>
To: Sean Brogan <sean.brogan@microsoft.com>,
"rfc@edk2.groups.io" <rfc@edk2.groups.io>,
"Ni, Ray" <ray.ni@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Gao, Liming" <liming.gao@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-rfc] [edk2-devel] [RFC] EDK II Continuous Integration Phase 1
Date: Tue, 3 Sep 2019 19:45:32 +0200 [thread overview]
Message-ID: <f259c2f8-636a-1948-d2de-59a32c787d4b@redhat.com> (raw)
In-Reply-To: <DM5PR21MB0842ED9F69EA51BBC71CAA46E1B90@DM5PR21MB0842.namprd21.prod.outlook.com>
On 09/03/19 19:09, Sean Brogan wrote:
> Laszlo/Mike,
>
> The idea that the maintainer must create the PR is fighting the
> optimized github PR flow. Github and PRs process is optimized for
> letting everyone contribute from "their" fork while still protecting
> and putting process in place for the "upstream".
>
> Why not use github to assign maintainers to each package or filepath
> and then let contributors submit their own PR to edk2 after the
> mailing list has approved. Then the PR has a policy that someone that
> is the maintainer of all files changed must approve before the PR can
> be completed (or you could even set it so that maintainer must
> complete PR). This would have the benefit of less monotonous work
> for the maintainers and on rejected PRs the contributor could easily
> update their branch and resubmit their PR.
I'll let Mike respond.
Thanks
Laszlo
next prev parent reply other threads:[~2019-09-03 17:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 20:22 [RFC] EDK II Continuous Integration Phase 1 Michael D Kinney
2019-08-29 20:39 ` [edk2-devel] " Michael Zimmermann
2019-08-29 21:08 ` Michael D Kinney
2019-08-30 2:21 ` Sean
2019-08-30 13:11 ` [edk2-devel] " Laszlo Ersek
2019-09-13 21:00 ` Sean
2019-09-16 11:06 ` Laszlo Ersek
2019-09-19 21:45 ` Michael D Kinney
2019-09-19 21:55 ` Michael D Kinney
2019-09-20 21:29 ` Sean
2019-09-23 17:44 ` Michael D Kinney
2019-09-24 14:05 ` Liming Gao
2019-08-30 8:43 ` Liming Gao
2019-08-30 12:58 ` [edk2-devel] " Laszlo Ersek
2019-09-03 3:39 ` [edk2-rfc] " Ni, Ray
2019-09-03 13:19 ` Laszlo Ersek
2019-09-03 16:41 ` Ni, Ray
2019-09-03 16:55 ` Laszlo Ersek
2019-09-03 17:09 ` Sean
2019-09-03 17:45 ` Laszlo Ersek [this message]
2019-09-19 21:13 ` Michael D Kinney
2019-09-04 23:56 ` rebecca
2019-09-19 17:53 ` Michael D Kinney
2019-08-31 20:31 ` [edk2-rfc] " rebecca
2019-09-17 3:46 ` [edk2-devel] " rebecca
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=f259c2f8-636a-1948-d2de-59a32c787d4b@redhat.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