Hi,

At the toolchain meeting last Thursday we discussed the use of the
forge. We made some nice progress getting the batrachomyomachia bot
deployed and added various actions (pre-commit checks) and also
discussed some things people feel are still missing [1].

One issue with the forge was that you already needed to have an
Sourceware account. This has been fixed. Anybody can register an
account on the forge now. But a newly registered user will have to be
added to the Contributors Team by an Owner or Admin of the org or repo
before they can see, fork, create merge requests and run actions.

In the next two weeks the forge will move to a larger VM with more
cores, memory and disk space. And in the new year OSUOSL will replace
our two smaller x86_64 container builders sourceware-builder1 and
sourceware-builder2 machines with a larger sourceware-builder3 (2x28
core, 112 thread, 768GB RAM) machine which will be used for buildbot
builders and forgejo action runners to make it possible to do full
bootrap checks.

In general 2025 has been a good year for Sourceware infrastructure.
Thanks to your generous donations [1] the Sourceware Project
Leadership Committee [2] was able to add a larger server as part of
the 2025 migration [3] last month. The new VM-first setup was a great
step forward for our security isolation story [4].

  The Software Freedom Conservancy, our fiscal sponsor, is holding a
  fundraiser match challenge. To keep Sourceware worry-free, friendly
  and independent the best things you can do is become a sustainer:

      https://sfconservancy.org/sustainer/

  See under "Highlights From Our Member Projects" how SFC has helped
  Sourceware (and many other project) this last year:

      https://sfconservancy.org/sustainer/#YearInReview

Looking forward to more progress next year!

Mark

[1] https://gcc.gnu.org/wiki/OfficeHours#Meeting:_2025-12-18_.40_1100h_EST5EDT
[2] https://sourceware.org/donate.html
[3] https://sourceware.org/mission.html#plc
[4] https://sourceware.org/sourceware-wiki/Migration2025/
[5] https://sourceware.org/sourceware-security-vision.html

Reply via email to