From: Richard Palethorpe <rpalethorpe@suse.de>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC] LTP open monthly meeting
Date: Thu, 26 Oct 2023 11:01:12 +0100 [thread overview]
Message-ID: <87pm11u2bk.fsf@suse.de> (raw)
In-Reply-To: <20231019125948.GA56107@pevik>
Hello,
Petr Vorel <pvorel@suse.cz> writes:
> Hi Marius, all,
>
>> > And which platform would you use?
>
>> What about https://meet.jit.si/linux-test-project ? I assume MS Teams would
> +1. In case it does not work properly for all, I'd try
> https://meet.google.com/.
>
> Kind regards,
> Petr
>
>> not be very appreciated in the kernel community (and I'm not even sure whether
>> we could invite non-SUSE employees easily to those meetings).
> IMHO SUSE's Teams account is no-go for this.
>
> Kind regards,
> Petr
>
>> Best Regards
>> Marius
In the past we had some issues with Jitsi, but generally it has worked
fine for me. So I'm happy with this.
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-10-26 10:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 9:31 [LTP] [RFC] LTP open monthly meeting Richard Palethorpe
2023-10-19 11:03 ` Andrea Cervesato via ltp
2023-10-19 11:08 ` Petr Vorel
2023-10-19 11:30 ` Marius Kittler
2023-10-19 12:59 ` Petr Vorel
2023-10-26 10:01 ` Richard Palethorpe [this message]
2023-10-19 11:39 ` Wei Gao via ltp
2023-10-19 12:28 ` Cyril Hrubis
2023-10-20 3:04 ` Li Wang
2023-10-20 11:56 ` Cyril Hrubis
2023-10-23 8:10 ` Richard Palethorpe
2023-10-23 8:51 ` Li Wang
2023-10-26 10:16 ` [LTP] Open monthly meeting 1st of November 09:00 UTC Richard Palethorpe
2023-10-27 2:34 ` Li Wang
2023-11-01 9:33 ` Richard Palethorpe
2023-11-01 10:00 ` Cyril Hrubis
2023-11-01 10:12 ` Petr Vorel
2023-11-01 14:14 ` Jan Stancek
2023-11-03 6:56 ` Petr Vorel
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=87pm11u2bk.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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.