June 27, 2018 1 min. read
For a lot of people, learning that Microsoft will buy GitHub at the end of 2018 shattered trust in GitHub like the glass of @opendata26's Sony Xperia Z2 Tablet. Beyond that, GitHub has always employed vendor lock-in: the user's issues and pull requests are hidden behind a rate limited API instead of being available through a proper export feature. And even if you managed to export it through that API, you cannot host your own GitHub instance and modify it as you like because, there is not even a partially open source version of it.
We want to be in control of our own data. While we can't maintain a self-hosted solution at this point, we want to at least be able to create a public backup of all our > 1500 issues and pull requests once a week. After some discussion we ended up with gitlab.com as alternative, because its API allows us to create whole backups at once and we can import them into our own instance if we want to do that in the future. The workflow is similar to GitHub, so we expect a rather smooth transition compared to using something entirely different.
The migration is scheduled for Saturday (2018-06-30). If you have written anything in issues or pull requests in the postmarketOS repositories on GitHub, consider creating a gitlab account with the same e-mail address as your GitHub account for a smooth migration (so it will show what you have written on GitHub with your gitlab user on gitlab).
Thanks to @craftyguy for migrating our CI scripts in #1539. Also, thanks to everyone working at GitHub for providing us with their hosting service for more than a year. A good opportunity for Microsoft to follow through with their promises of being nice to the open source community would be to open up GitHub more. In case you think that won't happen and want to move away from GitHub as well, make sure to carefully evaluate all the platforms that are out there. Just because gitlab was the best match for us doesn't mean that you can't find a better one for your project.