public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
Subject: Re: Sourceware infrastructure presentation and community Q&A
Date: Sun, 1 Jan 2023 00:36:57 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Nov 15, 2022 at 11:06:14PM +0100, Mark Wielaard wrote:
> We like to discuss how to use the new infrastructure setup this last
> year, builder, try/ci/full buildbots, bunsen testsuite analysis,
> patchwork patch tracking, handling patches/email with public-inbox,
> b4, the sourcehut mirror. And the future of Sourceware as a Software
> Freedom Conservancy member project. (*)

Thanks to everybody who could attend.  For those who couldn't the html
slides and markdown sources with the presenter notes are here:
And a (video) recording is here:

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:

In 2023 Sourceware will be 25 years. Happy new year!

(*) The Software Freedom Conservancy is currently running a fundraiser:

      reply	other threads:[~2022-12-31 23:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 18:58 Proposing Sourceware as SFC member project Mark Wielaard
2022-09-08 23:07 ` Sourceware accepted " Mark Wielaard
2022-11-15 22:06   ` Sourceware infrastructure presentation and community Q&A Mark Wielaard
2022-12-31 23:36     ` 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).