From: Mark Wielaard <mark@klomp.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: "gcc developers" <gcc@gcc.gnu.org>,
"glibc developers" <libc-alpha@sourceware.org>,
"gdb developers" <gdb@sourceware.org>,
"binutils developers" <binutils@sourceware.org>,
"Overseers mailing list" <overseers@sourceware.org>,
cti-tac@lists.linuxfoundation.org, "Zoë Kooyman" <zoe@fsf.org>,
"Karen M. Sandler" <karen@sfconservancy.org>
Subject: Re: Core Toolchain Infrastructure - October 2024 update
Date: Wed, 30 Oct 2024 11:39:12 +0100 [thread overview]
Message-ID: <20241030103912.GD28606@gnu.wildebeest.org> (raw)
In-Reply-To: <9ee5b9e1-3f84-4d9e-8249-7a4bf8080bb0@redhat.com>
Hi Carlos,
On Tue, Oct 29, 2024 at 06:02:03PM -0400, Carlos O'Donell via Gcc wrote:
> Recent discussions on the glibc mailing list make it clear
> that we need to expand and discuss more about our "why" along with
> the "what" and "how" of these changes.
Zoe wrote a good summary of that discussion back in July:
https://inbox.sourceware.org/f20ce996-e9c6-4b6c-856d-eec6e14af26e@fsf.org/
Has anything changed since then to address the issues raised by her
and others?
I don't believe the community is helped by trying to set up yet
another, corporate controlled, organization or doing some highly
disruptive move of some parts of the services our projects are using.
A couple of years ago we spend the time and energy to setup Sourceware
as an organization that provides free infrastructure for our free
software projects. And made sure to work out our relationship with our
fiscal sponsor: https://sourceware.org/Conservancy-Sourceware-FSA.pdf
https://sfconservancy.org/projects/policies/conflict-of-interest-policy.html
We have a generic mission to provide core toolchain and developer
tools project with free software infrastructure:
https://sourceware.org/mission.html
The history and general roadmap for the next 25 years are descriped at
https://sourceware.org/sourceware-25-roadmap.html
And a specific roadmap and projects for state of the art sustainable
secure and robust services, the Secure Sourceware Project Goals, are
described in https://sourceware.org/sourceware-security-vision.html
I noticed you attended the Infrastructure BoF at the Cauldron and seem
to be experimenting with the new Forge we setup. I hope you will be
happy to work with the existing community and the existing
organizations that support the GNU toolchain and the Sourceware
infrastructure, instead of trying to setup yet another organization
that would split our efforts.
Cheers,
Mark
next prev parent reply other threads:[~2024-10-30 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 22:02 Carlos O'Donell via Gdb
2024-10-30 10:39 ` Mark Wielaard [this message]
2024-10-30 12:32 ` Carlos O'Donell via Gdb
2024-10-30 15:45 ` Mark Wielaard
2024-10-30 16:23 ` Karen M. Sandler via Gdb
2024-10-30 16:45 ` Joseph Myers via Gdb
2024-10-30 16:52 ` Carlos O'Donell via Gdb
2024-10-30 17:06 ` Joseph Myers via Gdb
2024-11-04 10:50 ` Mark Wielaard
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=20241030103912.GD28606@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=carlos@redhat.com \
--cc=cti-tac@lists.linuxfoundation.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=karen@sfconservancy.org \
--cc=libc-alpha@sourceware.org \
--cc=overseers@sourceware.org \
--cc=zoe@fsf.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