From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Overseers mailing list <overseers@sourceware.org>
Subject: Re: Sourceware / GNU Toolchain at Cauldron
Date: Mon, 3 Oct 2022 11:55:36 -0400 [thread overview]
Message-ID: <20221003155536.h6lgvsrndyurahmp@cgf.cx> (raw)
In-Reply-To: <95f2c79d-1dbc-4e52-0d89-d3babdae66c5@gotplt.org>
On Mon, Oct 03, 2022 at 09:26:57AM -0400, Siddhesh Poyarekar wrote:
>...
You're bringing up concerns but, even if they are valid, they don't
translate into requiring a wholesale transfer of control to another
entity. It is not a given that the current overseers can't act to
mitigate agreed-upon security issues, especially with the help of the
SFC.
Also, if these are really serious issues then this plan was developed in
private for two years without raising the alarm. During that time, the
people who claim that sourceware is in jeopardy have advanced the issues
as bullet points in presentations to the LF and friends. IMO, if these
really are serious concerns, they should have been discussed here much
earlier, without prompting, so that we could work through what needs to
be done.
It's like noticing that your neighbor's windows are open and working in
secret to acquire the house out from under them so that you can close
them "for their own good".
cgf
prev parent reply other threads:[~2022-10-03 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 20:57 Zoë Kooyman
2022-09-16 21:10 ` Ian Kelling
2022-09-18 16:27 ` Mark Wielaard
2022-09-18 21:38 ` Mark Wielaard
2022-09-19 21:09 ` Mark Wielaard
2022-09-26 22:04 ` Carlos O'Donell
2022-09-27 1:31 ` Alexandre Oliva
2022-09-27 11:02 ` Mark Wielaard
2022-09-28 11:14 ` Frank Ch. Eigler
2022-09-30 13:38 ` Carlos O'Donell
2022-10-02 14:55 ` Frank Ch. Eigler
2022-10-03 13:26 ` Siddhesh Poyarekar
2022-10-03 13:53 ` Frank Ch. Eigler
2022-10-03 19:16 ` Mark Wielaard
2022-10-03 15:55 ` Christopher Faylor [this message]
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=20221003155536.h6lgvsrndyurahmp@cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--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).