Re: Migrate away from vger to GitHub or (on-premise) GitLab?
- From
Patrick Steinhardt <ps@pks.im>
- Date
- Feb 2, 2024, 05:10 UTC
- Message-ID
- <Zbx5Xzb3kyHvkp7C@tanuki>
- In-Reply-To
- <ZbxI4wNTBZ48YcTi@tapette.crustytoothpaste.net>
On Fri, Feb 02, 2024 at 01:44:03AM +0000, brian m. carlson wrote:
> On 2024-02-01 at 18:36:48, Hans Meiser wrote:
[snip]
Show 14 quoted lines
> > In the end, it's all just about git. You may create your own git > > webserver (https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb), > > or just use an existing one, like the GitLab server: > > https://about.gitlab.com/install/ > > The Git project has tried for a long time to be neutral on any > particular external piece of software. Installing a GitLab server as > our preferred development platform would promote GitLab as the preferred > forge to other users. Similarly, moving to GitHub would prefer GitHub > over other forges. That's not a thing we want to do. > > We also don't accept patches or features for the benefit of one > particular forge or external project. Patches and features must be > of general benefit to the project at large.
I think this point is indeed really important in the context of the Git project. It's a rather unique limitation that no other project out there will really have. I don't think this has to completely rule out the use of a forge. But in my opinion it completely rules out any forge that is run by a for-profit company and that isn't completely open source. So GitLab, GitHub and Bitbucket are not really an option in my opinion.
That still leaves other forges like SourceHut, Gogs or Forgejo. But the benefit becomes at least a bit more questionable as the barrier for entry is again higher in that context -- after all most people only know about the large forges out there, and creating a new account raises the bar.
Patrick