From: "Demeter, Miki" <miki.demeter@intel.com>
To: "announce@edk2.groups.io" <announce@edk2.groups.io>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: TianoCore Community Meeting APAC/NAMO
Date: Fri, 19 Aug 2022 19:07:17 +0000 [thread overview]
Message-ID: <DS0PR11MB644561DEB63CA4C5463581468D6C9@DS0PR11MB6445.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
# TianoCore Community Meeting
**Highlights:**
* Moving AM Community Meeting to 8:00AM PST to be more Time Zone friendly
# Meeting Minutes:
1) **Event Updates (_5 minutes]**
** Linux Plumbers – Dublin Sep 12–14, 2022 **
** OSFC – Mölndal, Sweden – Sept. 19-21, 2022 **
2) [**Stable Tag Updates (_5 minutes_)**
- 2022- Release
** Stable Tag 202208Freeze - Current **
** Stable Tag 202208Release – August 26, 2022 **
3) **Stewards Download (_20 minutes_)**
* Static Analysis tools are under evaluation
* ! additional patch approved for inclusion in hard freeze
-**Coverity Status**
- No update
-** EDK2 Bugzilla Status **
- 179 Unconfirmed bugs
- 501 Confirmed
- 163 Unassigned
- 39 In Progress
- Last ~30 days 20 new issues
Need to determine what to do about BZ reporters not responding to requests for info
4) **Opens (_30 minutes_)**
- No Opens
**AR: **
AR: Miki to add new reminders to calendar hits -COMPLETED Reminders set
** Nate presenting on FSP2.4 and min-platform – OCP summit **
GSOC
Next meeting will be Thursday Septmber 15th 7:30PM PST
--
Miki Demeter (she/her/Miki)
Security Researcher / FW Developer
FST
Intel Corporation
Co-Chair, Network of Intel African-Ancestry(NIA) - Oregon
NIA-Oregon<https://intel.sharepoint.com/sites/NIA>
Portland Women in Tech Best Speaker
miki.demeter@intel.com<mailto:miki.demeter@intel.com>
503.712.8030 (office)
971.248.0123 (cell)
[-- Attachment #2: Type: text/html, Size: 17013 bytes --]
reply other threads:[~2022-08-19 19:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=DS0PR11MB644561DEB63CA4C5463581468D6C9@DS0PR11MB6445.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