From: Patrick Steinhardt <ps@pks•im>
To: "brian m. carlson" <sandals@crustytoothpaste•net>,
Hans Meiser <brille1@hotmail•com>,
Dragan Simic <dsimic@manjaro•org>,
Konstantin Ryabitsev <konstantin@linuxfoundation•org>,
"git@vger•kernel.org" <git@vger•kernel.org>
Subject: Re: Migrate away from vger to GitHub or (on-premise) GitLab?
Date: Fri, 2 Feb 2024 06:10:55 +0100 [thread overview]
Message-ID: <Zbx5Xzb3kyHvkp7C@tanuki> (raw)
In-Reply-To: <ZbxI4wNTBZ48YcTi@tapette.crustytoothpaste.net>
[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]
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]
> > 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-02 5:11 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AS2P195MB21350F44B079009C05A1EAF1E2432@AS2P195MB2135.EURP195.PROD.OUTLOOK.COM>
2024-02-01 12:10 ` Migrate away from vger to GitHub or (on-premise) GitLab? Hans Meiser
2024-02-01 12:20 ` Antonin Delpeuch
2024-02-01 12:21 ` Kristoffer Haugsbakk
2024-02-01 17:39 ` Hans Meiser
2024-02-01 12:56 ` Dragan Simic
2024-02-01 15:39 ` Konstantin Ryabitsev
2024-02-01 16:54 ` Dragan Simic
2024-02-01 17:00 ` Dragan Simic
2024-02-01 17:28 ` Hans Meiser
2024-02-01 17:49 ` Dragan Simic
2024-02-01 18:36 ` Hans Meiser
2024-02-01 19:00 ` Dragan Simic
2024-02-01 20:01 ` rsbecker
2024-02-01 20:09 ` Dragan Simic
2024-02-02 10:21 ` Hans Meiser
2024-02-02 10:18 ` Hans Meiser
2024-02-02 10:54 ` Dragan Simic
2024-02-02 11:23 ` Muting and unmuting threads (Was: Migrate away from vger to GitHub or (on-premise) GitLab?) Dragan Simic
2024-02-02 11:07 ` Migrate away from vger to GitHub or (on-premise) GitLab? Phillip Wood
2024-02-02 11:13 ` Dragan Simic
2024-02-02 19:02 ` Junio C Hamano
2024-02-02 1:44 ` brian m. carlson
2024-02-02 5:10 ` Patrick Steinhardt [this message]
2024-02-02 11:15 ` Phillip Wood
2024-02-02 11:50 ` Michal Suchánek
2024-02-02 12:36 ` Dragan Simic
2024-02-04 15:12 ` Oswald Buddenhagen
2024-02-04 15:28 ` Dragan Simic
2024-02-04 15:51 ` Michal Suchánek
2024-02-04 15:58 ` Dragan Simic
2024-02-04 15:47 ` Michal Suchánek
2024-02-05 1:04 ` Oswald Buddenhagen
2024-02-02 10:43 ` Hans Meiser
2024-02-02 10:48 ` Hans Meiser
2024-02-01 17:46 ` Nico Williams
2024-02-01 17:39 ` Kristoffer Haugsbakk
2024-02-02 14:49 ` Sergey Organov
2024-02-02 15:22 ` rsbecker
2024-02-02 16:16 ` Theodore Ts'o
2024-02-02 17:23 ` Michal Suchánek
2024-02-02 19:04 ` Junio C Hamano
2024-02-02 21:28 ` Theodore Ts'o
2024-02-06 7:22 ` Hans Meiser
2024-02-06 8:06 ` Dragan Simic
2024-02-02 16:41 ` Junio C Hamano
2024-02-02 17:06 ` rsbecker
2024-02-02 17:39 ` Junio C Hamano
2024-02-02 17:50 ` rsbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zbx5Xzb3kyHvkp7C@tanuki \
--to=ps@pks$(echo .)im \
--cc=brille1@hotmail$(echo .)com \
--cc=dsimic@manjaro$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=konstantin@linuxfoundation$(echo .)org \
--cc=sandals@crustytoothpaste$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox