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