From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Carsten Strotmann <cas@strotmann.de>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Debian m68k <debian-68k@lists.debian.org>
Subject: Re: Planning a Debian/Linux m68k Meeting in 2020
Date: Wed, 20 May 2020 22:51:39 +0200 [thread overview]
Message-ID: <f0be6fc6-3836-5fae-3231-270a1ffe8112@physik.fu-berlin.de> (raw)
In-Reply-To: <865zcqz6lz.fsf@emacs.strotmann.de>
Hi!
On 5/20/20 10:36 PM, Carsten Strotmann wrote:
> after collecting some feedback, we will now try to get a small online
> workshop organized to discuss a possible 2020 m68k meeting (virtual or/and
> in person).
>
> Here is a poll for a date for the planning workshop (not for the m68k
> meeting):
>
> <https://nuudel.digitalcourage.de/li1otkp9sBrzu9Xm>
>
> The meeting time would be 20:00 CEST.
Good idea. Added myself to the list.
> I operate a Jitsi Video-Conference-Server we could use for the meeting,
> but I'm also open for other options.
I don't have any strong preference on this but I think Jitsi works very well.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2020-05-20 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 8:04 Planning a Debian/Linux m68k Meeting in 2020 Carsten Strotmann
2020-04-10 12:05 ` John Paul Adrian Glaubitz
[not found] ` <1802398089.6357995.1586526646576@mail.yahoo.com>
2020-04-10 14:54 ` Christian T. Steigies
2020-05-20 20:36 ` Carsten Strotmann
2020-05-20 20:51 ` John Paul Adrian Glaubitz [this message]
2020-06-01 10:50 ` Carsten Strotmann
2020-06-02 7:16 ` John Paul Adrian Glaubitz
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=f0be6fc6-3836-5fae-3231-270a1ffe8112@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=cas@strotmann.de \
--cc=debian-68k@lists.debian.org \
--cc=linux-m68k@lists.linux-m68k.org \
/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;
as well as URLs for NNTP newsgroup(s).