public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Zoë Kooyman" <zoe@fsf.org>
To: overseers@sourceware.org
Subject: Sourceware infrastructure - A presentation and community Q&A
Date: Tue, 15 Nov 2022 18:18:56 +0100	[thread overview]
Message-ID: <6e9cde97-d880-5343-6cfd-16a648cf67f6@fsf.org> (raw)

Hi All,

At the request of many of you, the FSF is hosting a presentation
and conversation with the Sourceware overseers this Friday, 18
November on the current sourceware infrastructure and future
plans. We start at 11:00am Eastern (16:00 UTC), and it will be hosted on
the FSF Big Blue Button instance and streamed live.

To limit some bandwith we will also have our #fsf irc channel
available on Libera.Chat to participate. We learned previously that, as long
as people do not use their cameras when not presenting, we can
host quite some people inside the BBB, so do not hesitate to
reach out to us to join in the channel (first come first serve).

We hope you can all make it!  Questions you would like to see
discussed can be sent to campaigns@fsf.org in advance, and you can find some
more information the specifics of the event here:

https://www.fsf.org/events/sourceware-infrastructure-a-presentation-and-community-q-a

Thank you!

-- 
Zoë Kooyman // Executive Director
Free Software Foundation

Join the FSF and help us defend software freedom:
https://my.fsf.org/

US government employee? Use CFC charity code 63210 to support us through
the Combined Federal Campaign. https://cfcgiving.opm.gov/


             reply	other threads:[~2022-11-15 17:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 17:18 Zoë Kooyman [this message]
2022-11-20  0:09 ` Mark Wielaard
2022-11-20 14:01   ` Ian Kelling
2023-01-01  1:38 ` Mark Wielaard

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=6e9cde97-d880-5343-6cfd-16a648cf67f6@fsf.org \
    --to=zoe@fsf.org \
    --cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).