I know the move to github has been discussed before, multiple times. Some of the reasons not to switch to github (that there’s no clear benefit, that the T&Cs are not acceptable, etc.) seem very reasonable to us.
I am proposing to open a separate thread for a slightly separate discussion: the move from mercurial to git.
For many reasons, we initially preferred mercurial too (we as in our company: individual people had individual preferences).
We are currently using SDL for several games. We have had our own mercurial mirrors of all SDL2 projects on bitbucket for years now, and we use them to investigate how to implement certain features before we contact the original authors with our proposed solutions. We never relied on the github mirror because we didn’t know whether it would always be up to date with the upstream. Also, we weren’t sure that mercurial and git would not diverge towards paths that would make the automatic conversion incompatible. We would not want to rely on conversion tools like git-hg.
For better or worse, git seems to have won the VCS “battle” for now. It is not just a trend, it is here to stay. Mercurial support on bitbucket will soon be going away. It would seem reasonable to expect most other services and tools to follow suit. Mercurial will be less and less convenient to use for everybody, and git will be more and more convenient. As the world turned towards git, we saw the change almost unavoidable. Over the last 2 months, we have migrated all our repos to git.
Using git does not mean at all using github. Projects can still be self-hosted: you can use gitlab, gitolite, or several other solutions. We, for example, have mostly moved our of github and bitbucket, but find it convenient to rely on a solution with support for issue tracking.
Would the SDL development team be willing to consider this?
Backend Software Developer