| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 02/14/2015 02:40 PM, Ciaran McCreesh wrote: |
| 5 |
> On Sun, 15 Feb 2015 01:35:40 +0300 Andrew Savchenko |
| 6 |
> <bircoph@g.o> wrote: |
| 7 |
>> On Sat, 14 Feb 2015 22:31:48 +0000 Ciaran McCreesh wrote: |
| 8 |
>>> On Sat, 14 Feb 2015 23:23:48 +0100 Alexander Berntsen |
| 9 |
>>> <bernalex@g.o> wrote: |
| 10 |
>>>> On 14/02/15 23:13, Ciaran McCreesh wrote: |
| 11 |
>>>>> That's how Git works. |
| 12 |
>>>> |
| 13 |
>>>> Consider contributors (Gentoo developers or not) that want to |
| 14 |
>>>> submit patches to a project. They should have access to the |
| 15 |
>>>> primary repository (git or not), and be able to contribute |
| 16 |
>>>> without being forced to use proprietary software. This is |
| 17 |
>>>> incredibly easy to facilitate, so I don't expect us to have a |
| 18 |
>>>> problem related to github and our social mission here. |
| 19 |
>>> |
| 20 |
>>> What if their ISP runs proprietary software to manage its |
| 21 |
>>> network? Will Gentoo accept patches by pigeon? (Obviously the |
| 22 |
>>> postal service can't be relied upon to not use proprietary |
| 23 |
>>> software.) |
| 24 |
>> |
| 25 |
>> One should not confuse transparent data transmission mediator and |
| 26 |
>> active data management engine required to create, submit or apply |
| 27 |
>> changes. |
| 28 |
> |
| 29 |
> What's the difference between connecting to a proprietary Git |
| 30 |
> server over an open network stack, and connecting to an open Git |
| 31 |
> server over a proprietary network stack? |
| 32 |
> |
| 33 |
|
| 34 |
The proprietary network stack can be gotten around. If the git |
| 35 |
provider is closed and goes down, the data is gone. If a proprietary |
| 36 |
network stack goes down, there are other options available and the |
| 37 |
data is still available at the open repository. |
| 38 |
|
| 39 |
Unfortunately, most businesses are not in line with FOSS philosophy, |
| 40 |
so essentially every single ISP is using proprietary stacks. |
| 41 |
Additionally, one can check the hash of the HEAD or another known |
| 42 |
commit to verify data integrity of the repository to ensure the |
| 43 |
proprietary network didn't screw with it in transit. |
| 44 |
|
| 45 |
Keeping the repository open is more a matter of control and |
| 46 |
dependability than pure philosophy. No ISP that I know of uses FOSS |
| 47 |
stacks, so they're not really comparable imo. |
| 48 |
|
| 49 |
Just 2¢ from a user. |
| 50 |
-----BEGIN PGP SIGNATURE----- |
| 51 |
Version: GnuPG v2 |
| 52 |
|
| 53 |
iQEcBAEBAgAGBQJU39X8AAoJEJUrb08JgYgHVPoH/2jVpSf2lWuk7gYroPv/Zz5i |
| 54 |
PQWDvGPNXLXZrUd7x+2gXXCAnd5VaQVy/g2wtlSlJ9hlAnnXGs/dmjFsi9HcULwg |
| 55 |
PJeftIj10RjBGFBdC1IkU+7il7YNn7pXKTOjiiRdecKWUJM7My1twN2FoURk30cR |
| 56 |
aA64dxBF6BVGdXDSFNeYGI7HkTs5yjHe+oqsnj0GzzelBp20pHS3F4VUR3Z04nIJ |
| 57 |
iGesUSkxfWPlCzQSWSVhj9vA4OONIvoeSAY9cS/Wy7dAqfSkBKlZq2+kcXm4DTEn |
| 58 |
JekhjpvJKEpvG81kpw2tdrBPog3o5lEGoWodXO+aPadL7CdveotKsghefbp8ir4= |
| 59 |
=D1yC |
| 60 |
-----END PGP SIGNATURE----- |
Archives