All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: phillip.wood@dunelm.org.uk, Patrick Steinhardt <ps@pks.im>,
	"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: Sun, 4 Feb 2024 16:12:02 +0100	[thread overview]
Message-ID: <Zb+pQk9R3AOouFxF@ugly> (raw)
In-Reply-To: <20240202115004.GV9696@kitsune.suse.cz>

On Fri, Feb 02, 2024 at 12:50:04PM +0100, Michal Suchánek wrote:
>Given the open nature of lore it should be feasible to provide
>additional interfaces on top of it that cater to people used to PRs
>on popular forge web UIs without hijacking the whole project and the
>existing tools and interfaces. For some reason people are set on
>replacing it as a whole, and removing the interfaces they personally
>don't use,

>calling them obosolete.
>
because they positively *are*.

when i started, patch-based code reviews were the norm, and i'm still
using them for my small project with almost no external contributions.

but after working with gerrit code review for over a decade, i find it
mind-boggling that people are still voluntarily subjecting themselves to
mail-based reviews for serious high-volume work.

it doesn't matter just how super-proficient you got with your old tools.
there is just no way you'll get anywhere near as efficient as you would
with the new ones, if you just were interested enough to learn them.
migrating the workflows that are worth keeping isn't such a bit deal.

i'll note that i don't consider github-like forges to be adequate tools
for serious work, as they seem to intentionally discourage producing
polished commits.
the gerrit project is unfortunately not interested in building a proper
forge, but luckily there is a bridge to github (hosted version available
at gerrithub.io).

  parent reply	other threads:[~2024-02-05  1:35 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
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 [this message]
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=Zb+pQk9R3AOouFxF@ugly \
    --to=oswald.buddenhagen@gmx.de \
    --cc=brille1@hotmail.com \
    --cc=dsimic@manjaro.org \
    --cc=git@vger.kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=msuchanek@suse.de \
    --cc=phillip.wood@dunelm.org.uk \
    --cc=ps@pks.im \
    --cc=sandals@crustytoothpaste.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.