public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: Sean Brogan <spbrogan@outlook.com>
Cc: devel@edk2.groups.io, "Marvin Häuser" <mhaeuser@posteo.de>,
	"Isaac Oram" <isaac.w.oram@intel.com>,
	"Théo Jehl" <theojehl76@gmail.com>
Subject: Re: [edk2-devel] edk2-platforms, continuous integration, testing, and you
Date: Thu, 5 Jan 2023 23:32:48 +0000	[thread overview]
Message-ID: <CAKbZUD2MQwZNzg2QUH83E=1+sHBjoCYHAc+UDByB8Jxk0Bc9ZA@mail.gmail.com> (raw)
In-Reply-To: <BY3PR19MB4900B0BA3ED3F68B085BB40BC8FA9@BY3PR19MB4900.namprd19.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]

On Thu, Jan 5, 2023 at 1:52 AM Sean Brogan <spbrogan@outlook.com> wrote:

> Pedro,
>
> Thanks.  Happy to get some feedback.  I hope others also provide
> feedback.  :)
>
>
> Regarding the Edk2 tools & CI meeting:  If we scheduled the Jan 16th
> meeting for Jan 17th at 8am Pacific (should be 5 pm your time) would that
> work?  In the meeting we have discussed that we need to rotate the time of
> the meetings to accommodate more world wide attendance and given the
> standard time would fall on a US holiday it seems like a good week to do
> it.  Could you make it that day?
>
I could make it work that day I believe, but only 2-3 hours later. Does
that work for you folks?

> At a minimum we could talk about your packages:
>
> Like should ext4 really depend on redfishpkg?  More likely the library
> should be promoted to a more "core" package.
>
Should? No. I just haven't had the patience to send a patch moving the
BaseUcs2Utf8Lib to somewhere more central like MdeModulePkg.

> Could your qemu open board pkg be built using stuart and setup to run
> tests?  More details about the goals and plans for the qemu open board
> pkg.
>
Great questions. Probably? It should just work and actually be able to run
tests.
Re: goals and plans, I do have a few ideas but they're all very unclear. We
haven't had much community engagement wrt QemuOBP, it's definitely
something that could be explored (CC Isaac and Theo, who might want to show
up or chime in).

Thanks,
Pedro

[-- Attachment #2: Type: text/html, Size: 2345 bytes --]

  reply	other threads:[~2023-01-05 23:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 21:38 edk2-platforms, continuous integration, testing, and you Sean
2023-01-04 23:57 ` [edk2-devel] " Pedro Falcato
2023-01-05  1:52   ` Sean
2023-01-05 23:32     ` Pedro Falcato [this message]
2023-01-05 23:48       ` Théo Jehl
2023-01-10  0:24         ` Isaac Oram
2023-01-13 22:32         ` Sean
2023-01-14  2:54           ` Pedro Falcato
2023-01-16 21:06             ` 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='CAKbZUD2MQwZNzg2QUH83E=1+sHBjoCYHAc+UDByB8Jxk0Bc9ZA@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