From: Jeff King <peff@peff.net>
To: Roberto Tyley <roberto.tyley@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [RFC/PATCH] point pull requesters to Git Git Gadget
Date: Wed, 13 Mar 2019 15:34:37 -0400 [thread overview]
Message-ID: <20190313193436.GA3400@sigill.intra.peff.net> (raw)
In-Reply-To: <CAFY1edYQcWzYJXF6f_TRk4=bEMVnFXTAp=5u=TJ4XZ3UUd4EmA@mail.gmail.com>
On Tue, Mar 12, 2019 at 11:08:00PM +0000, Roberto Tyley wrote:
> On Tue, 12 Mar 2019 at 21:34, Jeff King <peff@peff.net> wrote:
> ...
> > We could continue to mention _both_ tools, but it's probably better to
> > pick one in order to avoid overwhelming the user with choice. After all,
> > one of the purposes here is to reduce friction for first-time or
> > infrequent contributors. And there are a few reasons to prefer GGG:
>
> That's fair enough - I haven't committed to submitGit for 2 years
> (it's continued to work without incident for most of that time I
> think!).
Yeah, it has been working fine as far as I know. I was a little curious
about how often (and about my impression that GGG was replacing it), so
I did some quick mining of the list archive. Here are numbers of
messages each month (from the last ~100k messages) mentioning Amazon SES
(presumably submitGit) or GitGitGadget in the message-id. I omitted
months with no entries for either, so there are some gaps:
ses ggg year-mo
--- --- -------
7 0 2015-07
2 0 2015-08
3 0 2015-09
1 0 2015-11
2 0 2016-01
3 0 2016-02
34 0 2016-03
27 0 2016-04
2 0 2016-05
6 0 2016-06
26 0 2016-07
54 0 2016-08
3 0 2016-09
29 0 2016-10
3 0 2016-12
4 0 2017-01
7 0 2017-03
5 0 2017-04
3 0 2017-05
23 0 2017-06
9 0 2017-07
14 0 2017-09
6 0 2017-10
8 0 2017-11
8 0 2017-12
38 0 2018-01
86 0 2018-02
49 0 2018-03
9 0 2018-04
1 0 2018-05
3 4 2018-06
0 86 2018-07
13 105 2018-08
0 65 2018-09
14 149 2018-10
7 131 2018-11
1 46 2018-12
14 96 2019-01
16 149 2019-02
0 44 2019-03
That measures pure patches, so they tend to cluster as there are often
several patches in a series. Poking manually at the ses hits, submitGit
seems to have been often used by GSoC and Outreachy applicants and
interns.
I don't know if any of this really supports or refutes my earlier commit
message, but I just thought it was kind of neat to see the numbers, so I
thought I'd share.
> > 2. Subjectively, GGG seems to be more commonly used on the list these
> > days, especially by list regulars.
>
> That's probably true too, though my interest with submitGit was more
> driven by helping early/first-time contributors than regulars. Though
> I'm sure GGG works well, in an ideal world it would be interesting to
> get a perspective from a cohort of those kind of users about what kind
> of flow works best for them - although, as I haven't been following
> development, maybe this has already been done?
I think the flow is quite similar, and GGG is definitely geared at
helping infrequent contributors, too. Dscho might have more thoughts on
this.
The biggest friction is marking a user as allowed to send. I think in
submitGit you have to "OK" the submitGit app sending on your behalf. In
GGG, somebody who already has been OK'd has to OK you with a comment in
the PR (after which you're approved for future PRs, too). It's possible
the approval could slow things down, but I think as long as users of the
tool are fairly prompt about approving non-spam PRs, it wouldn't be a
big deal.
> > I feel a little bad sending this, because I really value the work that
> > Roberto has done on submitGit. So just dropping it feels a bit
> > dismissive.
>
> Oh, you're very kind, that's ok! Very glad submitGit could help for a
> while, sounds like it was a good proof that GitHub could become part
> of the contribution process.
Yes, I think it definitely was.
-Peff
next prev parent reply other threads:[~2019-03-13 19:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 21:32 [RFC/PATCH] point pull requesters to Git Git Gadget Jeff King
2019-03-12 23:08 ` Roberto Tyley
2019-03-13 19:34 ` Jeff King [this message]
2019-03-13 20:50 ` Johannes Schindelin
2019-03-13 1:49 ` Junio C Hamano
2019-03-13 19:39 ` Jeff King
2019-03-13 20:18 ` Jeff King
2019-03-14 11:31 ` Johannes Schindelin
2019-03-15 3:19 ` Jeff King
2019-03-15 13:42 ` Johannes Schindelin
2019-03-15 18:43 ` Jeff King
2019-03-18 2:52 ` Junio C Hamano
2019-03-18 21:12 ` Jeff King
2019-03-18 21:48 ` Thomas Gummerer
2019-03-18 21:52 ` Jeff King
2019-03-19 0:30 ` Junio C Hamano
2019-03-18 22:25 ` Ævar Arnfjörð Bjarmason
2019-03-13 21:05 ` Johannes Schindelin
2019-03-13 22:17 ` Junio C Hamano
2019-03-13 2:07 ` Junio C Hamano
2019-03-13 2:18 ` Junio C Hamano
2019-03-13 19:39 ` Jeff King
2019-03-14 12:04 ` GitGitGadget on github.com/git/git?, was " Johannes Schindelin
2019-03-14 14:46 ` Duy Nguyen
2019-03-15 3:30 ` Jeff King
2019-03-15 14:51 ` Johannes Schindelin
2019-03-15 16:28 ` Ævar Arnfjörð Bjarmason
2019-03-15 18:41 ` Jeff King
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=20190313193436.GA3400@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=roberto.tyley@gmail.com \
/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).