From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Subject: Re: Sourceware infrastructure - A presentation and community Q&A
Date: Sun, 1 Jan 2023 02:38:14 +0100 [thread overview]
Message-ID: <Y7DkBrktxmBlmOAW@wildebeest.org> (raw)
In-Reply-To: <6e9cde97-d880-5343-6cfd-16a648cf67f6@fsf.org>
On Tue, Nov 15, 2022 at 06:18:56PM +0100, Zoë Kooyman via Overseers wrote:
> 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
Thanks to everybody who could attend. For those who couldn't the html
slides and markdown sources with the presenter notes are here:
https://gnu.wildebeest.org/blog/mjw/2022/11/20/new-services-for-sourceware-sfc-fsf/
And a (video) recording is here:
https://media.libreplanet.org/u/libreplanet/m/sourceware-infrastructure-a-presentation-and-community-q-a/
We hope to have answered all questions, but if we missed anything, or
you want to help with the infrastructure please contact us at the
overseers mailinglist or file a sourceware infrastructure bug:
https://sourceware.org/mailman/listinfo/overseers
https://sourceware.org/bugzilla/buglist.cgi?component=Infrastructure&product=sourceware
In 2023 Sourceware will be 25 years. Happy new year!
prev parent reply other threads:[~2023-01-01 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 17:18 Zoë Kooyman
2022-11-20 0:09 ` Mark Wielaard
2022-11-20 14:01 ` Ian Kelling
2023-01-01 1:38 ` Mark Wielaard [this message]
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=Y7DkBrktxmBlmOAW@wildebeest.org \
--to=mark@klomp.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).