public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
Subject: Re: Sourceware Open Office Hours
Date: Fri, 9 Jun 2023 11:38:56 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, May 15, 2023 at 08:32:16PM +0200, Mark Wielaard wrote:
> 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.
> 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
> 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.

Which is today! Please feel free to drop by with any Sourceware
hosting questions. Help with email (archives, spam), secure supply
chain, setting up new buildbot CI, producing snapshots, helping write
up some POCs, discussing how the PLC should work, or just to say
things are all working fine.
> Of course you are welcome to drop into the #overseers channel at any
> time and we can also be reached through email and bugzilla:
> If you aren't already and want to keep up to date on Sourceware
> infrastructure services then please also subscribe to the overseers
> mailinglist.
> [1]
> [2]

      reply	other threads:[~2023-06-09  9:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 18:32 Mark Wielaard
2023-06-09  9: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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).