From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org
Subject: Sourceware Open Office Hours
Date: Mon, 15 May 2023 20:32:16 +0200 [thread overview]
Message-ID: <20230515183216.GA11203@gnu.wildebeest.org> (raw)
As a Sourceware project admin or admin of one of the Sourceware
services you might be interested in discussing what the recent
announcement of Sourceware joining the Software Freedom Conservancy as
member project means.
https://sfconservancy.org/news/2023/may/15/sourceware-joins-sfc/
There will be no big changes, this is just an oppertunity to protect
the confidence in the long term future of Sourceware. There is a small
budget already available which we would like to use for extra
redundancy and backup services. But we are happy to discuss other
ideas like mentioned in the original proposal and sourceware technical
roadmap [1] [2].
We will be available to discuss all this in #overseers on
irc.libera.chat now from 18:00 till 19:00 UTC. And we will also start
regular Overseers Open Office Hours every second Friday of the month
on irc at the same time.
Of course you are welcome to drop into the #overseers channel at any
time and we can also be reached through email and bugzilla:
https://sourceware.org/mission.html#organization
If you aren't already and want to keep up to date on Sourceware
infrastructure services then please also subscribe to the overseers
mailinglist. https://sourceware.org/mailman/listinfo/overseers
[1] https://sourceware.org/pipermail/overseers/2022q3/018802.html
[2] https://inbox.sourceware.org/overseers/YrLdfDWzq1T4k5xg@wildebeest.org/
next reply other threads:[~2023-05-15 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 18:32 Mark Wielaard [this message]
2023-06-09 9: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=20230515183216.GA11203@gnu.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).