Re: GTI TAC Meeting Notes 2022-11-09

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