From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Cc: Alexander Berntsen <bernalex@gentoo.org>
Subject: Re: rsync mirror security (WAS: Re: [gentoo-dev] .gitignore)
Date: Tue, 11 Aug 2015 21:07:11 +1200 [thread overview]
Message-ID: <CAATnKFABU-7aEwM5=ChbmmX9pj6Ejxx0C4iUjY2JBeij6oJiCg@mail.gmail.com> (raw)
In-Reply-To: <20150811103801.6d0f9f33@pomiot>
On 11 August 2015 at 20:38, Michał Górny <mgorny@gentoo.org> wrote:
> Dnia 2015-08-11, o godz. 10:29:55
> Alexander Berntsen <bernalex@gentoo.org> napisał(a):
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> On 10/08/15 22:59, Aaron W. Swenson wrote:
>> > Users can fetch/pull from Github.
>> Users should not have to interface with or rely on proprietary
>> software to use Gentoo.
>
> Then please provide them with true open-source infrastructure. And also
> remember to block all the mirrors by default.
Its fine to say "can" in the context of "They may if they want to, but
they are not forced to".
Having a quality infrastructure should happen in parallel to github mirrors.
Uses may use the proprietary one or the opensource one.
As long as nothing *demands* they use the proprietary instead of the
opensource one, and there is a working path that is usable and
covenient to avoid the proprietary ( which there is in this case ),
then there's no real foul.
The only downside is realistically, if all users cloned from gentoo
infra using git, then we would drown.
"Ban mirrors" wouldn't fix this problem, "Ban github" wouldn't fix this problem.
So you basically *must* implement a reasonable infrastructure, and
they can use github instead if it is more convenient for them.
To an extent this does imply we're relying that *some* users will use
github/other to decrease our server load.
Meh.
--
Kent
KENTNL - https://metacpan.org/author/KENTNL
next prev parent reply other threads:[~2015-08-11 9:07 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 6:28 [gentoo-dev] .gitignore Justin (jlec)
2015-08-10 6:42 ` Mike Frysinger
2015-08-10 7:17 ` Michał Górny
2015-08-10 7:27 ` Mike Frysinger
2015-08-10 7:35 ` Justin (jlec)
2015-08-10 13:56 ` Anthony G. Basile
2015-08-10 15:04 ` Mike Gilbert
2015-08-10 15:09 ` Rich Freeman
2015-08-10 18:30 ` Daniel Campbell (zlg)
2015-08-10 20:13 ` rsync mirror security (WAS: Re: [gentoo-dev] .gitignore) hasufell
2015-08-10 20:47 ` Andrew Savchenko
2015-08-10 20:49 ` Andrew Savchenko
2015-08-10 20:59 ` Aaron W. Swenson
2015-08-10 21:05 ` [gentoo-dev] Re: rsync mirror security Matthias Maier
2015-08-11 3:06 ` Mike Frysinger
2015-08-11 3:23 ` Kent Fredric
2015-08-11 4:07 ` Mike Frysinger
2015-08-11 3:47 ` Matthias Maier
2015-08-11 3:20 ` Kent Fredric
2015-08-11 3:44 ` Matthias Maier
2015-08-11 3:56 ` Kent Fredric
2015-08-11 4:07 ` Matthias Maier
2015-08-11 11:15 ` Rich Freeman
2015-08-11 14:53 ` Matthias Maier
2015-08-11 16:25 ` Rich Freeman
2015-08-11 8:29 ` rsync mirror security (WAS: Re: [gentoo-dev] .gitignore) Alexander Berntsen
2015-08-11 8:38 ` Michał Górny
2015-08-11 9:07 ` Kent Fredric [this message]
2015-08-11 11:58 ` Rich Freeman
2015-08-11 12:26 ` Ciaran McCreesh
2015-08-11 14:01 ` Rich Freeman
2015-08-10 21:03 ` Michał Górny
2015-08-10 20:51 ` hasufell
2015-08-11 16:42 ` Michał Górny
2015-08-11 16:45 ` hasufell
2015-08-11 16:47 ` Michał Górny
2015-08-10 21:01 ` Michał Górny
2015-08-14 20:49 ` [gentoo-dev] .gitignore hasufell
2015-08-10 19:08 ` Mike Gilbert
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='CAATnKFABU-7aEwM5=ChbmmX9pj6Ejxx0C4iUjY2JBeij6oJiCg@mail.gmail.com' \
--to=kentfredric@gmail.com \
--cc=bernalex@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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