public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: libc-alpha <libc-alpha@sourceware.org>
Cc: 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>
Subject: Re: Core Toolchain Infrastructure - Services for glibc
Date: Fri, 14 Jul 2023 17:58:17 +0200	[thread overview]
Message-ID: <1d46484c1fe9c5c57bee8fbdd78952ca5846ad43.camel@klomp.org> (raw)
In-Reply-To: <45e98807-908f-0968-b6fe-5dbb0af265b1@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]

Hi Carlos,

On Thu, 2023-07-13 at 17:58 -0400, Carlos O'Donell via Libc-alpha
wrote:
> As part of this effort the Technical Advisory Committee (TAC) has
> evaluated the services used by glibc and how they could be migrated
> and serviced by the CTI project.
> 
> The CTI TAC recommendation is to use Linux Foundation IT services
> for core infrastructure. The LF IT team already supports many of
> the same services for the Linux kernel and at scale. The migration
> would involve moving services from Sourceware.org to LF IT servers.
> We continue to be thankful and appreciative of the time spent by
> Sourceware.org volunteers in support of the current services.

Your goals seem to align with those of Sourceware and the expanded
services we have been setting up over the last couple of years
together. So hopefully you don't have to leave the community.
https://sourceware.org/mission.html

A couple of months ago we finalized the incorporation of Sourceware as
a Software Freedom Conservancy member project with eight community
members serving as Project Leadership Committee:
https://sfconservancy.org/news/2023/may/15/sourceware-joins-sfc/

If the community needs any help with any of the Sourceware services
please join one of the Open Office talks (there is one today, at 18:00
UTC, in #overseers on irc.libera.chat) or contact us through the
overseers mailinglist, bugzilla, etc at any time. See attached.

Cheers,

Mark

[-- Attachment #2: Attached message - Sourceware Open Office, Friday July 14, 18:00 UTC --]
[-- Type: message/rfc822, Size: 6201 bytes --]

From: Mark Wielaard via Overseers <overseers@sourceware.org>
To: overseers@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: Sourceware Open Office, Friday July 14, 18:00 UTC
Date: Fri, 14 Jul 2023 02:11:34 +0200
Message-ID: <20230714001134.GA29669@gnu.wildebeest.org>

Every second Friday of the month is the Sourceware Overseers Open
Office hour in #overseers on irc.libera.chat from 18:00 till 19:00
UTC. That is this Friday July 14th.

Please feel free to drop by with any Sourceware hosting questions.
Help with email (archives, spam), secure supply chain, setting up new
buildbot CI, producing snapshots, helping write up some POCs,
discussing extending services, what the Software Freedom Sourceware
Project Leadership Committee should prioritize, or just to say things
are all working fine.

Of course you are welcome to drop into the #overseers channel at any
time and we can also be reached through email and bugzilla:
https://sourceware.org/mission.html#organization

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

We are also on the fediverse these days:
https://fosstodon.org/@sourceware

  parent reply	other threads:[~2023-07-14 15:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 21:58 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 [this message]
2023-08-22 15:53 ` Frank Ch. Eigler
2023-08-23  7:57   ` Sourceware Infrastructure " Mark Wielaard
2023-08-29 20:45   ` Core Toolchain Infrastructure - " 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=1d46484c1fe9c5c57bee8fbdd78952ca5846ad43.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=eggert@cs.ucla.edu \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=libc-alpha@sourceware.org \
    --cc=maxim.kuvyrkov@linaro.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).