From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id eIUvKKpdImdOtx8AWB0awg (envelope-from ) for ; Wed, 30 Oct 2024 12:24:10 -0400 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=KksnOU8P; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 9E8D21E5A1; Wed, 30 Oct 2024 12:24:10 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-6.8 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_BLOCKED,RCVD_IN_VALIDITY_CERTIFIED,RCVD_IN_VALIDITY_RPBL, RCVD_IN_VALIDITY_SAFE,URIBL_BLOCKED,URIBL_DBL_BLOCKED_OPENDNS autolearn=unavailable autolearn_force=no version=4.0.0 Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 0BE8C1E35A for ; Wed, 30 Oct 2024 12:24:10 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 604FD385829B for ; Wed, 30 Oct 2024 16:24:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 604FD385829B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1730305449; bh=owD6uDsg8+tLiVs+/J7mHJvs1KEYkOoXXOpuK48V9UY=; h=Date:To:Cc:Subject:In-Reply-To:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=KksnOU8P1xPj/FV+Rnicd4vkTmz9vM8+rrXX7P0vRNQxoe3CA+FjziouKdW1oVcxA fd+FrM5rk9OXOOIb8COnHLVtmOojnGxF7eV8W8mhn4SqxJTRxHLNQKvD7Fld+Ws2nk 4JSngigc/P2nmToxS1HGoE9rdFYxAuZmy2iOiTiY= Received: from pine.sfconservancy.org (pine.sfconservancy.org [192.237.253.17]) by sourceware.org (Postfix) with ESMTPS id A5CB23858D28; Wed, 30 Oct 2024 16:23:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org A5CB23858D28 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org A5CB23858D28 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1730305387; cv=none; b=YfRy6UTeSKyi3AUNLc19Yr2DllFy4yxQch8trTHrmmdSOm3SFJklo9a+Laxm6sC7L27N6/ZeFmvWb+QwCPbbnRKOJGtqrxne2xD4jkKN06zIMbmVTM4zpX4wtD1BIS8DmQVvJymoHORvIIvUyPJz3m6IgU7Z0SvibDG9jfjw7vc= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1730305387; c=relaxed/simple; bh=RDmljZfe5nBAfF6x/hhBtiiTrlhRIMUn5NPsPgbwmro=; h=DKIM-Signature:MIME-Version:Date:From:To:Subject:Message-ID; b=UmS2l30nuQ9IoWVcHEoiTQ5v6gy+szk/jU9Hths5hLD6DjLzfa21zXQFERYyoiuADSJzOvtMu815vJABBoy9dFWX4SBw4+5RehVNE48INogRruwM268LBZUL5cyMWLj1bYYGXu5U5obFeAYqQ79/NePYbhOX7AHiJDyveOGJB0Q= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from mail.sfconservancy.org (unknown [192.237.253.17]) (Authenticated sender: karen) by pine.sfconservancy.org (Postfix) with ESMTPSA id 9FBF1E709; Wed, 30 Oct 2024 16:23:00 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 30 Oct 2024 12:23:00 -0400 To: Mark Wielaard Cc: Carlos O'Donell , gcc developers , glibc developers , gdb developers , binutils developers , Overseers mailing list , cti-tac@lists.linuxfoundation.org, =?UTF-8?Q?Zo=C3=AB_Kooyman?= Subject: Re: Core Toolchain Infrastructure - October 2024 update In-Reply-To: References: <9ee5b9e1-3f84-4d9e-8249-7a4bf8080bb0@redhat.com> <20241030103912.GD28606@gnu.wildebeest.org> <3a2c2d35-3b86-4286-a393-5ec166659f92@redhat.com> Message-ID: <89da0eac930620feb31b97083714e858@sfconservancy.org> X-Sender: karen@sfconservancy.org User-Agent: Roundcube Webmail/1.2.3 X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Karen M. Sandler via Gdb" Reply-To: "Karen M. Sandler" Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" On 2024-10-30 11:45, Mark Wielaard wrote: > Hi Carlos, > > On Wed, 2024-10-30 at 08:32 -0400, Carlos O'Donell wrote: >> I can get down to specific requirements and possible solutions for >> them, including >> things like securing logins with 2FA etc. Which *could* be solved by >> Sourceware >> today possibly using Nitrokeys (open hardware and FOSS), for example. > > Yes, a nitrokey distribution scheme is part of the Secure Sourceware > Project Goals: https://sourceware.org/sourceware-security-vision.html > > We discussed this with OpenSSF and submitted a funding request to > OpenSSF Alpha Omega for this particular part. OpenSSF initially was > supportive to funding these kinds of security plans, but they have been > silent for the last couple of months. If you have contacts to get this > going forward again that would be great. > >> Having all the details spelled out would allow Sourceware to make >> progress on the >> same issues raised, and I can even file infrastructure bugs if that >> helps. > > Yes, please file bugzilla reports against the Sourceware Infrastructure > project: > https://sourceware.org/bugzilla/buglist.cgi?product=sourceware&component=Infrastructure > Or bring it up on the overseers list or during the Sourceware open > office hours. https://sourceware.org/mission.html#organization > >> My deepest concerns here is that Sourceware PLC cannot convince larger >> sponsors >> to provide the funding to do what needs to be done to scale out and >> improve our >> services. > > Thanks for your concern. The whole idea of setting up Sourceware as an > organization with Conservancy as a fiscal sponsor is precisely to make > these kind of sponsorships easy. And to expand funding to be able to > accept community donations and grants: > https://sourceware.org/donate.html Yes, SFC is already set up to receive donations from most of the large companies that are consistent funders in this space (we're registered in their vendor systems). Similarly, we regularly have fundraising meetings with them across our member projects. If you have a particular lead or suggestion for Sourceware, please let me/us know and we'll follow up! karen > > >> I'm excited that the GNU Toolchain community is looking at different >> workflows and >> solutions, but if I'm honest the same question of funding and >> service/workload >> isolation applies. >> >> I'm *more* excited to pay Codeberg directly to support the GNU >> Toolchain to support >> the development of Forgejo, particularly given that larger groups like >> Fedora are >> considering Forgejo. > > Yes, we did already discuss this. But it is too early for that. Richard > setup a wiki page for the Forge Experiment that includes a list of > various bugs/issues in Forgejo that we would like to see resolved > before we can call the experiment an success. > https://gcc.gnu.org/wiki/ForgeExperiment > When we are a bit further into the experiment to know which ones are > real blockers, we could fund the work to get those done. > > Cheers, > > Mark