public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Carlos O'Donell" <carlos@redhat.com>
Subject: Re: Toolchain Infrastructure project statement of support
Date: Wed, 12 Oct 2022 11:13:56 -0700	[thread overview]
Message-ID: <CA+=Sn1=yVxiYF0u==PhmmBY-7oOuoJsd2G=Kv4Lk8C76ymeh-A@mail.gmail.com> (raw)
In-Reply-To: <2513b668-9ebd-9e78-7263-dc24f4a9558a@redhat.com>

On Wed, Oct 12, 2022 at 9:43 AM Carlos O'Donell via Overseers
<overseers@sourceware.org> wrote:
>
> The GNU Toolchain project leadership supports the proposal[1] to move the
> services for the GNU Toolchain to the Linux Foundation IT under the auspices of
> the Toolchain Infrastructure project (GTI) with fiscal sponsorship from the
> OpenSSF and other major donors.

Who got to decide to be part of the leadership? Where are the bylaws?

>
> This support includes empowering the GTI Technical Advisory Committee to vote
> on issues surrounding key infrastructure requirements. Additionally we welcome
> any other projects at Sourceware.org that wish to join the effort.

Is there some kind of bylaws which describe the relationship between
GTI and the actual free source projects and the TAC?

>
> The GNU Toolchain is the cornerstone of the GNU/Linux ecosystem, the Cloud, and
> embedded environments. Open Source security best practices and mandates from
> governments and industry on software supply chain security require a strong
> effort to ensure compliance with policies, maintain the trust of the
> distributors of software built by the GNU Toolchain, and the continued vitality
> of the GNU Toolchain projects.

Trust is a heavy weighted word in general. Especially maintaining
trust of distributors is that really what we should be doing here,
rather than maintaining trust of the open/free sourceness of the
toolchain?

>
> We believe that utilizing the experience and infrastructure of the LF IT team
> that already is used by the Linux kernel community will provide the most
> effective solution and best experience for the GNU Toolchain developer
> community.

Can you expand on the voting mechanism that got to this decision? Is
there an email trail of all of emails between folks or notes from
meetings? Were the meetings held in private instead of allowing more
people to join the group? Who decided who was on the group and even
more how do people get to join the TAC and who gets to vote who is on
the TAC?

>
> As with kernel.org, GTI has requested from the Linux Foundation IT that all
> software implementing the infrastructure for the GNU Toolchain projects must
> be Free Software.  If Free Software versions of necessary security tools are
> missing, GTI will work with Free Software supporters to develop Free Software
> alternatives.

This is a stack backwards and even worse it is a fork.

Thanks,
Andrew Pinski

>
> Carlos O’Donell
> David Edelsohn
> Dave Miller
> Jason Merrill
> Jeff Law
> Jim Wilson
> Joel Brobecker
> Joel Sherrill
> Joseph Myers
> Kaveh Ghazi
> Martin Liska
> Ramana Radhakrishnan
> Richard Biener
> Segher Boessenkool
> Siddhesh Poyarekar
> Toon Moene
> Tulio Magno Quites Machado Filho
>
> [1] https://sourceware.org/pipermail/overseers/2022q3/018896.html
>

  reply	other threads:[~2022-10-12 18:14 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 16:43 Carlos O'Donell
2022-10-12 18:13 ` Andrew Pinski [this message]
2022-10-13 18:25 ` Christopher Faylor
2022-10-14 12:33   ` Siddhesh Poyarekar
2022-10-17 15:10   ` Mark Wielaard
2022-10-17 16:11     ` Siddhesh Poyarekar
2022-10-18  9:50       ` Mark Wielaard
2022-10-18 15:17         ` Siddhesh Poyarekar
2022-10-18 16:42           ` Christopher Faylor
2022-10-18 18:13             ` Siddhesh Poyarekar
2022-10-18 18:14               ` Siddhesh Poyarekar
2022-10-18 18:47                 ` Paul Smith
2022-10-21  0:33               ` Alexandre Oliva
2022-10-23  8:59           ` Ian Kelling
2022-10-23 13:27             ` Siddhesh Poyarekar
2022-10-23 15:16               ` Frank Ch. Eigler
2022-10-23 16:07                 ` Siddhesh Poyarekar
2022-10-23 16:32                   ` Siddhesh Poyarekar
2022-10-23 17:01                   ` Jeff Law
2022-10-23 22:35                     ` Christopher Faylor
2022-10-23 17:09                   ` Frank Ch. Eigler
2022-10-23 17:38                     ` Jeff Law
2022-10-24  1:51                     ` Siddhesh Poyarekar
2022-10-24 12:40                   ` Corinna Vinschen
2022-10-23 20:57               ` Christopher Faylor
2022-10-23 21:17                 ` Siddhesh Poyarekar
2022-10-23 21:59                   ` Christopher Faylor
2022-10-24  1:29                     ` Siddhesh Poyarekar
2022-10-23 11:33       ` Ian Kelling
2022-10-23 16:17         ` Siddhesh Poyarekar
2022-10-23 18:56           ` Konstantin Ryabitsev
2022-10-23 21:19 ` Alexandre Oliva
2022-10-23 22:07   ` Christopher Faylor

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='CA+=Sn1=yVxiYF0u==PhmmBY-7oOuoJsd2G=Kv4Lk8C76ymeh-A@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --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).