public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@gmail.com>
To: "Zoë Kooyman" <zoe@fsf.org>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: GNU Toolchain Proposal public discussion
Date: Thu, 20 Oct 2022 17:50:42 -0600	[thread overview]
Message-ID: <0bcd5e38-414d-88a8-edca-13e50947c1f1@gmail.com> (raw)
In-Reply-To: <c1536378-1975-eb20-8e80-a20a2387ad57@fsf.org>

On 10/18/22 11:25 AM, Zoë Kooyman via Overseers wrote:

> Please note: the FSF has not made recommendations or
> endorsements. We want to listen carefully to the different
> community ideas and proposals so that we can determine how best
> to help the projects succeed.
> 
> If there is an interest in us hosting a similar conversation for
> the Sourceware/SFC proposal, we would be happy to facilitate that
> too.
> //
> Thanks,

Hi Zoë,
I would be really interested in hearing in full the Sourceware plans,
basically what Mark was going to present at Cauldron, but didn't get the
chance. I know that there are plans for many things that would allow to
increase the security of the software supply chain that would probably
alleviate some of the "anxiety", but I would like to discuss the
details. And whatever has been already done, like the public-inbox and
the CI work. I don't think it's been presented as a whole coherent body
of work, so I'd like to hear how the pieces fit together, their
interdependencies, etc.

thanks
elena



> 
> Zoë
> 


      reply	other threads:[~2022-10-20 23:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 17:25 Zoë Kooyman
2022-10-20 23:50 ` Elena Zannoni [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=0bcd5e38-414d-88a8-edca-13e50947c1f1@gmail.com \
    --to=ezannoni@gmail.com \
    --cc=overseers@sourceware.org \
    --cc=zoe@fsf.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).