git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: RFC: Moving git-gui development to GitHub

From
Elijah Newren <newren@gmail.com>
Date
Oct 24, 2019, 19:46 UTC
Message-ID
<CABPp-BEHy8c3raHwf9aFXvXN0smf_WwCcNiYxQBwh7W6An60qQ@mail.gmail.com>
In-Reply-To
<20191023201310.thzpxyoeb3ta55dc@yadavpratyush.com>
On Thu, Oct 24, 2019 at 2:45 AM Pratyush Yadav <me@yadavpratyush.com> wrote:
Show 8 quoted lines
>
> 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

Previous: Pratyush YadavNext: Pratyush Yadav
Message 9 of 20 in “RFC: Moving git-gui development to GitHub”
  1. Pratyush YadavOct 23, 2019
  2. Junio C HamanoOct 24, 2019
  3. Birger Skogeng PedersenOct 24, 2019
  4. Denton LiuOct 24, 2019
  5. Pratyush YadavOct 24, 2019
  6. Pratyush YadavOct 24, 2019
  7. Birger Skogeng PedersenOct 25, 2019
  8. Pratyush YadavOct 25, 2019
  9. Elijah NewrenOct 24, 2019
  10. Pratyush YadavOct 25, 2019
  11. Jakub NarebskiOct 26, 2019
  12. Konstantin RyabitsevOct 28, 2019
  13. Elijah NewrenOct 30, 2019
  14. Birger Skogeng PedersenNov 20, 2019
  15. Elijah NewrenNov 20, 2019
  16. Pain points in PRs [was: Re: RFC: Moving git-gui development to GitHub]SZEDER Gábor, Apr 19, 2021
  17. Junio C HamanoApr 19, 2021
  18. Son Luong NgocApr 20, 2021
  19. Junio C HamanoApr 20, 2021
  20. Felipe ContrerasApr 22, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.