From: Alyssa Ross <alyssa.ross@unikie.com>
To: discuss@spectrum-os.org
Subject: Upcoming Spectrum community call
Date: Tue, 29 Nov 2022 10:56:37 +0000 [thread overview]
Message-ID: <20221129105637.dlabxp5l673hjpon@x220> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 764 bytes --]
Tomorrow (Wednesday) at 12:00 UTC I will be holding an experimental
Spectrum community call. The idea here is that it gives all
participants in the Spectrum community (interested users, developers,
etc.) the chance to meet and talk about upcoming development work.
So if you would like to hear or ask questions about where Spectrum is
going, or if you're working on Spectrum (or would like to be!) and want
to share what you're doing, please join us tomorrow at the following URL:
https://meet.jit.si/moderated/f20761163cb82478c3cc28dbffc1edcd788d8766232fa96f8dc0642b88a6ee59
Since somebody has asked already: I don't plan on recording this call.
If it goes well and we make this a regular thing, we can discuss at that
point whether calls should be recorded.
[-- Attachment #1.2: invite.ics --]
[-- Type: text/calendar, Size: 605 bytes --]
BEGIN:VCALENDAR
PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Etc/UTC
BEGIN:STANDARD
TZOFFSETFROM:+0000
TZOFFSETTO:+0000
TZNAME:GMT
DTSTART:19700101T000000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
CREATED:20221129T104341Z
LAST-MODIFIED:20221129T104431Z
DTSTAMP:20221129T104431Z
UID:bec6b49d-ae2a-40fa-b44e-fd7291e64efb
SUMMARY:Spectrum community call
ORGANIZER;PARTSTAT=NEEDS-ACTION;ROLE=REQ-PARTICIPANT:mailto:alyssa.ross@un
ikie.com
DTSTART;TZID=Etc/UTC:20221130T120000
DTEND;TZID=Etc/UTC:20221130T130000
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-11-29 10:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221129105637.dlabxp5l673hjpon@x220 \
--to=alyssa.ross@unikie.com \
--cc=discuss@spectrum-os.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).