From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id OemlKWIyL2rrRAcAWB0awg (envelope-from ) for ; Sun, 14 Jun 2026 18:59:46 -0400 Received: by simark.ca (Postfix, from userid 112) id A6D0E1E098; Sun, 14 Jun 2026 18:59:46 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.3 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED autolearn=unavailable autolearn_force=no version=4.0.1 Received: from vm01.sourceware.org (vm01.sourceware.org [IPv6:2620:52:6:3111::32]) (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 C34161E070 for ; Sun, 14 Jun 2026 18:59:45 -0400 (EDT) Received: from vm01.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id CBB8C4BB8F68 for ; Sun, 14 Jun 2026 22:59:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CBB8C4BB8F68 Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id AA7934BB58AC; Sun, 14 Jun 2026 22:59:11 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org AA7934BB58AC Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org ARC-Filter: OpenARC Filter v1.0.0 sourceware.org AA7934BB58AC Authentication-Results: sourceware.org; arc=none smtp.remote-ip=45.83.234.184 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1781477951; cv=none; b=JCLeL9WOUIMshEx/D1BIwYHWoKK2yiA8B7E5xlo/AaT87cSvVJAkpzTc5DshQ+YoV64IfCGr7bfAWpCBfvhdBgMqTEIcW4EBFUD6L9W0woEF65KjrLi12rhqZjewinOgbDSyFmtgrPiR9nVVli5ZJTvDXlZq8qtM8AVtSeNIl3s= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1781477951; c=relaxed/simple; bh=ICs50ibpoa9ltbXRduToJ7eczUN5YCQcmjPzvK0STw8=; h=Date:From:To:Subject:Message-ID:MIME-Version; b=Js2zgT6y9pOdDAcJzjPBgfktNrqDued71HN77soG6jS+2W7TyjoEsXXMZEi+HdOiovzFOkjHG3K+r9d88NH5/qT5fYY8cx+5WsSWK04IFPaEpt+V0Ihfr0mJQ5R1K3fYotdK/fv2FQVVRulKhR/1B3Q2zgT7K9h5RiS2SU3rIfE= ARC-Authentication-Results: i=1; sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AA7934BB58AC Received: by gnu.wildebeest.org (Postfix, from userid 1000) id 8839B32D7E62; Mon, 15 Jun 2026 00:59:10 +0200 (CEST) Date: Mon, 15 Jun 2026 00:59:10 +0200 From: Mark Wielaard To: overseers@sourceware.org Cc: gcc@gcc.gnu.org, libc-alpha@sourceware.org, binutils@sourceware.org, gdb@sourceware.org Subject: Re: Sourceware budget and funding 2026/2027, Fri 12, 15:00 UTC Message-ID: <20260614225910.GA14303@gnu.wildebeest.org> References: <20260611103835.GH14081@gnu.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260611103835.GH14081@gnu.wildebeest.org> User-Agent: Mutt/1.5.21 (2010-09-15) 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: , Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" Hi all, On Thu, Jun 11, 2026 at 12:38:35PM +0200, Mark Wielaard wrote: > Based on last months budget discussions and last years financial > overview the Sourceware Project Leadership Committee wrote up an > ambitious budget and funding proposal for 2026/2027, see below. Lets > discuss if this matches community expectations and what the most > effective way is to drive this fundraising campaign. For those that couldn't attend here is a summary. It looked liked emails with lots of dollar signs and asking for money go into spam filters, so not everybody had seen the Sourceware PLC financials overview. It is also here now: https://sourceware.org/financials.html The PLC document is based on the financials from 2025/2026 and the looking forward/looking backward discussions last month: https://inbox.sourceware.org/20260516203206.GR1219@gnu.wildebeest.org/ https://inbox.sourceware.org/20260510223754.GR1219@gnu.wildebeest.org/ Switching from metal to people is a good funding goal. Especially dodging RAM prices right now :) There were some worries that there aren't enough "tasks" listed for corporations to fund explicitly. But ideally sponsorships are not targetted, they are general funding for the project (to make managing the money better and easier for the project). But if there was specific contract work that would be relevant for companies, we could consider that separately. We currently have items listed per funding "source" and only list the tasks we believe we can do this year. But it would be good to list all the work we want to get done (over multiple years). We do list more under https://sourceware.org/sourceware-security-vision.html#plans Modernizing account processes, Release upload process improvements, Hardware keys, Security audit. It might be useful to just list them all. Question about spelling out the financial assumptions. For those forgejo additions we assume $60/hour (total budget for a week work), for upgrade/migration/automation tickets, we assume $80/hour (total budget 3 to 6 days of work), for the junior sysadmin (at the end) we assume $40/hour (total budget for 2.5 days for 6 to 12 months). Many of the SFC contractors are around $40/hour, we have to do special approvals if it's over $100/hour. People in north america/australia are often about $75/hour. It is normal for people to charge much lower rates for nonprofits. We might want to consider corporate sponsorship "levels". the Reproducible Builds team (who is another SFC project) uses that. https://reproducible-builds.org/donate/#benefits-of-sponsorship https://reproducible-builds.org/who/sponsors/ Then a corporation would fund for a specific "level" and not for a specific task/contract. In general people seem to agree you have to start somewhere and the current estimates are OK, but on the low end. We can be even more ambitious, ask for more than what we currently believe we can spend in a year and see if some individuals, corporatations or grant maker surprises us. We currently have a healthy reserve. We could operate for one or two years without any additional income. And for our minimal baseline we just depend on individual sponsors and some corporate in-kind (hosting) support. What is next? - Create a new sponsors page that lists incentives, levels and "bonus" targets. - Link it all together with the financials and donate pages. - Find Sourceware Ambassadors to drive the fundraising campaign.