public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Mark Wielaard <mark@klomp.org>,
	Overseers mailing list <overseers@sourceware.org>
Cc: gdb@sourceware.org, libc-alpha@sourceware.org,
	binutils@sourceware.org, gcc@gcc.gnu.org
Subject: Re: The GNU Toolchain Infrastructure Project
Date: Tue, 11 Oct 2022 09:24:02 -0400	[thread overview]
Message-ID: <684fc3a1-f48b-8a7b-6b1b-992f44118220@gotplt.org> (raw)
In-Reply-To: <517db8de93ece0eb81923fd05a731ca1da65e1dd.camel@klomp.org>

On 2022-10-07 04:57, Mark Wielaard wrote:
> Given that they were private I can only talk for myself:
> https://inbox.sourceware.org/overseers/Yz9dZWC9QIv+r4LH@elastic.org/T/#m22a52506bc116dbcb10c8cbfa8ed89510f4dc1b7

I believe one of your concerns (alternatives for proprietary 
videoconferencing and list management for TAC) was acknowledged before 
you raised it in that email and is being worked on.

As for the rest, it really is a question on whether all of sourceware 
will in the end be migrated over to LF, it's for the remaining projects 
to decide.  If we indeed have all projects on board then I agree, 
perhaps we then need to ask Red Hat to hand sourceware over to the LF 
and call the project "Sourceware Infrastructure Project" or just Sourceware.

> But various people listed as "key stakeholders consulted" said they
> either didn't know anything about this, they were contacted but never
> got any details, or were only told about parts of it.

It would be nice to hear from these folks on what parts were withheld 
from them.

> That is precisely what we have been doing for the last couple of
> months. And we don't believe that is in conflict with finding
> alternative sources of funding, creating a technical advisory committee
> and/or possibly having some "managed services" where that makes sense.

That part is not in conflict, calling it the "Sourceware project" is.

Sid

  reply	other threads:[~2022-10-11 13:24 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 20:08 Carlos O'Donell
2022-09-28 22:38 ` Carlos O'Donell
2022-10-02 20:47   ` Mark Wielaard
2022-10-04 13:46     ` Siddhesh Poyarekar
2022-10-04 14:01       ` Frank Ch. Eigler
2022-10-04 14:13         ` Siddhesh Poyarekar
2022-10-04 14:19           ` Frank Ch. Eigler
2022-10-04 14:33             ` Siddhesh Poyarekar
2022-10-04 14:41               ` Frank Ch. Eigler
2022-10-04 14:55                 ` Siddhesh Poyarekar
2022-10-04 15:07                   ` Frank Ch. Eigler
2022-10-06 21:42             ` Alexandre Oliva
2022-10-04 17:10       ` Christopher Faylor
2022-10-04 17:17         ` Siddhesh Poyarekar
2022-10-04 18:42           ` Christopher Faylor
2022-10-04 19:05           ` Mark Wielaard
2022-10-04 19:10             ` Siddhesh Poyarekar
2022-10-06 20:02               ` Mark Wielaard
2022-10-06 20:12                 ` Christopher Faylor
2022-10-06 21:37                   ` Siddhesh Poyarekar
2022-10-07 13:39                     ` Mark Wielaard
2022-10-06 21:07                 ` Siddhesh Poyarekar
2022-10-06 21:36                   ` Frank Ch. Eigler
2022-10-06 21:44                     ` Siddhesh Poyarekar
2022-10-06 22:57                       ` Frank Ch. Eigler
2022-10-11 13:02                         ` Siddhesh Poyarekar
2022-10-07  8:57                   ` Mark Wielaard
2022-10-11 13:24                     ` Siddhesh Poyarekar [this message]
2022-10-11 14:23                       ` Frank Ch. Eigler
2022-10-11 15:58                     ` Alexandre Oliva
2022-10-11 17:14                       ` David Edelsohn
2022-10-11 18:12                         ` Frank Ch. Eigler
2022-10-12  8:00                         ` Mark Wielaard
2022-10-12 13:18                           ` Florian Weimer
2022-10-12 21:23                             ` Mark Wielaard
2022-10-12 15:15                           ` Jonathan Corbet
2022-10-12 10:55                         ` Alexandre Oliva

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=684fc3a1-f48b-8a7b-6b1b-992f44118220@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=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).