| 1 |
On Sun, 15 Feb 2015 02:13:36 +0300 |
| 2 |
Andrew Savchenko <bircoph@g.o> wrote: |
| 3 |
> > What's the difference between connecting to a proprietary Git server |
| 4 |
> > over an open network stack, and connecting to an open Git server |
| 5 |
> > over a proprietary network stack? |
| 6 |
> |
| 7 |
> 1a. If proprietary git server denies user, nothing can be done. |
| 8 |
> Access to a free software project is restricted. |
| 9 |
|
| 10 |
If an ISP decides to start blocking traffic, access is restricted. This |
| 11 |
happens regularly. |
| 12 |
|
| 13 |
> 1b. If proprietary network stack makes it impossible to use free |
| 14 |
> git server, it is possible to change ISP in most of cases. |
| 15 |
|
| 16 |
It's utterly trivial to move a Git repository. It's not easy to change |
| 17 |
ISP. |
| 18 |
|
| 19 |
> 2a. Github has almost no obligations to free software users: |
| 20 |
> service access is free, but may be restricted any moment without any |
| 21 |
> legal penalties. |
| 22 |
|
| 23 |
So what? If it is, it doesn't affect anything, because Git doesn't rely |
| 24 |
upon everything being in one specific place. |
| 25 |
|
| 26 |
> 2b. ISP services are usually paid for, so users have a possibility |
| 27 |
> to affect ISP actions in majority of cases. |
| 28 |
|
| 29 |
Tell that to anyone whose government decides to block Github... |
| 30 |
|
| 31 |
-- |
| 32 |
Ciaran McCreesh |
Archives