All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kelling <iank@fsf.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Carlos O'Donell <carlos@redhat.com>,
	cti-tac@lists.linuxfoundation.org,
	Khahil White <kwhite@linuxfoundation.org>
Subject: Re: Next steps from GTI TAC meeting on 2023-03-08 - Evaluate cost of glibc migration.
Date: Mon, 22 May 2023 10:37:58 -0400	[thread overview]
Message-ID: <87wn108jqr.fsf@fsf.org> (raw)
In-Reply-To: <20230519-rebate-guru-b0528e@meerkat>


Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:

> In the case when we can't use the git tag note process, we can also do tarball
> uploads using our own "kup" tool that is done over ssh and uses the gitolite
> permission framework. I'm quite shocked that someone in the world still uses
> FTP for any uploads. :)

GNU already has a system for release uploads to https://ftp.gnu.org that
works very well and I help maintain it.

Debian uses ftp for package uploads according to
https://www.debian.org/security/faq and of course they support package
downloads over ftp too. There is nothing wrong with it for our use
case. Ssh would have the disadvantage of managing extra keys, but I'm
not opposed to adding it if it would make sense. If there are any
features lacking for the GNU ftp, we would be happy to add them. For GNU
maintainers to discuss potential improvements to the ftp the best place
is https://lists.gnu.org/mailman/listinfo/gnu-prog-discuss. There are
also multiple inherent advantages of GNU packages to use the GNU release
site. For example, for any changes to the set of keys gpg authorized to
upload, there is a manual review by FSF tech team and GNU volunteers.

-- 
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

  reply	other threads:[~2023-05-22 15:32 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 17:24 Next steps from GTI TAC meeting on 2023-03-08 - Evaluate cost of glibc migration Carlos O'Donell
2023-04-12 20:46 ` Konstantin Ryabitsev
2023-04-12 21:28   ` Brian Behlendorf
2023-05-19 21:00 ` Konstantin Ryabitsev
2023-05-22 14:37   ` Ian Kelling [this message]
2023-05-24 20:50     ` Carlos O'Donell
2023-05-24 21:53       ` Ian Kelling
2023-05-25 11:02         ` Carlos O'Donell
  -- strict thread matches above, loose matches on Subject: below --
2023-05-19 22:47 Joseph Myers
2023-05-22 10:11 ` Joel Brobecker
2023-05-24 12:44   ` Carlos O'Donell
2023-05-24 13:43     ` Siddhesh Poyarekar
2023-05-24 14:12       ` Carlos O'Donell
2023-05-24 15:18         ` Siddhesh Poyarekar
2023-05-23 17:38 ` Konstantin Ryabitsev
2023-05-23 19:34   ` Joseph Myers
2023-05-23 19:52     ` Konstantin Ryabitsev
2023-05-23 20:12       ` Joseph Myers
2023-05-23 20:21         ` Konstantin Ryabitsev
2023-05-23 22:12           ` Joseph Myers
2023-05-24 16:29             ` Konstantin Ryabitsev
2023-05-24 18:13               ` Siddhesh Poyarekar
2023-05-24 18:55                 ` Brian Behlendorf
2023-05-24 21:27                   ` Siddhesh Poyarekar
2023-05-25 11:06                     ` Carlos O'Donell
2023-05-24 19:06                 ` Konstantin Ryabitsev
2023-05-24 19:42                   ` Joseph Myers
2023-05-24 21:12                   ` Siddhesh Poyarekar
2023-05-25 11:12                     ` Carlos O'Donell
2023-05-24 18:58               ` Joseph Myers
2023-05-24 12:11       ` Siddhesh Poyarekar
2023-05-24 18:44         ` Joseph Myers
2023-05-24 19:58           ` Carlos O'Donell
2023-05-24 12:57     ` Carlos O'Donell
2023-05-24 18:46       ` Joseph Myers
2023-05-24 20:19         ` Carlos O'Donell
2023-05-24 20:48           ` Joseph Myers

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=87wn108jqr.fsf@fsf.org \
    --to=iank@fsf.org \
    --cc=carlos@redhat.com \
    --cc=cti-tac@lists.linuxfoundation.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=kwhite@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.