From: Ian Kelling <iank@fsf.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Zoë Kooyman" <zoe@fsf.org>
Subject: Re: Sourceware / GNU Toolchain at Cauldron
Date: Fri, 16 Sep 2022 17:10:25 -0400 [thread overview]
Message-ID: <878rmjhv5q.fsf@fsf.org> (raw)
In-Reply-To: <AE0DB51B-70EF-4D50-AF93-3094CC30C20D@fsf.org>
The message was accidentally not plain text, I'm replying just to make a
plain text version so it is readable in the archive:
Zoë Kooyman via Overseers <overseers@sourceware.org> writes:
Hi all,
We are aware that several presentations will be given at Cauldron this
weekend proposing new ways to support the Sourceware project and the GNU
Toolchain packages hosted there.
The FSF has been a fiscal sponsor to the GNU Toolchain for several years
(and continues to be), and has been grateful to have Sourceware
providing development infrastructure using free software. Unfortunately,
we won't have staff present at Cauldron, but we are keeping up with the
development of the various proposals and talking with people involved,
as well as seeing how we might be able to offer support to help make
good things happen.
We want Sourceware and the GNU packages it hosts to have stable homes
and strong futures in freedom. We expect the conversations in the next
few days to be open and transparent and involving the community, and
look forward to discussing the best way(s) forward in the coming weeks.
next prev parent reply other threads:[~2022-09-16 21:22 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 [this message]
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
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=878rmjhv5q.fsf@fsf.org \
--to=iank@fsf.org \
--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).