public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Felix Polyudov <Felixp@ami.com>
To: 'Laszlo Ersek' <lersek@redhat.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Jeremiah Cox <jerecox@microsoft.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-announce] Community Meeting Minutes
Date: Fri, 15 Feb 2019 19:54:46 +0000	[thread overview]
Message-ID: <9333E191E0D52B4999CE63A99BA663A00302C62F87@atlms1.us.megatrends.com> (raw)
In-Reply-To: <ffb30238-12b2-f4c0-b1ca-a5036b1b7bf8@redhat.com>

> -----Original Message-----
> From: Laszlo Ersek
> Sent: Friday, February 15, 2019 9:23 AM
>
> Just a short comment below.
>
> (Not changing my stance in any way that I've presented thus far; the
> comment is only meant in addition to / as a clarification for that.)
>
> On 02/15/19 09:43, Ard Biesheuvel wrote:
>
> > I would like to see more engagement from these contributors in the
> > actual project before we start rebuilding our infrastructure around
> > them.
>
> Agreed. In my opinion, some public "testimonials" would be nice, such as
>
>   Yes, the mailing list based workflow is the one thing that prevents us
>   from sharing patches, listening to and addressing reviews, posting
>   updated patches, and commenting on others' patches.

For AMI and for me personally mailing list based workflow is one of the factors that limits our level of engagement.
I've done a few patch submissions, but I have yet to figure out how to make applying embedded patches work in my Windwos & Outlook configuration.

Please consider the environment before printing this email.

The information contained in this message may be confidential and proprietary to American Megatrends, Inc.  This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited.  Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.


  reply	other threads:[~2019-02-15 19:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 19:26 [edk2-announce] Community Meeting Minutes stephano
2019-01-13  3:59 ` Rebecca Cran
2019-01-14  9:28   ` Laszlo Ersek
2019-01-14 17:06   ` stephano
2019-02-07 17:52 ` Jeremiah Cox
2019-02-07 18:30   ` stephano
2019-02-08  6:41     ` Rebecca Cran
2019-02-08  9:01       ` Laszlo Ersek
2019-02-08 17:33         ` Rebecca Cran
2019-02-08 17:52           ` Andrew Fish
2019-02-22 11:52             ` Rebecca Cran
2019-02-08 20:33           ` Laszlo Ersek
2019-02-08 13:58   ` Ard Biesheuvel
2019-02-14 19:07     ` Jeremiah Cox
2019-02-14 20:27       ` Rebecca Cran
2019-02-14 22:13         ` Kinney, Michael D
2019-02-15  2:56           ` Rebecca Cran
2019-02-15 14:30             ` Laszlo Ersek
2019-02-15 17:55             ` stephano
2019-02-15  8:43       ` Ard Biesheuvel
2019-02-15 14:23         ` Laszlo Ersek
2019-02-15 19:54           ` Felix Polyudov [this message]
2019-02-15 22:53             ` Laszlo Ersek
  -- strict thread matches above, loose matches on Subject: below --
2019-02-20  6:23 stephano
2019-02-20  6:45 ` stephano
2019-02-20  7:49 ` Rebecca Cran

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=9333E191E0D52B4999CE63A99BA663A00302C62F87@atlms1.us.megatrends.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