From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 0DFD5384B0C9; Thu, 6 Oct 2022 20:02:21 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0DFD5384B0C9 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from reform (deer0x0d.wildebeest.org [172.31.17.143]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id E21CB3021EAC; Thu, 6 Oct 2022 22:02:19 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 6618E2E80560; Thu, 6 Oct 2022 22:02:19 +0200 (CEST) Date: Thu, 6 Oct 2022 22:02:19 +0200 From: Mark Wielaard To: Overseers mailing list Cc: Siddhesh Poyarekar , gdb@sourceware.org, libc-alpha@sourceware.org, binutils@sourceware.org, gcc@gcc.gnu.org Subject: Re: The GNU Toolchain Infrastructure Project Message-ID: References: <6f6d141b-b776-8707-2c91-dc38d20aa9e1@gotplt.org> <20221004171007.oc2ot6eu6l24aipn@cgf.cx> <05b0f7fa-7077-5a8b-0c2f-dfb3068dd10f@gotplt.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-3033.4 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi Siddhesh, On Tue, Oct 04, 2022 at 03:10:35PM -0400, Siddhesh Poyarekar via Overseers wrote: > > We do take this proposal, and all other suggestions people make about > > the sourceware infrastructure, seriously, but a lot of details of this > > proposal are still unclear. We are trying to get as much details as > > possible so we can see how this fits into the current sourceware > > roadmap, get a better understanding of the budgetary needs, file > > sourceware infrastructure bugs with those details. All to get a better > > understanding what the real needs are and document the necessary steps > > forward. > > I had in fact missed the websites mention, sorry I overreacted to your > comment. In that case, I don't know if the GNU websites are actually part > of this proposal. No worries. It seems everybody is somewhat unclear on the details of this proposal. Making it hard for people not to speculate a little. And it seems the scope changed between when various "key stakeholders" were informed, the LF/IT presentation, the Cauldron talk and what eventually got posted. That is why we are trying to collect all details and file sourceware infrastructure bugs to track the various technical needs from a community perspective. But it would be really nice to hear directly from the Linux Foundation and the OpenSSF about what exactly they are proposing, which parts of the proposal are mandatory, which can be mixed and matched, and how they see this working together with Sourceware becoming a Software Freedom Conservancy member project. Cheers, Mark