From: Carsten Strotmann <cas@strotmann.de>
To: linux-m68k <linux-m68k@lists.linux-m68k.org>,
Debian-68k <debian-68k@lists.debian.org>
Subject: Virtual m68k Developer Meeting 2020
Date: Thu, 18 Jun 2020 20:45:32 +0200 [thread overview]
Message-ID: <86sgeskyb7.fsf@emacs.strotmann.de> (raw)
Hi,
during a nice virtual meeting we've had on 5th of June with a
couple a
people from the m68k community, the decision was made to organize
a
virtual meeting for 2020 (which might be followed by a 'in person'
meeting in 2021).
I've setup a poll to find a date (or multiple dates) in
Q4/2020. If you
are interested in joining the meeting, please go to the poll and
fill in
your dates:
<https://nuudel.digitalcourage.de/sBwNfnUh2BjGWHJY>
The poll will run until end of August, the date(s) for the meeting
will
be announced in the first week of September.
The next virtual eventing chat meeting will be on 10th of July
2020
starting at 8:00pm CEST (20:00 H) on <https://meet.m68k.info> (the
meeting page will appear until this date [famous last words]).
Greetings
Carsten
next reply other threads:[~2020-06-18 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 18:45 Carsten Strotmann [this message]
2020-07-10 8:18 ` virtual eventing chat meeting today Carsten Strotmann
2020-07-10 8:26 ` John Paul Adrian Glaubitz
2020-07-10 17:35 ` Carsten Strotmann
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=86sgeskyb7.fsf@emacs.strotmann.de \
--to=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).