From: "Carlos López" <clopez@suse.de>
To: "Jörg Rödel" <jroedel@suse.de>
Cc: svsm-devel@coconut-svsm.dev
Subject: Re: [svsm-devel] [RFC] SVSM Development Call
Date: Thu, 7 Sep 2023 14:29:16 +0200 [thread overview]
Message-ID: <873bdb74-a67b-4fe7-a41b-ba3477fccb01@suse.de> (raw)
In-Reply-To: <ZPBqvbMM28sdqewQ@suse.de>
Thursday would be a bit harder for me, but I could make it depending on
the week. The rest of the slots look good.
On 31/8/23 12:26, Jörg Rödel wrote:
> Hi,
>
> I talked to a couple of people recently about our SVSM project and the
> idea came up to schedule a semi-regular call where the community can
> sync on development and direction of the project.
>
> It also fits my wish to be more transparent about our direction and work
> and helps move discussions out of private formats to a more public
> community forum.
>
> So I wanted to propose a couple of time slots and see what people think.
> The idea is to have a meeting every 2 weeks, I will collect and post an
> agenda beforehand and we can always cancel if there is nothing to talk
> about.
>
> Some time slots that would work for me:
>
> CEST ET CT PST
>
> Tuesday 5pm 11am 10am 8am
> 6pm 12pm 11am 9am
>
> Wednesday 5pm 11am 10am 8am
> 6pm 12pm 11am 9am
>
> Thursday 6pm 12pm 11am 9am
>
> Friday 4pm 10am 9am 7am
>
> I have only considered slots that work well for participants joining
> from America or Europe/Africa because most people I talked to live in
> these areas. If people living in Asia/Australia time zones want to join
> as well please let me know. We can use alternating time slots to make
> this possible.
>
> Please let me know what you think.
>
> Thanks,
>
--
Carlos López
Security Engineer
SUSE Software Solutions
next prev parent reply other threads:[~2023-09-07 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 10:26 [svsm-devel] [RFC] SVSM Development Call Jörg Rödel
2023-08-31 16:02 ` Giani, Dhaval
2023-08-31 16:40 ` Dewey, Larry
2023-09-06 20:24 ` Bilbao, Carlos
2023-08-31 19:18 ` Claudio Carvalho
2023-09-01 7:01 ` Oliver Steffen
2023-09-05 13:12 ` Tom Lendacky
2023-09-07 12:29 ` Carlos López [this message]
2023-09-07 16:41 ` Jörg Rödel
2023-09-07 16:57 ` Giani, Dhaval
2023-09-07 18:18 ` Jörg Rödel
[not found] <PBqvbMM28sdqewQ@suse.de>
2023-09-01 7:16 ` Stefano Garzarella
2023-09-01 15:24 ` Dionna Amalie Glaze
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=873bdb74-a67b-4fe7-a41b-ba3477fccb01@suse.de \
--to=clopez@suse.de \
--cc=jroedel@suse.de \
--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.