From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: Oliver Smith-Denny <osde@linux.microsoft.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Call or topics for April TianoCore Community Meeting
Date: Wed, 3 Apr 2024 20:38:32 +0000 [thread overview]
Message-ID: <CO1PR11MB4929DF84D38FD85E085F2D8FD23D2@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <a24f89b3-d6d8-404c-8ff1-b782044e2087@linux.microsoft.com>
Hi Oliver,
I missed this response. Did not show up in thread for some reason.
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.
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
Mike
> -----Original Message-----
> From: Oliver Smith-Denny <osde@linux.microsoft.com>
> Sent: Wednesday, April 3, 2024 10:25 AM
> To: devel@edk2.groups.io; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Subject: Re: [edk2-devel] Call or topics for April TianoCore Community
> Meeting
>
> Hi Mike,
>
> My two topics would be PRs and lack of maintainer response, the proper
> process there, etc.
>
> Thanks,
> Oliver
>
> On 4/2/2024 5:12 PM, Michael D Kinney wrote:
> > Please let me know if you have any topics for the TianoCore
> Community
> > Meeting this month.
> >
> > Thanks,
> >
> > Mike
> >
> >
> >
> >
> >
> >
> >
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#117389): https://edk2.groups.io/g/devel/message/117389
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]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-04-03 20:38 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 [this message]
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
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=CO1PR11MB4929DF84D38FD85E085F2D8FD23D2@CO1PR11MB4929.namprd11.prod.outlook.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