Sourceware infrastructure community updates for Q4 2024 Sourceware has provided the infrastructure for core toolchain and developer tools projects for more than 25 years. https://sourceware.org/sourceware-25-roadmap.html
The last couple of years it has transformed from a purely volunteer into a professional organization with an eight person strong Project Leadership Committee, monthly open office hours, multiple hardware services partners, expanded services, the Software Freedom Conservancy as fiscal sponsor and a more diverse funding model that allows us to enter into contracts with paid contractors or staff when appropriate. Every quarter we provide a summary of news about Sourceware, the core toolchain and developer tools infrastructure, from the last 3 months. - Donations and Software Freedom Conservancy match fundraiser - Sourceware Cyber Security FAQ - New incoming email dmarc p=reject policy - Sourceware forge experiment - Signed-commit census report - Sourceware Organization, Contact and Open Office hours = Donations and Software Freedom Conservancy match fundraiser We like to thank all the individuals who donated this year and helped us create a hardware backup fund in case one of our hardware sponsors has to drop out. https://sourceware.org/donate.html But various hardware and service partners have actually offered more resources this year. So we haven't needed to spend much money this year. And could still expand the buildbot CI, snapshot server and run the Forge experiment. https://sourceware.org/mission.html#sponsors Currently the best way to support Sourceware is to join the Software Freedom Conservancy match fundraiser: https://sfconservancy.org/news/2024/nov/26/2024-fundraiser/ By becoming a Software Freedom Conservancy Sustainer the Conservancy can keep supporting Sourceware and other Software Freedom communities https://sfconservancy.org/sustainer/ = Sourceware Cyber Security FAQ After lots of discussions at some of our Open Office hours, at the Cauldron, with other Software Freedom organizations and some of our hardware and services providers we created an Sourceware Cyber Security FAQ "explainer" about topics like the "US Improving the Nation's Cybersecurity Executive Order 14028", "EU Cyber Resilience Act (EU CRA)" and "Secure Software Development Framework (NIST SP 800-218)" or who is required to use Zero Trust (NIST SP 800-207) cloud-computing environments. https://sourceware.org/cyber-security-faq.html Somewhat related the Software Freedom Conservancy published a blog post about the recent bans of Russian contributors in the Linux project and whether Free Software projects need to worry about U.S. Sanctions. https://sfconservancy.org/blog/2024/dec/12/linux-banned-russian-contributors-do-i-need-to/ = New incoming email dmarc p=reject policy We are now rejecting any incoming emails that fail dmarc for domains that have a p=reject policy. Because if we forward such emails through mailinglists (without From rewriting) they will cause bounces for some subscribers (eventually causing those subscribers to be unsubscribed). https://sourceware.org/bugzilla/show_bug.cgi?id=32255 https://inbox.sourceware.org/e137cda184f7c54a91bb3966c1d067c92095eda6.ca...@klomp.org/ = Sourceware forge experiment https://forge.sourceware.org As an experiment Sourceware is now running an Forgejo v9 instance. The full setup can be found in this git repository: https://sourceware.org/cgit/forge/ For now it is only open for existing maintainers/developers for experimenting with a pull-request model. There is also a new mailinglist for discussion about the setup and the best way to create a pull-request workflow: https://sourceware.org/mailman/listinfo/forge And a wiki with more background information: https://gcc.gnu.org/wiki/ForgeExperiment = Signed-commit census report Analyzing branch HEAD since 2024-01-01 annobin 85 commits 16 signed 18% 1 committers 1 signers 100% binutils-gdb 3433 commits 74 signed 2% 99 committers 3 signers 3% builder 141 commits 19 signed 13% 3 committers 1 signers 33% bunsen 163 commits 102 signed 62% 4 committers 3 signers 75% bzip2 1 commits 0 signed 0% 1 committers 0 signers 0% cgen 1 commits 0 signed 0% 1 committers 0 signers 0% cygwin-calm 68 commits 68 signed 100% 1 committers 1 signers 100% cygwin-setup 50 commits 49 signed 98% 3 committers 2 signers 66% debugedit 22 commits 1 signed 4% 2 committers 1 signers 50% dwz 2 commits 0 signed 0% 1 committers 0 signers 0% elfutils 161 commits 21 signed 13% 4 committers 2 signers 50% forge 7 commits 0 signed 0% 1 committers 0 signers 0% gcc 9654 commits 721 signed 7% 216 committers 14 signers 6% gitsigur 9 commits 9 signed 100% 1 committers 1 signers 100% glibc 1147 commits 82 signed 7% 39 committers 3 signers 7% insight 54 commits 0 signed 0% 1 committers 0 signers 0% libabigail 185 commits 1 signed 0% 2 committers 1 signers 50% lvm2 833 commits 42 signed 5% 8 committers 1 signers 12% newlib-cygwin 376 commits 16 signed 4% 12 committers 1 signers 8% systemtap 155 commits 87 signed 56% 5 committers 3 signers 60% valgrind 448 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 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 Sourceware PLC, Frank Ch. Eigler, Christopher Faylor, Ian Kelling, Ian Lance Taylor, Tom Tromey, Jon Turney, Mark J. Wielaard, Elena Zannoni
