DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 636MXDW62565287
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0C88B4BA2E05
Date: Tue, 7 Apr 2026 00:32:49 +0200
To: cygwin AT cygwin DOT com
Subject: Sourceware infrastructure updates for Q1 2026
Message-ID: <20260406223249.GS7048@gnu.wildebeest.org>
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
From: Mark Wielaard via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Mark Wielaard <mark AT klomp DOT org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

Sourceware infrastructure community updates for Q1 2026

  Keep Sourceware independent, worry-free and friendly, sustain our
  fiscal sponsor https://sfconservancy.org/sustainer support OSUOSL
  to host projects like ours https://osuosl.org/donate or donate
  directly to Sourceware https://sourceware.org/donate.html

Every quarter we provide a summary of news about Sourceware and
roadmap updates https://sourceware.org/sourceware-25-roadmap.html

  - New buildbot CI workers and forge action runners
  - VM-first hardware refresh cycle completed
  - Forge updates
  - Signed-commit census leaderboard
  - Sourceware Organization, Contact and Open Office hours

= New buildbot CI workers and forge action runners

  We worked with the OSUOSL admins to get a new sourceware-builder3
  x86_64 server at OSUOSL 2x28 cores (2x56 threads), 768GB RAM and 2 x
  NVMe M.2 1TB online. It replaces two (smaller) sourceware-builder1
  and sourceware-builder2 servers, which have been turned off now.

  The machine has been partitioned into four VMs:

  - sw3bb1: 40 vcpus, 256GB mem, 500GB disk
  - sw3bb2: 16 vcpus,  96GB mem, 420GB disk
  - sw3runner1: 40 vcpus, 256GB mem, 500GB disk
  - sw3runner2: 16 vcpus,  96GB mem, 420GB disk

  The buildbot worker tasks and containers can be configured through
  the builder project: https://sourceware.org/cgit/builder For
  projects with user branches (like binutils, gdb, libabigail,
  elfutils, valgrind) it can also be used for pre-commit CI with try
  branches: https://sourceware.org/binutils/wiki/Buildbot
  For questions please join the mailinglist:
  https://sourceware.org/mailman/listinfo/buildbot

  The forge workflows can be configured through your projects
  .forgejo/workflows/ actions (you can also enable actions on your
  personal forks). For workflows that need to run on sw3runner1 use
  the sourceware-large-runner label. See also the forge project on
  https://forge.sourceware.org/forge/ or join the mailinglist:
  https://sourceware.org/mailman/listinfo/forge

= VM-first hardware refresh cycle completed

  This quarter the old server2 and server3 joined the new server1 that
  was moved to the new datacenter (RDU3) last quarter. They are also
  setup as VM-first machines (no services running on the bare-metal,
  everything in VMs). The intention is to configure a VM on server2 as
  warm backup for sourceware, periodically copying over the VM lvm
  snapshot. server3 will also be available for random new workloads
  (also VMs). As both server2 and server3 have raid6 setups we have
  pretty good redundancy in case of many-disk failures.

  The next vms would be inbox, patchwork, buildbot, bunsen (and maybe
  cygwin, gitweb/cgit, bugzilla, dwarfstd, valgrind). The limiting
  factor for creating more isolated, but publicly accessible, VMs is
  external IP addresses, we have 8 (which can be freely assigned to
  any VM on any of the 3 servers), but we are already using 4.

  This effort completes our bare-metal to VM-first transition. And
  with the replacement of the OSUOSL build servers (see above) this
  also completes our hardware refresh cycle. For the effort to upgrade
  the Sourceware hardware, services and security isolation the
  Sourceware PLC has been working closely together with the overseers,
  Software Freedom Conservancy, FSF sysadmins, Red Hat IT and OSUOSL
  over the last year.

  And thanks to your generous donations our hardware refresh fund is
  already back up to strenght. So we are able to replace any failing
  server or components (outside of waranty) with new hardware
  immediately. For hardware, hosting and VMs, we should be good for
  the next couple of years now.

= Forge updates

  Besides the new action runners (see above), the forge now also has a
  bigger VM on server1 (vm02), data has been migrated from the
  production server still running on the RH OSPO cloud server (but
  needs a new resync now of course). The new VM should get an ansible
  setup and a hot backup on server3 (48GB mem, 16 cores, 200GB lv).

  There has been work/discussion on how the forge should convert a
  pull request to an email containing all discussions on the forge.
  When should it trigger? What should (and shouldn't) go into the
  email? Claudio has a concrete proposal for which bot workflows would
  need to be implemented and what should happen at what time:
  https://inbox.sourceware.org/c16d2000-a13c-4136-8faf-3c0bb5feb402 AT arm DOT com/

  The Linaro bot does run merge requests through CI and updates
  comments with the current CI state.

  There were also suggestions to also "incoming" emails.
  But that still has to be setup:
  https://forgejo.org/docs/latest/admin/advanced/incoming-email/

= Signed-commit census leaderboard

  How is your project doing on signed commits?
  
analyzing branch HEAD since 2026-01-01
cygwin-calm     28 commits  28 signed 100%   1 committers  1 signers 100%
cygwin-setup    28 commits  28 signed 100%   2 committers  2 signers 100%
profiledb        5 commits   5 signed 100%   1 committers  1 signers 100%
annobin         10 commits   9 signed  90%   2 committers  1 signers  50%
systemtap       16 commits  13 signed  81%   2 committers  2 signers 100%
bunsen          57 commits  46 signed  80%   3 committers  2 signers  66%
elfutils        55 commits  36 signed  65%   4 committers  3 signers  75%
glibc          256 commits  19 signed   7%  24 committers  1 signers   4%
gcc           2008 commits 137 signed   6% 133 committers 11 signers   8%
newlib-cygwin   95 commits   2 signed   2%   7 committers  1 signers  14%
binutils-gdb  1214 commits  20 signed   1%  51 committers  4 signers   7%
valgrind       238 commits   1 signed   0%   7 committers  1 signers  14%
builder          8 commits   0 signed   0%   1 committers  0 signers   0%
debugedit        9 commits   0 signed   0%   1 committers  0 signers   0%
dwz              2 commits   0 signed   0%   1 committers  0 signers   0%
forge            1 commits   0 signed   0%   1 committers  0 signers   0%
insight         22 commits   0 signed   0%   1 committers  0 signers   0%
libabigail       7 commits   0 signed   0%   1 committers  0 signers   0%
lvm2           238 commits   0 signed   0%   8 committers  0 signers   0%

= 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 the fediverse for announcements, notices, downtime or
  temporary network issues 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 service or
  hosting questions.

  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 AT sourceware DOT org

  The PLC https://sourceware.org/mission.html#plc currently 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 AT sourceware DOT org.

  If you rather help with more technical tasks please join the
  overseers list: https://sourceware.org/mailman/listinfo/overseers

Sourceware PLC,

 Frank Ch. Eigler, Ian Kelling, Ian Lance Taylor, Tom Tromey,
 Jon Turney, Mark J. Wielaard and Elena Zannoni

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple