From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org
Cc: gcc@gcc.gnu.org, libc-alpha@sourceware.org,
binutils@sourceware.org, gdb@sourceware.org
Subject: Sourceware - Building Together, Fri 11, 15:00 UTC
Date: Thu, 10 Sep 2026 13:58:41 +0200 [thread overview]
Message-ID: <8bf28f40d7dad5169cdd0b222f38ec903a718d90.camel@klomp.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2520 bytes --]
Hi all,
Tomorrow is the second Friday of the month, so it is time for the
Sourceware Open Office again!
Friday September 11, from 15:00 UTC to 16:00 UTC
On #overseers on irc.libera.chat
$ date -d "Fri Sep 10 15:00 UTC 2026"
Discussion topics about various CI builder buildbots/patchwork/etc:
- Rainer would like to extend the Solaris (amd64 and sparcv9)
buildbot workers to gdb
https://inbox.sourceware.org/ydd4iglf9yj.fsf@CeBiTec.Uni-Bielefeld.DE
- DJ would like to run the patchwork CI/CD curator in a Sourceware VM
https://sourceware.org/glibc/wiki/CICDDesign
https://gitlab.com/djdelorie/glibc-cicd
This is also a good opportunity to discuss putting patchwork as a
whole in its own isolated VM. And to see if we can use some of the
builder servers/VM to use the curator to do CI builds.
https://sourceware.org/sourceware-wiki/servers-and-services-2026/
- Should we look into bugspray? A public-inbox bugzilla integrator:
https://git.kernel.org/pub/scm/utils/bugspray
- An update on funding https://sourceware.org/financials.html
- Builders/CI talk at Cauldron with tips and tricks for having all
our automated processes (buildbots, try-bots, pre/post-commit-CI/CD,
snapshots, forgejo runners, patchwork's curator, etc.) working smoothly,
even in the face of the AI scraperbot attacks, and how to add your own.
https://conf.gnu-tools-cauldron.org/prg26/talk/review/YZDVBNFDPSSZERNAYRYDCS8XWF3BURZC
The FSF (GNU Toolchain projects fiscal sponsor) and SFC
(Sourceware fiscal sponsor) will also attend to answer any
questions on how we are running the community infrastructure
together with our other partners.
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 financially, donate
hardware or services, then see the Sourceware sponsorship program at
https://sourceware.org/sponsor.html
[-- Attachment #2: so.ics --]
[-- Type: text/calendar, Size: 244 bytes --]
BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
BEGIN:VEVENT
DTSTART:20260612T150000Z
DURATION:PT1H
SUMMARY:Sourceware Open Office
LOCATION:#overseers on irc.libera.chat
RRULE:FREQ=MONTHLY;INTERVAL=1;BYDAY=FR;BYSETPOS=2
END:VEVENT
END:VCALENDAR
next reply other threads:[~2026-09-10 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 11:58 Mark Wielaard [this message]
2026-09-10 21:45 ` Zack Weinberg via Gdb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8bf28f40d7dad5169cdd0b222f38ec903a718d90.camel@klomp.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox