From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Joseph Myers <joseph@codesourcery.com>,
"Ryan S. Arnold" <ryan.arnold@gmail.com>,
Paul Eggert <eggert@cs.ucla.edu>,
Jakub Jelinek <jakub@redhat.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
Andreas Schwab <schwab@suse.de>, Alexandre Oliva <oliva@gnu.org>
Subject: Re: Sourceware Infrastructure Services for glibc
Date: Wed, 23 Aug 2023 09:57:12 +0200 [thread overview]
Message-ID: <20230823075712.GJ16919@gnu.wildebeest.org> (raw)
In-Reply-To: <87a5ujoyvn.fsf@redhat.com>
Hi Frank,
On Tue, Aug 22, 2023 at 11:53:43AM -0400, Frank Ch. Eigler via Libc-alpha wrote:
>
> > [...] Appended to this message are [...] an enumeration of the
> > current services. [...]
>
> Existing sourceware services for glibc also includes:
>
> - the buildbot server, having run some 12,000 glibc builds since
> inception: https://builder.sourceware.org/buildbot/#/builders
>
> - the bunsen instance accumulating glibc testsuite results, presently
> holding some 5,700 of them:
> https://builder.sourceware.org/testruns/?has_keyvalue_k=testrun.git_describe&has_keyvalue_op=glob&has_keyvalue_v=*glibc*&has_keyvalue2_k=source.gitdescribe&has_keyvalue2_op=glob&has_keyvalue2_v=*&order_by=testrun.authored.time&order=desc&limit=10000&offset=0&offset=0
>
> - the recently added 'snapshots' worker & server:
> https://snapshots.sourceware.org/glibc/trunk/
Thanks for the list. Note that Sourceware Infrastructure Services are
also listed per project at https://sourceware.org/projects.html
For glibc it is currently missing bunsen (would be nice to have short
URLs per project btw) and the fsf-tech team provided services for GNU
projects. Which should probably be added. There is also a generic
services list at https://sourceware.org/mission.html#services
Also note that over the last couple of years we setup a real
Sourceware organization to make sure the Sourceware community can be
sustained for another 25 years:
https://sourceware.org/sourceware-25-roadmap.html
So if there are any services missing or could be improved, please do
reach out to overseers@, file infrastructure bugs or come talk at one
of the open office hours on irc (or really at any time). See
https://sourceware.org/mission.html#organization
Cheers,
Mark
next prev parent reply other threads:[~2023-08-23 7:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 21:58 Core Toolchain Infrastructure - " Carlos O'Donell
2023-07-14 11:38 ` Florian Weimer
2023-07-14 15:34 ` Konstantin Ryabitsev
2023-07-18 11:47 ` Siddhesh Poyarekar
2023-07-18 12:26 ` Jakub Jelinek
2023-07-18 13:19 ` Jeff Law
2023-07-18 13:24 ` Siddhesh Poyarekar
2023-07-20 17:43 ` Joseph Myers
2023-07-18 13:38 ` Konstantin Ryabitsev
2023-08-03 10:10 ` Florian Weimer
2023-07-14 15:58 ` Mark Wielaard
2023-08-22 15:53 ` Frank Ch. Eigler
2023-08-23 7:57 ` Mark Wielaard [this message]
2023-08-29 20:45 ` Carlos O'Donell
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=20230823075712.GJ16919@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=eggert@cs.ucla.edu \
--cc=fche@redhat.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=konstantin@linuxfoundation.org \
--cc=libc-alpha@sourceware.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=oliva@gnu.org \
--cc=ryan.arnold@gmail.com \
--cc=schwab@suse.de \
/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).