From: "Demeter, Miki" <miki.demeter@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"announce@edk2.groups.io" <announce@edk2.groups.io>
Subject: TianoCore Community Meeting 20230713 NAMO/EMEA/APAC
Date: Fri, 14 Jul 2023 02:41:33 +0000 [thread overview]
Message-ID: <DS0PR11MB644576E723514D92A5131B778D37A@DS0PR11MB6445.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
# Agenda:
**Presentation Topics:**
* No topics
**Opens:**
* Miki is retiring from Intel and Next Month will be her last Community meeting
**Stewards Update**
* GHSA still have some rough edges in getting correct folx added to reviewers
* Maintainers.txt needs to be updated
* Miki has been reaching out to gauge continued interest
* ~50% responded to request to be kept as Reviewer/Maintainer
* OpenSSL 3.0 feedback
* Some patches have been accepted and merged upstream
* Most significant size change fix has not been accepted
* MBed-TLS is missing a couple of features necessary for TianoCore
** OpenSSL 1.1.1 EOL **
* OpenSSL 1.1.1 EOL 2023-09-11
* Current staging branches to develop the OpenSSL 1.1.1 replacement:
* https://github.com/tianocore/edk2-staging/tree/OpenSSL11_EOL
* https://github.com/tianocore/edk2-staging/blob/OpenSSL30/CryptoPkg/Readme-OpenSSL3.0.md
* Staging branch MBedTLS PoC
* https://github.com/tianocore/edk2-staging/blob/OpenSSL11_EOL/CryptoPkg/ReadmeMbedtls.md
**Stable Tag Updates (_5 minutes_)**
* edk2-stable202305 Current Stable Release
* Soft Freeze 2023-08-07
* Hard Freeze 2023-08-11
* Release 2023-08-25
--
Miki Demeter (she/her/Miki)
Security Researcher / FW Developer
Tianocore Community Manager
FST
Intel Corporation
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: 37284 bytes --]
reply other threads:[~2023-07-14 2:41 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=DS0PR11MB644576E723514D92A5131B778D37A@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