From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org
Subject: Sourceware Infrastructure, email arc, new osuosl hardware, patchworks
Date: Wed, 25 Oct 2023 14:47:16 +0200 [thread overview]
Message-ID: <a1b5efe42b8acdb219743029c2daf6d16c8195d9.camel@klomp.org> (raw)
Hi,
Various small updates. Not news for anybody following the Sourceware
open office hours, tracking #overseers on irc.libera.chat or the
buildbot mailinglist, but good to know people are working on improving
the infrastructure:
- Outgoing sourceware email now includes ARC headers.
https://en.wikipedia.org/wiki/Authenticated_Received_Chain
Feedback on whether this helps email delivery appreciated.
- There have been complaints about overloaded builders.
So OSUOSL have provided us with another arm64 server
that is already used for glibc and gcc buildbot builds.
They will also likely provide us with another bigger
x86_64 server for the buildbot.
Since that brings the total of OSUOSL provided servers
to 5 (snapshots.sourceware.org is also an OSUOSL server)
the Sourceware Project Leadership Committee, with the
help of Conservancy, is looking into having a bit more
formal relation with OSUOSL as our managed server
provider.
- Given we have the resources now we are looking into also
using builder.sourceware.org for pre-commit checking on
patchwork.sourceware.org. And hopefully we can automate
the commit state for all projects.
There has been an increase in interest of becoming
maintainers of various patchwork projects (thanks!)
Please reach out to overseers or patchwork "staff"
if you need maintainer permissions on any project.
In consultation with the GNU Guix hackers that project
has been removed from patchwork.sourceware.org,
since they were no longer using it.
Cheers,
Mark
reply other threads:[~2023-10-25 12:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a1b5efe42b8acdb219743029c2daf6d16c8195d9.camel@klomp.org \
--to=mark@klomp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).