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 Open Office, Happy New Year, Fri 16:00 UTC
Date: Fri, 9 Jan 2026 00:35:45 +0100 [thread overview]
Message-ID: <20260108233545.GK20684@gnu.wildebeest.org> (raw)
Happy New Year!
We would like to invite you to the first Sourceware Open Office of 2026
Friday Jan 9, from 16:00 to 17:00 UTC
At #overseers on irc.libera.chat
$ date -d "Fri Jan 9 16:00 UTC 2026"
2025 has been a good year for Sourceware infrastructure. Thanks to
some generous donations we got a larger server, which has been
installed into a new datacenter with a VM-first setup which has been a
great step forward for our security isolation story.
Come and discuss the next steps in 2026. Putting more services into
their own dedicated VMs. Getting server2 and server3 into the new
datacenter (early February). And decide how we are going to use the
other new OSUOSL sourceware-builder3 (2x28 core, 112 thread, 768GB
RAM) server for buildbot builders and forgejo action runners.
https://sourceware.org/sourceware-wiki/Migration2025/
https://sourceware.org/sourceware-wiki/OpenHouse2025/
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-01-08 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 23:35 Mark Wielaard [this message]
2026-01-11 23:11 ` 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=20260108233545.GK20684@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