From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Carlos O'Donell <carlos@redhat.com>, gti-tac@lists.linuxfoundation.org
Subject: Re: GTI TAC Meeting Notes 2022-11-09
Date: Wed, 9 Nov 2022 13:28:54 -0500 [thread overview]
Message-ID: <4366b156-d1db-9414-66ec-6728eeaa3625@gotplt.org> (raw)
In-Reply-To: <90611be5-1c79-e5c9-e925-cad7ef854447@redhat.com>
On 2022-11-09 12:47, Carlos O'Donell wrote:
> - Siddhesh: Could we just use some of the LF and OpenSSF stuff?
> - David: Some of that could be non-FOSS
> - Siddhesh: Do we have concerns about non-FOSS for the TAC?
Specifically, I wanted to know if reusing their github project
namespaces was acceptable.
> - David: Yes.
> - Siddhesh: Yes, a simple solution would work.
> - David: Also have.
> - toolchains.dev
> - tollchain-infrastructure.org
> - Regarding the GNU Toolchain infrastrucutre at the LF IT proposal
> - Next steps?
> - Create a working group.
> - Detailed assessment of the current technoloyg and services.
> - Enumerate the features.
> - Wether the GTI TAC or subgroup, working with the LF IT
> - Use the more detailed list to do the analysis and sizing
> of effort and expense for:
> - Steady state provisioning of the services.
> - Transitioning the services.
> - With that plan and budget, the GTI TAC votes on that.
> - Plan goes out for review.
> - Jose: Do I have your permission to be a little bit naive here.
> - The GNU Toolchain projects are GNU projects.
> - The projects have had a historical process.
> - How do we make that decision?
> - Carlos: That would be for the GNU Toolchain projects to decide that.
> - David: Yes, this needs to go out to those projects to make their decisions.
> - Jose: That's clear.
> - Siddhesh: Yes, there is a bit of word soup here. The "Leadership" is the
> general term here because multiple projects use different nomenclature.
To add some more detail (since this question has come up multiple times
in previous years), we have:
- gcc: GCC Steering committee as the GNU/FSF representatives
- glibc: FSF Stewards. GNU maintainers (i.e. on Savannah) don't have
special powers in this context
- gdb: FSF appointed GDB Maintainers
- binutils: Nick and Alan (what do y'all call yourselves? The GNU
maintainer list on savannah looks different :) )
Sid
next prev parent reply other threads:[~2022-11-09 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 17:47 GTI TAC Meeting Notes 2022-11-09 Carlos O'Donell
2022-11-09 18:28 ` Siddhesh Poyarekar [this message]
[not found] ` <874jv7x384.fsf@gnu.org>
2022-11-09 20:55 ` Siddhesh Poyarekar
2022-11-09 19:08 ` Jeff Law
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=4366b156-d1db-9414-66ec-6728eeaa3625@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=gti-tac@lists.linuxfoundation.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 NNTP newsgroup(s).