May this affect ReactOS?
https://blogs.microsoft.com/blog/2018/06/04/microsoft-github-empowering-developers/
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
No it may not.5 черв. 2018 р. 11:24 Javier Agustìn Fernàndez Arroyo пише:May this affect ReactOS?https://blogs.microsoft.com/blog/2018/06/04/microsoft-github-empowering-developers/
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mail
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
great! :)
On Tue, Jun 5, 2018 at 10:34 AM, Thomas Faber
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, Olek
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 w
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-s
Let's no be paranoid and make plans out of nothing please...
And if Microsoft are that evil, why are you using their mail services?
Le 05/06/2018 à 19:43, M. Ziggyesque a écrit :
> 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 pas
> the issues list
WHAT?! We have JIRA for that :/
--
Stas'M was here
Вторник, 5 июня 2018, 20:44 +03:00 от "M. Ziggyesque" :
>
> 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
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
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 hit
> 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
> i
11 matches
Mail list logo
