1 |
On Tue, Jul 3, 2018 at 12:34 PM William Hubbs <williamh@g.o> wrote: |
2 |
> |
3 |
> On Tue, Jul 03, 2018 at 11:40:53AM -0400, Rich Freeman wrote: |
4 |
> > On Tue, Jul 3, 2018 at 11:32 AM Brian Dolbec <dolsen@g.o> wrote: |
5 |
> > > 2) we have a large infrastructure of rsync mirrors, which we do not for |
6 |
> > > git. |
7 |
> > > |
8 |
> > |
9 |
> > Do we need them. I've yet to see somebody complain about poor syncing |
10 |
> > performance from github. I imagine we could just use that and a few |
11 |
> > other free mirroring services to distribute the tree. |
12 |
> |
13 |
> I don't feel comfortable relying on github as a primary means of |
14 |
> distributing the tree due to our social contract. It is a value-added |
15 |
> kind of service, but we should not rely on it. |
16 |
> |
17 |
|
18 |
Do you know that all our existing mirrors are 100% FOSS? |
19 |
|
20 |
It is a mirror. You upload something. Somebody else downloads the same thing. |
21 |
|
22 |
If we were distributing tarballs via http would we really care if the |
23 |
mirror is running apache vs IIS? Do we even check our existing |
24 |
mirrors for such things? Do we care that they're running on coreboot |
25 |
too, without an IME? |
26 |
|
27 |
Hey, I'm all for having all the mirrors we can, and it isn't like |
28 |
mirroring git is particularly difficult. I just think that there is a |
29 |
double-standard being applied when it comes to get. I completely get |
30 |
the argument when it comes to things like issues/PRs/etc since those |
31 |
aren't distributed, but for git itself you really just need something |
32 |
that supports the protocol and it is trivial to replace. Certainly |
33 |
for anything we host we should use FOSS because it is the cleanest |
34 |
solution anyway. |
35 |
|
36 |
-- |
37 |
Rich |