public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Ian Kelling <iank@fsf.org>
Subject: Re: Moving sourceware to the Linux Foundation? No thanks.
Date: Sun, 2 Oct 2022 23:15:27 +0200	[thread overview]
Message-ID: <Yzn/b5NkPL7Tcfbf@wildebeest.org> (raw)
In-Reply-To: <87edvvvpjk.fsf@fsf.org>

Hi Ian,

On Wed, Sep 28, 2022 at 04:53:15AM -0400, Ian Kelling via Overseers wrote:
> 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).

Thanks. Although the various GNU projects of course do use the GNU ftp
services which requires cryptographically signed releases. Other
Sourceware projects don't enforce that.

I'll file an sourceware infrastructure bug to see if we can provide
something similar to
https://www.gnu.org/prep/maintain/maintain.html#Automated-FTP-Uploads
for the other Sourceware projects. I assume the scripts for that are
available somewhere.

Also it might be nice to have cross-mirrors between sourceware and
gnu.

Cheers,

Mark

  reply	other threads:[~2022-10-02 21:15 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
2022-10-02 21:15                     ` Mark Wielaard [this message]
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=Yzn/b5NkPL7Tcfbf@wildebeest.org \
    --to=mark@klomp.org \
    --cc=iank@fsf.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).