From: "Jörg Rödel" <joro@8bytes.org>
To: svsm-devel@coconut-svsm.dev, coconut-svsm@lists.linux.dev,
linux-coco@lists.linux.dev
Subject: SVSM Development Call May 7th, 2025
Date: Tue, 6 May 2025 17:40:42 +0200 [thread overview]
Message-ID: <aBotemx_JthzO9FG@8bytes.org> (raw)
Hi,
Here is the usual call for agenda items for the this weeks SVSM
development call. Please send me any agenda items you have in mind or
raise them in the meeting.
Currently I have one item on the list:
* Announcements
We will use the LF Zoom instance for the first time this week, not GMeet
as before. Details of the meeting can be found in our governance
repository at:
https://github.com/coconut-svsm/governance
Especially the link the the new COCONUT-SVSM calendar is important. It
has the meeting appointments and the link to the Zoom meeting room:
https://zoom-lfx.platform.linuxfoundation.org/meetings/coconut-svsm?view=week
The meeting will be recorded and the recording eventually published.
See you all there.
Regards,
Jörg
next reply other threads:[~2025-05-06 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 15:40 Jörg Rödel [this message]
2025-05-08 8:33 ` [svsm-devel] SVSM Development Call May 7th, 2025 Jörg Rödel
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-all 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=aBotemx_JthzO9FG@8bytes.org \
--to=joro@8bytes.org \
--cc=coconut-svsm@lists.linux.dev \
--cc=linux-coco@lists.linux.dev \
--cc=svsm-devel@coconut-svsm.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.