public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: gdb@sourceware.org, libc-alpha@sourceware.org,
	binutils@sourceware.org, gcc@gcc.gnu.org,
	"Zoë Kooyman" <zoe@fsf.org>
Subject: Re: Toolchain Infrastructure project statement of support
Date: Thu, 13 Oct 2022 14:25:29 -0400	[thread overview]
Message-ID: <20221013182529.sm76fysq37sv754x@cgf.cx> (raw)
In-Reply-To: <2513b668-9ebd-9e78-7263-dc24f4a9558a@redhat.com>

Re: https://sourceware.org/pipermail/overseers/2022q4/018981.html

On Wed, Oct 12, 2022 at 12:43:09PM -0400, Carlos O'Donell wrote:
>The GNU Toolchain project leadership supports the proposal[1] to move the
>services for the GNU Toolchain to the Linux Foundation IT under the auspices of
>the Toolchain Infrastructure project (GTI) with fiscal sponsorship from the
>OpenSSF and other major donors.

Noted, however, a list of signatories does not automatically confer
authority over any particular project.  Any participation from 
overseers in moving projects to different infrastructure will require
clear approval from the individual projects themselves.

Also, the FSF, being the existing fiscal sponsor to these projects,
surely needs to review the formal agreements before we sunset our
infrastructural offerings to glibc, gcc, binutils, and gdb and hand
control of the projects' infrastructure over to a different entity.

We'd like to assure the communities that, when and if any individual
project formally expresses the decision of their developers to transfer
their services, we'll endeavor to make the move as smooth as possible. 
Those projects that wish to stay will continue to receive the best
services that the overseers can offer, with the ongoing assistance of
Red Hat, the SFC, and, when relevant, the FSF tech team.


       reply	other threads:[~2022-10-13 18:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2513b668-9ebd-9e78-7263-dc24f4a9558a@redhat.com>
2022-10-13 18:25 ` Christopher Faylor [this message]
2022-10-14 12:33   ` Siddhesh Poyarekar
2022-10-17 15:10   ` Mark Wielaard
2022-10-17 16:11     ` Siddhesh Poyarekar
2022-10-18  9:50       ` Mark Wielaard
2022-10-18 15:17         ` Siddhesh Poyarekar
2022-10-18 16:42           ` Christopher Faylor
2022-10-18 18:13             ` Siddhesh Poyarekar
2022-10-18 18:14               ` Siddhesh Poyarekar
2022-10-18 18:47                 ` Paul Smith
2022-10-21  0:33               ` Alexandre Oliva
2022-10-23  8:59           ` Ian Kelling
2022-10-23 13:27             ` Siddhesh Poyarekar
2022-10-23 15:16               ` Frank Ch. Eigler
2022-10-23 16:07                 ` Siddhesh Poyarekar
2022-10-23 16:32                   ` Siddhesh Poyarekar
2022-10-23 17:01                   ` Jeff Law
2022-10-23 22:35                     ` Christopher Faylor
2022-10-23 17:09                   ` Frank Ch. Eigler
2022-10-23 17:38                     ` Jeff Law
2022-10-24  1:51                     ` Siddhesh Poyarekar
2022-10-23 20:57               ` Christopher Faylor
2022-10-23 21:17                 ` Siddhesh Poyarekar
2022-10-23 21:59                   ` Christopher Faylor
2022-10-24  1:29                     ` Siddhesh Poyarekar
2022-10-23 11:33       ` Ian Kelling
2022-10-23 16:17         ` Siddhesh Poyarekar
2022-10-23 18:56           ` Konstantin Ryabitsev
2022-10-23 21:19 ` Alexandre Oliva
2022-10-23 22:07   ` Christopher Faylor
2022-10-12 17:40 Carlos O'Donell

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=20221013182529.sm76fysq37sv754x@cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).