From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org
Subject: Sourceware infrastructure updates for Q2 2025
Date: Wed, 30 Jul 2025 02:28:09 +0200 [thread overview]
Message-ID: <20250730002809.GG4685@gnu.wildebeest.org> (raw)
Sourceware infrastructure community updates for Q2 2025
Sourceware has provided the infrastructure for core toolchain
and developer tools projects for more than 25 years.
https://sourceware.org/sourceware-25-roadmap.html
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/
Every quarter we provide a summary of news about Sourceware
infrastructure:
- Sourceware @ Conservancy Year Two
- Anubis for more services, now without javascript challenge
- Sourceware servers on the move
- Red Hat Community Cage server move
- OSUOSL datacenter move
- The Road to Porto: Cauldron in September
- Thanks Christopher Faylor (cgf)
- Signed-commit leaderboard
- Sourceware Organization, Contact and Open Office hours
= Sourceware @ Conservancy Year Two
In May we celebrated that Sourceware got a financial and
administrative home at the Software Freedom Conservancy two years
ago https://sfconservancy.org/news/2023/may/15/sourceware-joins-sfc/
Conservancy has helped us turn from a purely volunteer into a
professional organization with an Project Leadership Committee,
monthly open office hours, multiple hardware services partners,
expanded services, and a more diverse funding model that allows us
to enter into contracts with paid contractors or staff if necessary.
Read all about the last year communications, user survey, the new
services, cyber security and regulations, new and upgraded hardware,
and our finances:
https://inbox.sourceware.org/20250527023158.GA11631@gnu.wildebeest.org
= Anubis for more services, now without javascript challenge
What started as an experiment for patchwork and bunsen has now been
rolled out to most other services, cgit, gitweb, bugzilla, wikis and
the forge.
The latest version of Anubis contains a non-javascript challenge
which has been used for bugzilla as an experiment and seems as
effective as the javascript challenge. So it has now been rolled out
to all services.
= Sourceware servers on the move
All our servers will be moving later this year because both our
hardware services partners will move datacenters. The Sourceware PLC
decided to take advantage of this move by adding more/bigger
machines.
- Red Hat Community Cage server move
This https://www.osci.io/tenants/ impacts server2 (main server),
server3 (backup server) and forge.sourceware.org. We will add a new
bigger server which has 3x memory [24x64GB], 10x storage [6x3.84TB],
2x cpu ish [2x28 cores] compared to the current servers. The new
data center also has a a faster/bigger network pipe.
The new server1 was made possible thanks to the FUTO grant,
individual Sourceware donations and Red Hat OSPO CommInfra & IT
teams. It has already been installed in the new RDU3 data
center. But doesn't have network yet (will be added in two weeks).
We like to have the new server1 setup and in production before the
move of the other two servers so there is a minimum of downtime. We
discussed a plan to do this and how we can use this for moving some
services in their own isolated VMs, and which resources need to be
untangled for that at the last Open Office hour.
https://sourceware.org/sourceware-wiki/Migration2025/
- OSUOSL datacenter move
This https://osuosl.org/communities/ impacts sourceware-builder1,
sourceware-builder2, arm64-1, arm64-2 and the snapshots server. The
OSL might be able to upgrade the first two CI x86_64 builders which
would be great since we expect the experimental forge to also want
to add CI for merge requests. But they would like us to cover some
of the co-location hosting costs if possible.
= The Road to Porto: Cauldron in September
The next GNU Tools Cauldron, taking place in Porto, Portugal, on
September 26-28, 2025.
https://inbox.sourceware.org/87o6ubhn4j.fsf@oracle.com/
https://gcc.gnu.org/wiki/cauldron2025
https://gnu-tools-cauldron.org/
Various Sourceware Project Leadership Committee members will be
there to discuss various infrastructure projects and experiments.
= Signed-commit census leaderboard
How is your project doing on signed commits?
Analyzing branch HEAD since 2025-01-01
cygwin-calm 32 commits 32 signed 100% 1 committers 1 signers 100%
cygwin-setup 11 commits 11 signed 100% 1 committers 1 signers 100%
gitsigur 5 commits 5 signed 100% 1 committers 1 signers 100%
bunsen 163 commits 136 signed 83% 2 committers 2 signers 100%
annobin 48 commits 39 signed 81% 2 committers 1 signers 50%
systemtap 67 commits 50 signed 74% 4 committers 3 signers 75%
builder 58 commits 18 signed 31% 4 committers 3 signers 75%
elfutils 102 commits 14 signed 13% 4 committers 2 signers 50%
lvm2 428 commits 41 signed 9% 7 committers 1 signers 14%
glibc 741 commits 74 signed 9% 33 committers 2 signers 6%
gcc 5659 commits 447 signed 7% 152 committers 10 signers 6%
debugedit 15 commits 1 signed 6% 2 committers 1 signers 50%
newlib-cygwin 416 commits 26 signed 6% 14 committers 2 signers 14%
binutils-gdb 2244 commits 80 signed 3% 79 committers 5 signers 6%
libabigail 81 commits 2 signed 2% 2 committers 1 signers 50%
bzip2 2 commits 0 signed 0% 1 committers 0 signers 0%
dwz 9 commits 0 signed 0% 2 committers 0 signers 0%
insight 54 commits 0 signed 0% 1 committers 0 signers 0%
forge 12 commits 0 signed 0% 1 committers 0 signers 0%
valgrind 332 commits 0 signed 0% 6 committers 0 signers 0%
= Thanks Christopher Faylor (cgf)
Since 1999 Christopher Faylor has been one of the Cygwin project
leads for 15 years. He was list maintainer for cygwin, sourceware
and gcc mailinglists for 20 years. And handled spam almost daily so
we could have open lists. He was one of the founding members of the
Sourceware Project Leadership Committee (PLC). Sourceware wouldn't
be what it is today without him.
But after 25 years of being involved with Sourceware and 2 years
serving on the PLC he decided to resign. We thank him for all he did
and all his insights making Sourceware a worry-free, friendly home
for core toolchain and developer tools projects.
The PLC https://sourceware.org/mission.html#plc now consists of 7
members. The mandatory minimum number of Members is 4. And no more
than 2 Members may be Financially-Related to the same Entity.
If you are interested in joining the PLC please read the
https://sourceware.org/Conservancy-Sourceware-FSA.pdf
Fiscal Sponsorship Agreement, the Conflict of Interest Policy
https://sfconservancy.org/projects/policies/conflict-of-interest-policy.html
and contact us at plc@sourceware.org.
If you rather help with more technical tasks please join the
overseers list: https://sourceware.org/mailman/listinfo/overseers
= Sourceware Organization, Contact and Open Office hours
We can be reached through irc, email and bugzilla
https://sourceware.org/mission.html#organization
There is also a fediverse account for for announcements, notices
about downtime and temporary issues with our network.
https://fosstodon.org/@sourceware
Every second Friday of the month is the Sourceware Overseers Open
Office hour in #overseers on irc.libera.chat from 16:00 till 17:00
UTC. Please feel free to drop by with any Sourceware services and
hosting questions.
If you aren't already and want to keep up to date on Sourceware
infrastructure services then please also subscribe to the overseers
mailinglist https://sourceware.org/mailman/listinfo/overseers
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
Sourceware PLC,
Frank Ch. Eigler, Ian Kelling, Ian Lance Taylor, Tom Tromey,
Jon Turney, Mark J. Wielaard and Elena Zannoni
next reply other threads:[~2025-07-30 0:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 0:28 Mark Wielaard [this message]
[not found] <20250730003509.GQ4685@gnu.wildebeest.org>
2025-07-30 13:35 ` Carlos O'Donell
2025-07-30 21:43 ` Mark Wielaard
2025-08-19 11:25 ` Carlos O'Donell
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=20250730002809.GG4685@gnu.wildebeest.org \
--to=mark@klomp.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).