From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id CBVgCnVYSGMKzQsAWB0awg (envelope-from ) for ; Thu, 13 Oct 2022 14:27:01 -0400 Received: by simark.ca (Postfix, from userid 112) id 281B51E112; Thu, 13 Oct 2022 14:27:01 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=dZDmd6QM; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id D54861E0D5 for ; Thu, 13 Oct 2022 14:27:00 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 367613850430 for ; Thu, 13 Oct 2022 18:27:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 367613850430 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1665685620; bh=M9bQqtZ+4hQjUR4AehSzzG6u5CBL9jkgrnqr9MXoiFE=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=dZDmd6QMI/T36GP55C8iFBXTwWPNAblCqhdOZ6bQFhSzmL9YeviwxfunUYAG7GlWd 5iDWg7G/HNlKcnvgbKPAoHZfkNXESoF4rrQPfL+1857wmNyeKwqJjCDZ1lVr+otaSR +QeZWOZFQCL3ouzXi2ubg7ZbmtRf+Uudr+DpupXY= Received: from cgf.cx (external.cgf.cx [107.170.62.102]) by sourceware.org (Postfix) with ESMTPS id 151A63858C56; Thu, 13 Oct 2022 18:25:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 151A63858C56 DKIM-Filter: OpenDKIM Filter v2.11.0 cgf.cx A219E10FE54 Date: Thu, 13 Oct 2022 14:25:29 -0400 To: Overseers mailing list Subject: Re: Toolchain Infrastructure project statement of support Message-ID: <20221013182529.sm76fysq37sv754x@cgf.cx> Mail-Followup-To: Overseers mailing list , gdb@sourceware.org, libc-alpha@sourceware.org, binutils@sourceware.org, gcc@gcc.gnu.org, =?utf-8?Q?Zo=C3=AB?= Kooyman References: <2513b668-9ebd-9e78-7263-dc24f4a9558a@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2513b668-9ebd-9e78-7263-dc24f4a9558a@redhat.com> X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Christopher Faylor via Gdb Reply-To: Christopher Faylor Cc: gdb@sourceware.org, =?utf-8?Q?Zo=C3=AB?= Kooyman , libc-alpha@sourceware.org, binutils@sourceware.org, gcc@gcc.gnu.org Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" 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.