Hi, On Fri, Oct 09, 2026 at 12:16:36AM +0200, Mark Wielaard wrote: > There were talks about the Forge and CI Automation at Cauldron last > weekend: > > The Sourceware Forge Experiment - year 2 and onwards > https://conf.gnu-tools-cauldron.org/prg26/talk/YZQYFQ/ > > Sourceware Infrastructure Organization and Automation > https://conf.gnu-tools-cauldron.org/prg26/talk/SVVBRS/ > > And feedback in the various project BoFs. > > We also got a big donation just before the Cauldron, which makes it > possible to start work on some of the programs at > https://sourceware.org/financials.html
For those that couldn't attend. Some notes on the topics discussed. - Xe released Anubis 1.28.1. Mark to install next week. Also looking into whether "authenticated" users can get an anubis bypass (as requested in the Cauldron Sourceware session). - Forgejo merge request action/bot issue. There seems to be an issue with a merge request getting "disconnected" after which new actions cannot be run against it. Which seems a codeberg bug. Only known "fix" for now is to close the merge request and open a new one. If no open Codeberg bug exists for Forgejo, a new one should be opened. This might, or might not, be the reason the b15a bot isn't showing up. - Reminder that user account requests should go to account-requests@ rather than the public overseers@ mailing list. - Budget Status. Sourceware received another big ($5,000) donation just prior to Cauldron, fully funding the 2026/2027 budget. Slides from Cauldron are available: https://conf.gnu-tools-cauldron.org/media/prg26/submissions/SVVBRS/resources/Sourceware-Cauldron-_7FQ0SPp.pdf (funding & budget are slide 17 & 18). Fund Allocation: - $1,000 – OSUOSL partner support / compensation - $12,000 – Paid staff / consultants for service upgrades and VM migrations (Bugzilla, Public-Inbox, Patchwork, Buildbot) - $3,000 – Upstream Forgejo improvements - $1,500 – Hardware replacement fund - $500 – Operational overhead (domain, banking, expenses) - Discussed requirements for contracting out the upgrade/migration tasks. While Software Freedom Conservancy guidelines generally require an open application process, uniquely qualified candidates who have previously contributed can be selected if formally documented and approved by the PLC. Next steps: PLC to draft work orders and scope for service upgrades (The SFC provided some examples from other member projects.) Claudio, Richard and Mark will coordinate on the specific feature list for upstream Forgejo work (using the GCC wiki forge experiment page bug list as a starting point) - Richard pointed out the the current primary technical hurdle is integrating existing direct push hooks with Forgejo hooks and actions. Flipping the main repository to the forge depends on ensuring direct pushes outside the pull/merge-request workflow continue enforcing commit policies reliably. Mark to investigate converting hooks into Actions as well as integrating them directly into native Forge git hooks. Richard's slides from the Cauldron forge talk will be published soon. There were more topics raised in the various project BoFs and talks, but we ran out of time. To be continued on the mailinglists.
