From: Mark Wielaard <mark@klomp.org>
To: Andrea Pinski <andrew.pinski@oss.qualcomm.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
gcc developers <gcc@gcc.gnu.org>,
glibc developers <libc-alpha@sourceware.org>,
gdb developers <gdb@sourceware.org>,
binutils developers <binutils@sourceware.org>
Subject: Re: Meeting Minutes - Office Hours for CTI - 2026-09-18
Date: Tue, 22 Sep 2026 11:46:32 +0200 [thread overview]
Message-ID: <20260922094632.GF6122@gnu.wildebeest.org> (raw)
In-Reply-To: <CALvbMcB=jvi0JUwK=bZGdPGEGGtcPXHyrT0Ru1wwTqUWB6FV3Q@mail.gmail.com>
Hi,
On Mon, Sep 21, 2026 at 09:55:47AM -0700, Andrea Pinski via Gdb wrote:
> On Mon, Sep 21, 2026 at 9:34 AM Carlos O'Donell via Gcc <gcc@gcc.gnu.org> wrote:
> > Posting across the project mailing lists since some developers had
> > questions and are only subscribed on some lists.
>
> This assumes that there is consensus on moving forward with any
> proposal. And second, there is not enough information in these
> meeting notes.
> [...]
> > * Discuss on libc-alpha finalizing git URLs
> > * git.glibc.coretoolchain.dev/glibc (RO mirror)
> > * gitolite.glibc.coretoolchain.dev/glibc (RW for developers)
> > * gitolite.glibc.coretoolchain.dev/glibc-keyring (RW for admins)
>
> What is the rationale for having 3 different URLs? What is the
> rationale for using `coretoolchain.dev` rather than something more
> specific named with gnu?
> Why have a glibc subdomain? Etc.
If you want and have a good rational then Sourceware could of course
provide (sub)domains like glibc.sourceware.org or
gnu.toolchain.dev/glibc or (in cooperation with the fsf-tech team)
glibc.gnu.org, etc. backed by different VMs or services.
> [...]
> There is no rationale there at all; even the previous meetings notes
> don't mention why. Rather just the final choices.
>
> This is a communication failure and a trust issue here.
>
> > * ACTION: Carlos to email the mailing list with proposals for discussion.
Best action item would be to first seek concensus on moving forward
with any of these proposals. Otherwise you risk spending time on
things nobody will use or worse create a fork and split the community:
https://inbox.sourceware.org/3fb85049-8d6a-4f83-a0a3-770cc385e6af@app.fastmail.com
Like Zoë said we could achieve much more by working together:
https://inbox.sourceware.org/7021a9fb-2476-463c-8eab-a4e254d93df2@fsf.org
And there have been many constructive suggestions how we could do that.
Cheers,
Mark
next prev parent reply other threads:[~2026-09-22 9:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 16:32 Carlos O'Donell via Gdb
2026-09-21 16:55 ` Andrea Pinski via Gdb
2026-09-21 17:58 ` DJ Delorie via Gdb
2026-09-22 18:14 ` Siddhesh Poyarekar
2026-09-22 9:46 ` Mark Wielaard [this message]
2026-09-22 18:34 ` Joseph Myers via Gdb
2026-09-22 19:02 ` Andrea Pinski via Gdb
2026-09-22 19:14 ` DJ Delorie via Gdb
2026-09-22 19:22 ` Andrea Pinski via Gdb
2026-09-24 14:55 ` Siddhesh Poyarekar
2026-09-22 20:37 ` Joseph Myers via Gdb
2026-09-23 15:58 ` Mark Wielaard
2026-09-24 15:15 ` Siddhesh Poyarekar
2026-09-24 15:21 ` Siddhesh Poyarekar
2026-09-25 21:28 ` Carlos O'Donell via Gdb
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=20260922094632.GF6122@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=andrew.pinski@oss.qualcomm.com \
--cc=binutils@sourceware.org \
--cc=carlos@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libc-alpha@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