public inbox for
 help / color / mirror / Atom feed
From: "Group Notification" <>
Subject: [edk2-devel] Event: Tools, CI, Code base construction meeting series - Monday, April 1, 2024 #cal-reminder
Date: Mon, 01 Apr 2024 15:30:01 -0700	[thread overview]
Message-ID: <> (raw)

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

*Reminder: Tools, CI, Code base construction meeting series*

Monday, April 1, 2024
4:30pm to 5:30pm
(UTC-07:00) America/Los Angeles


View Event ( )


TianoCore community,

Microsoft and Intel will be hosting a series of open meetings to discuss build, CI, tools, and other related topics. If you are interested, have ideas/opinions please join us. These meetings will be Monday 4:30pm Pacific Time on Microsoft Teams.

MS Teams Link in following discussion: *

Anyone is welcome to join.

* tianocore/edk2: EDK II (
* tianocore/edk2-basetools: EDK II BaseTools Python tools as a PIP module (
* tianocore/edk2-pytool-extensions: Extensions to the edk2 build system allowing for a more robust and plugin based build system and tool execution environment (
* tianocore/edk2-pytool-library: Python library package that supports UEFI development (

MS Teams Browser Clients *

-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group.
View/Reply Online (#117297):
Mute This Topic:
Mute #cal-reminder:
Group Owner:
Unsubscribe: []

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

             reply	other threads:[~2024-04-01 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 22:30 Group Notification [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-31 23:30 [edk2-devel] Event: Tools, CI, Code base construction meeting series - Monday, April 1, 2024 #cal-reminder Group Notification

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \

* 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