From: Jonathan Corbet <corbet@lwn.net>
To: Carlos O'Donell <carlos@redhat.com>
Cc: overseers@sourceware.org
Subject: Re: The GNU Toolchain Infrastructure Project
Date: Thu, 29 Sep 2022 08:45:50 -0600 [thread overview]
Message-ID: <87v8p6i6ht.fsf@meer.lwn.net> (raw)
In-Reply-To: <ef140a6b-c72d-bd63-b94c-bceeb365b32a@redhat.com>
carlos@redhat.com (Carlos O'Donell) writes:
> During the Sourceware / Infrastructure BoF sessions at GNU Cauldron, the GNU
> Toolchain community in collaboration with the Linux Foundation and OpenSSF,
> announced the GNU Toolchain Infrastructure project (GTI).
Thanks for making more information available.
Just for the record, it is still my feeling that the LF's infrastructure
management has been a good thing for the kernel community. Whether it
would be suitable for the toolchain community is not something I'm in a
position to have an opinion on. If anybody is curious about how
interactions with that group work, there is a current discussion on
bugzilla that might be interesting:
https://lwn.net/ml/ksummit-discuss/05d149a0-e3de-8b09-ecc0-3ea73e080be3@leemhuis.info/
Konstantin's response to the idea of moving everything to a Gitlab
instance is the sort of thing I find reassuring.
I do, though, have a few questions.
- Why not dispense with the governing board and have the TAC be the
decision-making body? That would help ensure ongoing community
control over this infrastructure. It would also be a clear statement
from the sponsors that they trust the community and do not intend to
force changes in how development is done.
- How were the members of the TAC chosen, and what will be the process
for choosing members in the future?
- During the Cauldron discussion it was said that $400,000 in annual
funding has been committed to GTI. You must have a rough budget for
how those funds will be spent that you can share?
- Keeping that money stream going will surely require ongoing
fundraising efforts; who will be responsible for that? What happens
if, say, tech companies start getting nervous about dark economic
clouds on the horizon and stop funding the project?
Thanks,
jon
next prev parent reply other threads:[~2022-09-29 14:45 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 19:59 Carlos O'Donell
2022-09-28 14:06 ` Frank Ch. Eigler
2022-09-29 9:51 ` Mark Wielaard
2022-09-29 14:45 ` Jonathan Corbet [this message]
2022-09-29 17:13 ` Joseph Myers
2022-09-29 18:40 ` Elena Zannoni
2022-09-29 18:54 ` Andrew Pinski
2022-10-19 5:47 ` Carlos O'Donell
2022-09-29 21:13 ` Andrew Pinski
2022-09-30 14:35 ` Siddhesh Poyarekar
2022-09-30 15:05 ` Andrew Pinski
2022-09-30 15:51 ` Siddhesh Poyarekar
2022-10-02 21:56 ` Mark Wielaard
2022-09-30 15:22 ` Christopher Faylor
2022-09-30 15:34 ` Siddhesh Poyarekar
2022-10-02 21:38 ` Mark Wielaard
2022-10-02 22:19 ` Mark Wielaard
[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
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
[not found] <b00dc0aa-31a6-a004-a430-099af3d0f6d1@redhat.com>
[not found] ` <558996ac-e4a0-cf77-48b9-f7d0e13862e8@redhat.com>
2022-10-02 20:54 ` Mark Wielaard
2022-10-03 19:24 ` 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=87v8p6i6ht.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=carlos@redhat.com \
--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).