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 Open Office, Fri 14, 15:00 UTC
Date: Thu, 13 Aug 2026 22:13:26 +0200 [thread overview]
Message-ID: <f0bfd49aed34349af61a7a6d34b048e90a641b22.camel@klomp.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]
Hi all,
Tomorrow is the second Friday of the month, so it is time for the
Sourceware Open Office again.
Friday August 14, from 15:00 UTC to 16:00 UTC
At #overseers on irc.libera.chat and
https://bbb.sfconservancy.org/rooms/sourceware
$ date -d "Fri Aug 14 15:00 UTC 2026"
Discussion topics:
- ai scraper bot mitigation
We have a better setup now, but ai scraper bots keep adapting.
Which layers needs tweaking to give the best performance for users?
- update on Sourceware fundraising
We got more donations and corporations joining the sponsorship
program!
- forge updates
MAINTAINERS.yml to forge user sync.
Secrets management for production instance.
What should we prioritize before cauldron?
- the FSF asked us to put our heads together to improve glibc services
https://inbox.sourceware.org/7021a9fb-2476-463c-8eab-a4e254d93df2@fsf.org/
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-08-13 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 20:13 Mark Wielaard [this message]
2026-08-16 21:00 ` Mark Wielaard
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=f0bfd49aed34349af61a7a6d34b048e90a641b22.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