From: Jakub Narebski <jnareb@gmail.com>
To: Elijah Newren <newren@gmail.com>
Cc: Pratyush Yadav <me@yadavpratyush.com>,
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: Sat, 26 Oct 2019 20:25:40 +0200 [thread overview]
Message-ID: <86k18rbbyz.fsf@gmail.com> (raw)
In-Reply-To: <CABPp-BEHy8c3raHwf9aFXvXN0smf_WwCcNiYxQBwh7W6An60qQ@mail.gmail.com> (Elijah Newren's message of "Thu, 24 Oct 2019 12:46:20 -0700")
Elijah Newren <newren@gmail.com> writes:
> On Thu, Oct 24, 2019 at 2:45 AM Pratyush Yadav <me@yadavpratyush.com> wrote:
>>
>> 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.
[...]
> 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.
[...]
> 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.
I agree with that. You need then to decide whether it is better to have
it easier for beginners to contribute, or is it better to have it easier
to review code. What are the pain points?
Another source worth looking into is "Patches carved into stone tablets,
why the Linux kernel developers rely on plain text email instead of
using “modern” development tools." presentation by Greg KH from
2016[1][2]. But remember that git-gui is not Linux kernel; what works
for one might not work for the other.
It is unfortunate that we have no tools described in "Patches carved
into developer sigchains"[3] wishfull blog post by Konstantin Ryabitsev...
[1]: https://kernel-recipes.org/en/2016/talks/patches-carved-into-stone-tablets/
[2]: https://www.slideshare.net/ennael/kernel-recipes-2016-patches-carved-into-stone-tablets
[3]: https://people.kernel.org/monsieuricon/patches-carved-into-developer-sigchains
Regards,
--
Jakub Narębski
next prev parent reply other threads:[~2019-10-26 18:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 20:13 RFC: Moving git-gui development to GitHub Pratyush Yadav
2019-10-24 2:06 ` Junio C Hamano
2019-10-24 7:37 ` Birger Skogeng Pedersen
2019-10-24 17:16 ` Denton Liu
2019-10-24 19:06 ` Pratyush Yadav
2019-10-24 21:29 ` Pratyush Yadav
2019-10-25 5:33 ` Birger Skogeng Pedersen
2019-10-25 17:47 ` Pratyush Yadav
2019-10-24 19:46 ` Elijah Newren
2019-10-25 18:36 ` Pratyush Yadav
2019-10-26 18:25 ` Jakub Narebski [this message]
2019-10-28 10:13 ` Konstantin Ryabitsev
2019-10-30 6:21 ` Elijah Newren
2019-11-20 12:19 ` Birger Skogeng Pedersen
2019-11-20 17:13 ` Elijah Newren
2021-04-19 20:33 ` Pain points in PRs [was: Re: RFC: Moving git-gui development to GitHub] SZEDER Gábor
2021-04-19 21:52 ` Junio C Hamano
2021-04-20 7:49 ` Son Luong Ngoc
2021-04-20 20:17 ` Junio C Hamano
2021-04-22 20:22 ` Felipe Contreras
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86k18rbbyz.fsf@gmail.com \
--to=jnareb@gmail.com \
--cc=bert.wesarg@googlemail.com \
--cc=birger.sp@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=johannes.schindelin@gmx.de \
--cc=me@yadavpratyush.com \
--cc=newren@gmail.com \
--cc=philipoakley@iee.email \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).