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.
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.
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
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.
Sad to see they only use MS GitHub instead of selfhosting something like GitLab. Just another vendor lock-in.
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.
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.
They did host a git server at git.mozilla.org, but took it down years ago.
https://bugzilla.mozilla.org/show_bug.cgi?id=1277297
And you need a team managing it. I doubt that they have not considered it.
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.
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
Still better than a fully closed, 100% proprietary, cloud-only Microsoft service.
Where do they mention GH? They only mention git in the post.
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.