From: Mark Wielaard <mark@klomp.org>
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
Date: Sun, 28 Jun 2026 23:59:02 +0200 [thread overview]
Message-ID: <20260628215902.GB12192@gnu.wildebeest.org> (raw)
In-Reply-To: <20260614225910.GA14303@gnu.wildebeest.org>
Hi all,
On Mon, Jun 15, 2026 at 12:59:10AM +0200, Mark Wielaard wrote:
> 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.
> [...]
> 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.
The Sourceware PLC reviewed all feedback and we now have:
- https://sourceware.org/donate.html
The individual donation page. Please donate if you haven't yet.
Every contribution makes a difference.
- https://sourceware.org/sponsor.html
The corporate sponsorship page. With three different tiers.
If your company would like to become a financial sponsor, or become
a resource partner please contact us at sponsor@sourceware.org
- https://sourceware.org/financials.html
Sourceware financials, budget and funding targets for 2026/2027.
Next week, start of next month, we'll start a formal fundraising
campaign.
Cheers,
Mark
prev parent reply other threads:[~2026-06-28 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 10:38 Mark Wielaard
2026-06-14 22:59 ` Mark Wielaard
2026-06-28 21:59 ` Mark Wielaard [this message]
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=20260628215902.GB12192@gnu.wildebeest.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