From: "Frank Ch. Eigler" <fche@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: Overseers mailing list <overseers@sourceware.org>,
"Frank Ch. Eigler" <fche@elastic.org>,
gdb@sourceware.org, Mark Wielaard <mark@klomp.org>,
libc-alpha@sourceware.org, binutils@sourceware.org,
gcc@gcc.gnu.org
Subject: Re: The GNU Toolchain Infrastructure Project
Date: Tue, 4 Oct 2022 10:41:14 -0400 [thread overview]
Message-ID: <20221004144114.GB15858@redhat.com> (raw)
In-Reply-To: <dd229687-9e22-d779-dbed-d2121e379388@gotplt.org>
Hi -
> > > I don't see a risk to freedom. The GNU toolchain is quite underfunded
> > > compared to llvm/clang and IMO it's a major risk to maintain status quo on
> > > that front. The GTI opens new avenues for funding aspects of the GNU
> > > toolchain without affecting its core governance.
> >
> > What aspects of the gnu toolchain are open to being funded via the
> > LF/GTI proposal, -other than- the vast majority of the funds being
> > redirected to its own managed services infrastructure?
>
> This current proposal is limited to infrastructure, which has ever-growing
> needs.
I'm afraid I don't understand then what the point of comparing to LLVM
with respect to competitiveness or freedom was. AIUI, infrastructure
is an enabler, not really a competitive differentiator.
> Do you think the current proposal is not an upgrade to what we
> currently have?
I don't know. I am not under the impression that infrastructure is
holding back development on any of these projects. Further, I suspect
that if the communities were given a choice to direct the sponsors'
generous donations toward new development type work, they may well
prefer that. Is that possibility on offer?
- FChE
next prev parent reply other threads:[~2022-10-04 14:41 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d9cb6cf9-89f5-87bb-933b-a03240479e71@redhat.com>
[not found] ` <a9396df3-5699-46ef-0b33-6c7589274654@redhat.com>
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 [this message]
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
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
2022-09-27 20:08 Carlos O'Donell
2022-09-28 22:38 ` Carlos O'Donell
2022-09-29 10:02 ` Nick Clifton
2022-10-02 20:54 ` Mark Wielaard
2022-10-03 19:24 ` Carlos O'Donell
2022-10-17 11:48 ` Luis Machado
2022-10-17 12:08 ` Siddhesh Poyarekar
2022-10-17 12:16 ` Luis Machado
2022-10-18 18:45 ` Siddhesh Poyarekar
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=20221004144114.GB15858@redhat.com \
--to=fche@redhat.com \
--cc=binutils@sourceware.org \
--cc=fche@elastic.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.org \
--cc=siddhesh@gotplt.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).