Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org
Cc: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org,
	 libc-alpha@sourceware.org
Subject: Sourceware: Funding the core toolchain infrastructure
Date: Fri, 25 Sep 2026 14:11:07 +0200	[thread overview]
Message-ID: <6f6b79ecac58c7d2fa1c65cb6f65ce418882321b.camel@klomp.org> (raw)

Hi core toolchain and developer tool hackers,

Start of this quarter we launched a Fundraiser for Sourceware:
https://inbox.sourceware.org/20260709005228.GN21398@gnu.wildebeest.org/

This has been an enormous success, with ~$12,000 raised we already got
2/3rd of the budget for individual and corporate donations and
sponsorship for our 2026/2027 financials in just one quarter.
https://sourceware.org/financials.html

This quarter we got ~$2800 through 68 individual donations by 56 people
for an average of ~$40 per donation of which ~$250 are recurring per
month. https://sourceware.org/donate.html

And three more companies joined Red Hat and OSL as Sourceware partners
through the new sponsorship program.
https://sourceware.org/sponsor.html

Open Source Security joined as a Supply Chain Defender.
BayLibre and Suse joined as Infrastructure Supporters.

We like to thank the Software Freedom Conservancy, our fiscal sponsor,
for all their help. So after you make your personal donation to
Sourceware, please go to https://sfconservancy.org/sustainer/ and
become an SFC Sustainer so they can help more project like ours.

Thanks from the Sourceware Project Leadership Committee,

 Frank Ch. Eigler, Ian Kelling, Ian Lance Taylor, Tom Tromey,
 Jon Turney, Mark J. Wielaard and Elena Zannoni

                 reply	other threads:[~2026-09-25 12:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6f6b79ecac58c7d2fa1c65cb6f65ce418882321b.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=overseers@sourceware.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