Re: Microsoft acquires GitHub

Plus, like people said, its decentralized. If they suddenly go nuts and
delete everything, you can just, though its a major PITA, just upload a
copy of the repo to a new server and change url's. If you want to be
paranoid about it, have a domain name that just aliases to github and then
if shit hits the fan point it elsewhere.

2018-06-05 19:52 GMT+02:00 David Quintana (gigaherz) <[email protected]>:

> No one said we don't need a plan B. We had a plan B before moving to
> github.
> In fact, the move to github only happened because people were assured we'd
> always have a plan B.
> Why? Because github's servers are in the US, and many of the dev team
> didn't like the idea to put our sources in US computers.
>
> I will proceed to ignore everything after your first line, because it's
> mindless paranoia.
>
> You do have a point about the issues, except we don't host them on github,
> so only the Pull Requests would remain, and i'm 100% sure if github becomes
> hostile, we'll have plenty time to make a copy of the data.
>
> [I was typing that and the power blinked off long enough to shut down my
> pc ¬¬]
>
> On 5 June 2018 at 19:43, M. Ziggyesque <[email protected]> wrote:
>
>> No, I don't see it as pointless to have a plan B. It's more a question of
>> when, not if, it's desirable, given past practices.
>>
>> Even with no immediate changes, github can no longer be considered
>> vendor-neutral. Down the road, as example, M$ may well try to require every
>> project adopt their code-signing policy or the project gets deleted, so
>> they get their kickbacks on all the certificate fees that would entail. ROS
>> doesn't require code-signing?? DELETE!! They did similar when they bought
>> out sysinternals, bloated all their utilities with certificates, so that's
>> a distinct possibility.
>>
>> While migrating the repo itself is easy, the issues list and other
>> history is less so, plus the hassle of getting links on external pages to
>> redirect to a new home; those would take some lead time so imo is better to
>> have some plan than not.
>>
>> ------ Original message------
>> *From: *David Quintana (gigaherz)
>> *Date: *Tue, Jun 5, 2018 4:40 AM
>> *To: *ReactOS Development List;
>> *Cc: *
>> *Subject:*Re: [ros-dev] Microsoft acquires GitHub
>>
>> To elaborate further:
>>
>>    1. The deal won't be closed for many months (they expect december)
>>    2. Microsoft probably won't change github at first (xcept maybe make
>>    the login integrate with a Microsoft Account)
>>    3. We don't know what they plan to do with the platform in the long
>>    term, so worrying now is pointless.
>>    4. We don't know that it will EVER be hostile toward ReactOS, even if
>>    they break the platform and make it unusable, so chances are we are good.
>>    5. If worst comes to worst, as Thomas said, we just say goodbye to GH
>>    and move elsewhere.
>>
>>
>>
>> On 5 June 2018 at 10:36, Javier Agustìn Fernàndez Arroyo <
>> [email protected]> wrote:
>>
>>> great! :)
>>>
>>> On Tue, Jun 5, 2018 at 10:34 AM, Thomas Faber <[email protected]>
>>> wrote:
>>>
>>>> To elaborate, we're not dependent on GitHub in any significant way. It's
>>>> just convenient. But if it stops being so, it's easy to go elsewhere.
>>>> That's a key part of Git, being a "distributed" VCS.
>>>>
>>>>
>>>> On 2018-06-05 10:31, Oleksandr Shaposhnikov wrote:
>>>> > No it may not.
>>>> >
>>>> > 5 черв. 2018 р. 11:24 Javier Agustìn Fernàndez Arroyo <
>>>> [email protected]> пише:
>>>> >
>>>> >      May this affect ReactOS?
>>>> >
>>>> >      https://blogs.microsoft.com/blog/2018/06/04/microsoft-github
>>>> -empowering-developers/
>>>> <https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblogs.microsoft.com%2Fblog%2F2018%2F06%2F04%2Fmicrosoft-github-empowering-developers%2F&data=02%7C01%7C%7Ca6b7a92ca5c146e5bc5e08d5cac00cc9%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636637848550395788&sdata=MphM9bR%2F0p14QXZQBKrHGfUK3cmOwVfNKDYXdqtBMVA%3D&reserved=0>
>>>>
>>>>
>>>> _______________________________________________
>>>> Ros-dev mailing list
>>>> [email protected]
>>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>> <https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.reactos.org%2Fmailman%2Flistinfo%2Fros-dev&data=02%7C01%7C%7Ca6b7a92ca5c146e5bc5e08d5cac00cc9%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636637848550552040&sdata=V8%2B3DEP1VRUt2B34MdmNxVef9urlPZ8tYoamkdKQdts%3D&reserved=0>
>>>
>>>
>>>
>>> _______________________________________________
>>> Ros-dev mailing list
>>> [email protected]
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>> <https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.reactos.org%2Fmailman%2Flistinfo%2Fros-dev&data=02%7C01%7C%7Ca6b7a92ca5c146e5bc5e08d5cac00cc9%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636637848550552040&sdata=V8%2B3DEP1VRUt2B34MdmNxVef9urlPZ8tYoamkdKQdts%3D&reserved=0>
>>>
>>
>>
>
> _______________________________________________
> Ros-dev mailing list
> [email protected]
> http://www.reactos.org/mailman/listinfo/ros-dev
>

_______________________________________________
Ros-dev mailing list
[email protected]
http://www.reactos.org/mailman/listinfo/ros-dev