public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
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: Sourceware looking backward, looking forward, Fri 8, 15:00 UTC
Date: Thu, 7 May 2026 17:18:14 +0200	[thread overview]
Message-ID: <20260507151814.GK1219@gnu.wildebeest.org> (raw)

Hi all,

Lets discuss the previous year and the goals and budget for the
upcoming year. The Sourceware (financial) year runs from/to May 15
which is when we joined the Software Freedom Conservancy as a member
project. https://sfconservancy.org/news/2023/may/15/sourceware-joins-sfc/

Tomorrow is the second Friday of the month, so it is time for the
Sourceware Open Office again. This time one hour earlier so it isn't
yet weekend for those in Europe.

Friday May 8, from 15:00 UTC to 16:00 UTC
At #overseers on irc.libera.chat

$ date -d "Fri May 8 15:00 UTC 2026"

Last year was all about refreshing and expanding our hardware and
servers, moving into bigger datacenters and run all our services in
VMs instead of on bare metal servers.
https://sourceware.org/sourceware-wiki/servers-and-services-2026/

We spend a good chunk of our budget on bigger/faster hardware. But
also raised twice as much (individual) donations as the year before.

This looks pretty good and puts us "ahead of schedule". We predicted we
needed 3 years to raise enough money to refresh our hardware again. But
seem to have done it in one.

So for next year we can probably be a little more ambitious and also
request some more corporate funding and approach some grant makers to
accellerate some of the plans we discussed. There are a couple of
plans that could go a lot faster if we could hire some consultant or a
sysadmin that could execute them.

See also our previous Sourceware Survey results and Budget priority
discussions:
https://inbox.sourceware.org/20260412192052.GA15385@gnu.wildebeest.org

Sourceware relies on cooperation among a broad diversity of core
toolchain and developer tool projects, hackers, organizations,
ideas, and communication styles. The monthly Sourceware Open Office
meetings are one way of coming together as a community and discuss
our shared development infrastructure. For other ways to participate
see https://sourceware.org/mission.html#organization

Keep Sourceware worry-free, friendly and independent by donating
https://sourceware.org/donate.html support our fiscal sponser SFC
https://sfconservancy.org/sustainer and/or support OSUOSL for
hosting Free Software projects https://osuosl.org/donate/

Do you or your company want to sponsor Sourceware plans financially
https://sourceware.org/sourceware-security-vision.html#plans
donate hardware or services then contact us at sponsor@sourceware.org

             reply	other threads:[~2026-05-07 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 15:18 Mark Wielaard [this message]
2026-05-10 22:37 ` Mark Wielaard

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=20260507151814.GK1219@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).