public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
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 Meetig 20230406 EMEA APAC NAMO
Date: Fri, 7 Apr 2023 02:41:06 +0000	[thread overview]
Message-ID: <DS0PR11MB64455C37AFB90BE09A6D27BE8D919@DS0PR11MB6445.namprd11.prod.outlook.com> (raw)

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

# TianoCore Community Meeting

**Highlights:**

  *   GHSA Discussion/Update – GHSR and GHSA continues through the next Stable Tag release in May
  *   Critical CI event 20230331 worked through the issues back to normal on Sunday
  *   TianoCore Contributors Agreement for Docs

# Meeting Minutes:

 **Opens (_30 minutes_)**

  *   Miki - GHSA Discussion/Update – GHSR and GHSA will be trialed through the next Stable Tag release in May
  *   Rebecca Release Notes updates – check with Liming
  *   TianoCore Contributors Agreement for Docs
  *   PR Flow for Github to move away from email list management – still issues with information loss to be worked through



**Event Updates (_5 minutes]**

  *

**Stable Tag Updates (_5 minutes_)**

  *   edk2-stable202211 Current Stable Release
  *   Soft Freeze 20230508
  *   Hard Freeze 20230512
  *   Release 20230526

**Stewards Download (_20 minutes_)**

  *   Critical CI event 20230331 worked through the issues back to normal on Sunday
  *   Google Mock Support dependency on subhook and Sub module Firmware Device Tree support code review underway
  *   Libc Code review wrapper code and would like to see consolidated code duplication taken care of
     *   Updating of libc wrapper needs folx to work on it needs to be updated
  *   OpenSSL 3.0 some heavy lifting to enable openssl 3.0 size is prohibitive working on reducing size
     *   Working with OpenSSL community to upstream changes
     *   Fork of OpenSSL 3.0 for EDK2 to manage changes while working with Upstream Maintainers

Next Meeting: 20230504 [ May the 4th be with you ]

Agenda:

  *   HBFA/kAFL – Lynn Tipton, Mathieu Tarral
  *   Python UEFI – N. Jayaprash

--
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: 21327 bytes --]

                 reply	other threads:[~2023-04-07  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=DS0PR11MB64455C37AFB90BE09A6D27BE8D919@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