Hi all, On Thu, Oct 09, 2025 at 11:47:34AM +0200, Mark Wielaard wrote: > For those recovered from Cauldron and for those that missed Cauldron > and want to know about the new and exciting infrastructure ideas! > > Friday Oct 10, 16:00 UTC > At #overseers on irc.libera.chat
For those who couldn't attend here is a summary of things discussed: - The Cauldron videos are now on youtube and mirrors like: https://inv.nadeko.net/playlist?list=PL_GiHdX17WtxuKn7QYme8EfbBS-RKSn0w But we are still looking at where to store the originals. server1.sourceware.org (see below) in the new RDU3 datacenter will have 14TB RAID6 SSD storage, but isn't really setup as media server (and if we will, then storage will quickly run out). Asked the FSF about using their peertube setup or media.libreplanet.org for Cauldron video storage. They are looking into it: "With PeerTube, we are running out of space there so you should make your own PeerTube account. Still figuring out if we can handle it on our MediaGoblin instance." Best suggestion for now is archive.org. Anyone can upload content to archive.org, even relatively bulky stuff, no contact needed, just an archive.org account. - server1.sourceware.org is finally coming online in the new datacenter. For now no public internet access yet. But the good news is that we will be able to get public ip addresses for all VMs we setup. Which will make the setup and moving services into separate VMs easier. The old servers will be moved between Dec 2 and Dec 8. So it would be good to migrate all services to the new box before that. If we cannot make that then the next deadline would Feb 6 2026. - patchwork.sourceware.org, builder.sourceware.org and inbox.sourceware.org can probably be setup as their own VM from the start. - First VM will probably be for forge staging so we can have upgrade testing (and hopefully test a full ansible setup). - forge.sourceware.org (currently a separate VM in the old datacenter) will be updated to Forgejo 13 and Debian 13 on Thu 16 October (this already happened). - Claudio and Frank found thousands of (empty) spam wiki pages and removed them. This makes some "magic" pages work again, like: https://gcc.gnu.org/wiki/OrphanedPages https://sourceware.org/glibc/wiki/WantedPages - Our mailman2 setup is currently a bit of a blocker to untangle more services and upgrading the underlying OS (since it needs python2 support). One option is to keeping its status quo, as in colocating with a main "server2.sourceware.org" vm, at least initially. That way the disentanglement can be delayed. Another option is to look into using a Python 3 version of Mailman 2 https://github.com/jaredmauch/mailman2-python3 or https://github.com/cpanel/mailman2-python3 We could also run the current mailman2 setup inside a RHEL8 container. - Arsen's gcc documentation work would also helps to not have to install all the extra documentation generation tooling. - Please look at and update https://sourceware.org/sourceware-wiki/Migration2025/ - We (reluctantly) made it possible to enable Issues, Wikis and Projects (kanban boards) for forge repos. We don't really want to have to support those, but for new projects it might be interesting to try them out. > 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 [email protected]
