public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
Subject: Sourceware 2024 - The Plan
Date: Mon, 25 Mar 2024 10:58:27 +0100	[thread overview]
Message-ID: <> (raw)

The Sourceware Project Leadership Committee in discussion with the
Software Freedom Conservancy staff came up with the Sourceware 2024
plan and is looking at longer term projects that would be needed to
keep your infrastructure running smoothly and securely for the next
couple of years. We are currently discussing how to distribute these
tasks over paid staff, overseers, project admin volunteers and

We realize that our plans may not be your plans, so really like to get
feedback. It is our goal to offer a worry-free, friendly home for Free
Software core toolchain and developer tools projects. So please do
reach out and share your ideas on the overseers mailinglist, file
infrastructure bugs, join our channel #overseers on irc or join one of
the monthly open office hours:

For 2024 we want to concentrate on isolating and scaling the
services. In the last two years we doubled the number of machines (and
more are on the way!) that we run the services on. And some of the new
services are already setup in containers or on isolated VMs. But most
of the services are still isolated through traditional unix
mechanisms.  Moving those into their own container or VM will help
scaling by making it easy to move between separate physical
machines. It will also provide security in depth.

It is our preference to run distro packaged software (e.g. mailman,
postfix, public-inbox, etc.). That way we have easy security updates.
But for some services we track an upstream stable branch (e.g.
buildbot, patchwork and bugzilla). While isolating/containerizing
these services we will also publish the internal git repos (if they
contain any local adjustments), so we can easier share patches with
other organizations. Ideally we'll also publish ansible playbooks.
That way, over time, we will provide services that anybody can
replicate and setup themselves.

Longer term we identified a couple of thing, mainly around isolation
(the theme of 2024), email, spam, mailinglists, search, AI bots and
services upgrades that we believe are important to prepare for.

Concretely we are looking at:

- mailman2 upgrade/replacement

- bugzilla upgrade

- (local) search and AI bot/spiders, sitemaps, ...

- Distributed spam fighting

- buildbot email templates, pre-commit testing, buildbot-travis, ...

More items can be found in the Sourceware infrastructure bugzilla

If you read this far we really like your feedback, even if it is a
simple "OK!", Reply-To: Or add you comments
to the bugzilla items above. And take a look at other ways to

You can also help by becoming a Conservancy Sustainer or donating directly to


  Frank Ch. Eigler, Christopher Faylor, Ian Kelling, Ian Lance Taylor,
  Tom Tromey, Jon Turney, Mark J. Wielaard, Elena Zannoni

                 reply	other threads:[~2024-03-25  9:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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