From: Ian Kelling <iank@fsf.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Carlos O'Donell <carlos@redhat.com>
Subject: Re: Moving sourceware to the Linux Foundation? No thanks.
Date: Wed, 28 Sep 2022 04:53:15 -0400 [thread overview]
Message-ID: <87edvvvpjk.fsf@fsf.org> (raw)
In-Reply-To: <444c37f6-1e9e-3af3-0ca8-20a865b0855a@redhat.com>
Carlos O'Donell via Overseers <overseers@sourceware.org> writes:
> On 9/26/22 15:57, Frank Ch. Eigler via Overseers wrote:
> Even if we don't ship binaries, shipping source tarballs also might be of interest
> (currently only shipped via the GNU Project repositories).
I'm on of the FSF tech team members that maintains the GNU Project
repositories, eg: https://ftp.gnu.org/pub/gnu/gcc/ . If you have any
problems or improvement you want to that hosting, talk to us. There is
no reason for hosting to be changed or duplicated elsewhere. FSF can
actually host a lot more things and this seems to have been overlooked
when discussing potential changes to sourceware hosting.
I'm now watching this list, so talking here is fine. If you want to
email us privately, sysadmin@fsf.org (sysadmin@gnu.org goes to the same
place).
You can read about the FSF tech team here,
https://www.fsf.org/about/staff-and-board and out blog posts
https://www.fsf.org/blogs/sysadmin/
--
Ian Kelling | Senior Systems Administrator, Free Software Foundation
GPG Key: B125 F60B 7B28 7FF6 A2B7 DF8F 170A F0E2 9542 95DF
https://fsf.org | https://gnu.org
next prev parent reply other threads:[~2022-09-28 9:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Yw5aTCLyYx8qqN3W@wildebeest.org>
2022-08-31 22:19 ` Proposing Sourceware as SFC member project Jose E. Marchesi
2022-09-01 8:28 ` Mark Wielaard
2022-09-02 18:51 ` Daniel Pono Takamori
2022-09-03 14:07 ` Karen M. Sandler
2022-09-03 16:38 ` Mark Wielaard
2022-09-18 19:42 ` Moving sourceware to the Linux Foundation? No thanks Christopher Faylor
2022-09-25 22:31 ` Mark Wielaard
2022-09-26 14:07 ` Ian Lance Taylor
2022-09-26 17:05 ` Christopher Faylor
2022-09-26 19:57 ` Frank Ch. Eigler
2022-09-27 13:03 ` Carlos O'Donell
2022-09-28 8:53 ` Ian Kelling [this message]
2022-10-02 21:15 ` Mark Wielaard
2022-09-28 8:33 ` Ian Kelling
2022-09-28 10:08 ` Frank Ch. Eigler
2022-09-26 21:53 ` Moving sourceware into the future Mark Wielaard
2022-09-27 17:12 ` Daniel Pono Takamori
2022-09-26 22:21 ` Moving sourceware to the Linux Foundation? No thanks Carlos O'Donell
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=87edvvvpjk.fsf@fsf.org \
--to=iank@fsf.org \
--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).