Dear Peter, Mark and Quixote team,
As you are probably aware, Atlassian has announced in August that they will be sunsetting their support of Mercurial in Bitbucket, a process that will end with the removal of all Mercurial repositories on June 1st, 2020.
From 2014 to 2016, our team at Memorial University has expanded the JUMBO-converters as well as a few CML-CompChem dictionaries, however so far we fell short at contributing our changes back to the original projects.
Now with the risk of all the work being lost when Bitbucket pulls the plug on Mercurial, it's time to take action.
The first course of action from my side will be to create Pull-Requests containing our work done in the JUMBO-converters and
xml-cml.org repositories, because it will be much harder to merge them after the Mercurial-repositories have been moved elsewhere or converted to Git.
- Do all repositories need to be migrated?
I think I've counted 50 repositories but I have no idea how many of them contain data that has later-on been combined into other repositories. - Should they be converted to Git and re-uploaded to BitBucket?
As I understand, data about issues and pull-requests will likely get lost during the process.
Wikis are repositories as well and can/need to be converted from Mercurial to Git as well.
It might be possible to export and re-import the issues though. - Maybe move to another hosting site? GitHub? GitLab?
Unfortunately https://github.com/wwmm and https://github.com/cml are already taken.
I'm happy to pitch in and work on migrating some of the repositories.
As I had been working with Git quite a lot before my work on JUMBO-converters, I have been using the
git-remote-gh plugin the whole time. This allows you to use the Git command line tools to work on hg repositories transparently.
What are your thoughts?
Cheers,
Oliver
Oliver Stueker
Research Consultant, ACENET
A Compute Canada Regional Partner