Sad to see they only use MS GitHub instead of selfhosting something like GitLab. Just another vendor lock-in.
We will continue to use Bugzilla, moz-phab, Phabricator, and Lando.
Although weβll be hosting the repository on GitHub, our contribution workflow will remain unchanged and we will not be accepting Pull Requests at this time.
The cool thing about distributed version control is that itβs distributed. It sounds like GitHub will just be a public remote, rather than the place where active development happens.
Since they will not use Github for Pull Requests, bug tracking, or any other bonus feature on top of git, I have to disagree. It would be super easy to change the host of their git repo.
Depends a bit on what the default cloning url will be. If the domain is in control of mozilla, which forwards it to github, then fine, if most people start using the github url, then it is still a vendor lock in, because many people and projects will use it, and that is not so easy to move away.
Update: To the people down-voting my comment, I would love to hear why you either disagree with me, or find that my that my contribution to this discussion is worthless.
The upstream URL of a project or repo is important, because it will be used in other projects, like in build scripts for fetching the sources. If a projects changes that URL in the future, and the old URL is no longer available/functional, all those scripts need to be changed and the old versions of these scripts do not work anymore out of the box.
If the project owns the URL, then can add redirect rules, that might help alleviate some of these issues. I donβt think github allows projects that move away from it to do that. So this is a sort of vendor lock-in. The project needs to maintain the repo on github, because they want to break the internet as little as possible.
Honest question - is GitLab really that different of a vendor lock-in over GitHub?
Gitlab can be self-hosted. GitHub is a cloud-only service.
So they could do git.mozilla.com and it would be their own instance of git, on their own hardware (or, probably, from their own AWS account). They control it entirely.
It absolutely is. Yes. You can run and maintain it on an own server and it is open core (yeah π₯) using the MIT license - unlike GitHub where you have to rely 100% on the goodwill of Microsoft and everything is closed and locked behind a TOS.
So why not use forejo, which is completely open source?
If your criticism is MS pulling the plug, then Gitlab pulling a Redis/Hashicorp move and re-licensing their core should also be a concern
Gitlabβs AGPL so I donβt think thereβs anything stopping you from moving to a self managed instance.
No Gitlab is not AGPL, it is partly MIT and the corporate branch is under a proprietary license
Although weβll be hosting the repository on GitHub, our contribution workflow will remain unchanged and we will not be accepting Pull Requests at this time
