MKVToolNix moves to GitLab

Today I’ve moved MKVToolNix’ source code repository, the bug tracker and the wiki (including the FAQ) over to GitLab. You can continue using your checked-out copy of the source code if you want by simply replacing with in the file .git/config.

The move was done using GitLab’s import function. This means that all issues filed by people who already have a GitLab account will remain filed under your name (by mapping it to your GitLab account). All other issues have been mapped to me with mentioning the original poster in the issue text’s first line.

Anyone who doesn’t have a GitLab account yet — don’t fret. You can easily sign in to GitLab using your GitHub account (click on the corresponding icon at the below the login form).

5 thoughts on “MKVToolNix moves to GitLab

    1. mosu Post author

      Several reasons, including but not limited to GitLab being a much more open platform that GitHub will ever be. You can run your own GitLab instance for free, there’s a free & Open Source community edition, they provide excellent export & import functionality for all of your project’s data (including issues). A lot more features, and much more in line with the spirit of Open Source projects.

        1. mosu Post author

          I’m aware of that, have read the full post-incident analysis, but I don’t care about it. Accidents do happen. Similar things have happened to me. On our customer’s servers. On production databases.

          Matter of fact is that GitLab still provides much better backup opportunities to me, the end user, than GitHub does, and most likely ever will. Like I said I can get a full export of the whole MKVToolNix project on GitLab. Including issues and PRs. That I can import later, either in my own instance of the publicly hosted one. And I will definitely make use of that feature. Try doing that on GitHub.

          GitHub doesn’t have a good track record regarding listening to their users and implementing what they’re asking for. There’s always good and bad with each and every company and hosting opportunity. GitLab is just way more on the positive side than GitHub.

          1. Haakon

            About the drama I’d say that yeah, GitLab had a whoopsie. But if they learned from that, then why do we care now after the fact, if it wasn’t our data?

            Have GitHub tested their backup systems?

Comments are closed.