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 Survey results and Budget priority discussions
Date: Thu, 9 Apr 2026 16:18:49 +0200 [thread overview]
Message-ID: <20260409141849.GD7048@gnu.wildebeest.org> (raw)
Hi all,
The results of the Sourceware Survey 2026 are in!
https://sourceware.org/survey-2026
And since tomorrow is the second Friday of the month it is also
Sourceware Open Office time!
Friday April 10, from 16:00 UTC to 17:00 UTC
At #overseers on irc.libera.chat
$ date -d "Fri Apr 10 16:00 UTC 2026"
Come and lets discuss the Survey results and see what they mean for
our Budget priorities this year.
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
next reply other threads:[~2026-04-09 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 14:18 Mark Wielaard [this message]
2026-04-12 19:20 ` 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=20260409141849.GD7048@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).