From: Mark Wielaard <mark@klomp.org>
To: Zack Weinberg <zack@owlfolio.org>, overseers@sourceware.org
Cc: gcc@gcc.gnu.org, libc-alpha <libc-alpha@sourceware.org>,
binutils developers <binutils@sourceware.org>,
gdb developers <gdb@sourceware.org>
Subject: Re: Sourceware - Building Together, Fri 11, 15:00 UTC
Date: Fri, 11 Sep 2026 15:09:27 +0200 [thread overview]
Message-ID: <77a6a77035dc85944eae6122f1364a4ae47efaa3.camel@klomp.org> (raw)
In-Reply-To: <51cb2b32-6cc0-47c8-8800-3fea8368ae39@app.fastmail.com>
Hi Zack,
On Thu, 2026-09-10 at 17:45 -0400, Zack Weinberg wrote:
> On Thu, Sep 10, 2026, at 7:58 AM, Mark Wielaard wrote:
> > Tomorrow is the second Friday of the month, so it is time for the
> > Sourceware Open Office again!
>
> I recognize that this is a meeting about a whole bunch of things and not
> just the argument presently taking place on libc-alpha, but I have to
> ask that the *topic* of that argument be declared off-topic for this
> meeting. The glibc project is currently trying to dig out from a
> catastrophic process failure and we really, really need everyone even
> peripherally involved to agree to stick *exclusively* to libc-alpha when
> discussing anything related to the question of whether glibc should move
> any or all of its hosting off of sourceware.
No worries. glibc does that every 9 months or so. We really have no
intention to discuss any of that. I really appreciate you trying to
resolve that issue. But it has been going on for so long that most
people just want to get back to work.
The monthly Sourceware Open Office meeting is for simple technical
coordination. In this case about setting up some buildbots (for GDB),
hooking up the patchwork CI/CD curator (and maybe some of the
buildbots). Investigate bugspray, a public-inbox bugzilla integrator. A
quick update on fundraising progress. And discussion of what people to
like hear about for the builders/CI talk at Cauldron since we are
working on those issues anyway. Also it is a great time to ask about
any infrastructure issues you might experience where it helps to have
direct insight into real time logs.
There is also no requirement to attend unless you really could use some
direct admin help.
So see you in #overseers on irc.libera.chat at date -d "Fri Sep 10
15:00 UTC 2026". Or not if you have better things to do with your time.
Cheers,
Mark
prev parent reply other threads:[~2026-09-11 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 11:58 Mark Wielaard
2026-09-10 21:45 ` Zack Weinberg via Gdb
2026-09-11 13:09 ` 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:
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=77a6a77035dc85944eae6122f1364a4ae47efaa3.camel@klomp.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 \
--cc=zack@owlfolio.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