public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org
Cc: gcc@gcc.gnu.org, libc-alpha@sourceware.org,
	binutils@sourceware.org, gdb@sourceware.org
Subject: Sourceware Open Office, Friday 18:00 UTC, don't feel isolated
Date: Thu, 7 Mar 2024 23:06:58 +0100	[thread overview]
Message-ID: <20240307220658.GH24213@gnu.wildebeest.org> (raw)

TL;DR; Friday March 8, 18:00 UTC, Sourceware Open Office discussion of
services priorities for 2024, irc.liberachat.org #overseers

To get the right time in your local timezone:
$ date -d "Fri Mar 8 18:00:00 UTC 2024"

In 2022 we published the Sourceware GNU Toolchain Infrastructure
Roadmap [1]. And showed we could provide new services like patchwork,
buildbot, public-inbox and the snapshots server to help the community
become more efficient.

In 2023 we celebrated the Sourceware 25 Roadmap [2] and joined the
Software Freedom Conservancy as member project [3]. Showing we could
grow while diversifying hardware and service partners and raising
funds with a fiscal sponsor.

For 2024 we [4] 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.

But we of course want to do this in a way that doesn't disrupt any
services or causes a messy migration. And we want the projects to be
in control. So please come and discuss your projects priorities and
essentials.

For this meeting we will also have a BBB meeting room:
https://bbb.sfconservancy.org/b/mar-aom-dmo-fko
(But the real discussion will be in the irc channel)

[1] https://gnu.wildebeest.org/blog/mjw/2022/06/22/sourceware-gnu-toolchain-infrastructure-roadmap/
[2] https://sourceware.org/sourceware-25-roadmap.html
[3] https://sfconservancy.org/news/2023/may/15/sourceware-joins-sfc/
[4] https://sourceware.org/mission.html#plc

             reply	other threads:[~2024-03-07 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 22:06 Mark Wielaard [this message]
2024-03-25  5:55 최종석

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=20240307220658.GH24213@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.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).