Re: RFC: Moving git-gui development to GitHub

From: Elijah Newren <newren@gmail.com>
To: Pratyush Yadav <me@yadavpratyush.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Bert Wesarg <bert.wesarg@googlemail.com>,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	Junio C Hamano <gitster@pobox.com>,
	Birger Skogeng Pedersen <birger.sp@gmail.com>,
	Philip Oakley <philipoakley@iee.email>,
	Johannes Sixt <j6t@kdbg.org>
Subject: Re: RFC: Moving git-gui development to GitHub
Date: Thu, 24 Oct 2019 12:46:20 -0700	[thread overview]
Message-ID: <CABPp-BEHy8c3raHwf9aFXvXN0smf_WwCcNiYxQBwh7W6An60qQ@mail.gmail.com> (raw)
In-Reply-To: <20191023201310.thzpxyoeb3ta55dc@yadavpratyush.com>

On Thu, Oct 24, 2019 at 2:45 AM Pratyush Yadav <me@yadavpratyush.com> wrote:
>
> Hi everyone,
>
> I recently had some discussions with Dscho about whether it is a better
> idea to use GitHub for development instead of email [0]. His argument
> was that GitHub makes it easier for newcomers to contribute, since more
> people are familiar with GitHub compared to mailing lists. Also, it is
> somewhat difficult to set up an email-based workflow.

Interesting; I had been pondering asking the opposite question for
filter-repo: Even though filter-repo is tracked externally to git.git
(since we seem to want to move to a batteries-not-included model),
would it be okay to ask that filter-repo contributors send patches to
the git mailing list (possibly specially marked somehow)?

I'm debating between:
  - Ask contributors to send filter-repo patches to the git mailing
list (if okay).
  - Try out GerritHub (GitHub + Gerrit; see gerrithub.io) and maybe use it
  - Assume there won't be many contributions (wouldn't be surprising)
and put up with GitHub PRs

GitHub is great for ease of creating new repos, learning about other
developers, finding similar projects, creation of webhooks, etc.  But
it's *awful* for code review.  Gerrit is a lot better at code reviews
(though still has problems); so maybe dealing with both GitHub and
Gerrit would be reasonable.  (Reviewable also exists, and is kinda
decent, but I can't respect anything that doesn't offer reviewability
of commit messages.  And it makes me feel bad by making me want to
swat butterflies.)  Email is a horrible medium for sending/receiving
changes, but at least it gets the overall code review model right
(commit-messages-are-first-order-objects-that-can-be-reviewed,
review-individual-commits, merge-per-topic, cover-letter included,
range-diff for high-level comparison of different iterations,
reversing-commit-order-display-based-on-author-timestamps-is-NOT-forgivable,
Change-IDs-are-ugly, magic-refs-are-disgusting, etc.), something no
GUI tool (yet) does to my knowledge.

So...would anyone object if I asked filter-repo contributors to send
contributions via email to the git mailing list?

Thanks,
Elijah