general high-level discussion about spectrum
 help / color / mirror / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: discuss@spectrum-os.org
Subject: Help wanted: organising community calls
Date: Tue, 18 Apr 2023 20:49:08 +0000	[thread overview]
Message-ID: <20230418204908.turuowd3efvcwlmy@x220> (raw)

[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]

An annoying longstanding problem with Spectrum is that I do a lot of
very interesting work, but I'm not very good at keeping people following
the project informed about it.  Over the years I've tried writing status
updates, but it's really difficult for me to do them consistently.  The
community calls we've had a couple of are a good format for me,
especially because they're interactive, but the potential attendees
change over time, depending on who's interested in the project at the
moment, and so it's important to work with their schedules to make sure
enough people come to make it worthwhile.  That means that organising
the call is yet another task I should do on a schedule, and struggle
with.

So, I was wondering if there's somebody out there who's better at
sticking to schedules and would be able to help with this part.  It
really just involves making the scheduling poll, sending out an email
about it, and then checking the responses when the poll closes to pick
the meeting time, and sending out another email announcing that time.
Ideally, I think we'd have a community call every month.

If that sounds like that something that would be easier for you than it
is for me, it would be lovely if you could get in touch in any of the
normal ways. :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2023-04-18 20:49 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=20230418204908.turuowd3efvcwlmy@x220 \
    --to=hi@alyssa.is \
    --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).