From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jeff King" <peff@peff.net>, "Derrick Stolee" <stolee@gmail.com>,
"Stefan Beller" <sbeller@google.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git <git@vger.kernel.org>, "Duy Nguyen" <pclouds@gmail.com>,
"Derrick Stolee" <dstolee@microsoft.com>
Subject: Re: Measuring Community Involvement (was Re: Contributor Summit planning)
Date: Mon, 27 Aug 2018 17:54:58 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1808271754140.73@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqin4cznmt.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Tue, 14 Aug 2018, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > On Tue, Aug 14, 2018 at 01:43:38PM -0400, Derrick Stolee wrote:
> >
> >> On 8/13/2018 5:54 PM, Jeff King wrote:
> >> > So I try not to think too hard on metrics, and just use them to get a
> >> > rough view on who is active.
> >>
> >> I've been very interested in measuring community involvement, with the
> >> knowledge that any metric is flawed and we should not ever say "this metric
> >> is how we measure the quality of a contributor". It can be helpful, though,
> >> to track some metrics and their change over time.
> >>
> >> Here are a few measurements we can make:
> >
> > Thanks, it was nice to see a more comprehensive list in one spot.
> >
> > It would be neat to have a tool that presents all of these
> > automatically, but I think the email ones are pretty tricky (most people
> > don't have the whole list archive sitting around).
>
> I do not think it covered e-mail at all, but there was git stats
> project several years ago (perhaps part of GSoC IIRC).
>
> > I think I mentioned "surviving lines" elsewhere, which I do like this
> > (and almost certainly stole from Junio a long time ago):
>
> Yeah, I recall that one as part of counting how many of 1244 lines
> Linus originally wrote still were in our codebase at around v1.6.0
> timeframe (the answer was ~220 IIRC) ;-)
And if you do not remember precisely, you can easily re-run `Linus` from
here: https://github.com/git/git/blob/todo/Linus
Ciao,
Dscho
next prev parent reply other threads:[~2018-08-27 15:55 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 16:31 Contributor Summit planning Jeff King
2018-08-13 16:58 ` Derrick Stolee
2018-08-13 17:15 ` Jeff King
2018-08-27 13:22 ` Johannes Schindelin
2018-08-27 13:30 ` Derrick Stolee
2018-08-28 12:22 ` Johannes Schindelin
2018-08-28 19:06 ` Jonathan Nieder
2018-08-28 19:11 ` Jonathan Nieder
2018-08-29 14:38 ` Johannes Schindelin
2018-08-29 4:52 ` Jeff King
2018-08-29 14:44 ` Johannes Schindelin
2018-08-13 17:46 ` Stefan Beller
2018-08-14 4:31 ` Christian Couder
2018-08-14 14:35 ` Jeff King
2018-08-13 18:49 ` Ævar Arnfjörð Bjarmason
2018-08-13 19:44 ` Jeff King
2018-08-13 20:36 ` Junio C Hamano
2018-08-13 20:41 ` Stefan Beller
2018-08-13 21:06 ` Jeff King
2018-08-13 21:19 ` Stefan Beller
2018-08-13 21:54 ` Jeff King
2018-08-14 17:43 ` Measuring Community Involvement (was Re: Contributor Summit planning) Derrick Stolee
2018-08-14 19:36 ` Jeff King
2018-08-14 19:47 ` Stefan Beller
2018-08-14 20:06 ` Jeff King
2018-08-15 7:12 ` Eric Wong
2018-08-14 20:42 ` Junio C Hamano
2018-08-27 15:54 ` Johannes Schindelin [this message]
2018-08-15 16:28 ` Duy Nguyen
2018-08-27 15:55 ` Johannes Schindelin
2018-08-14 14:30 ` Contributor Summit planning Duy Nguyen
2018-08-14 14:47 ` Jeff King
2018-08-14 16:57 ` Stefan Beller
2018-08-14 20:59 ` Junio C Hamano
2018-08-17 15:18 ` Duy Nguyen
2018-08-27 22:49 ` Johannes Schindelin
2018-08-29 5:02 ` Jeff King
2018-08-14 6:52 ` Elijah Newren
2018-08-14 13:25 ` Randall S. Becker
2018-08-14 14:06 ` Ævar Arnfjörð Bjarmason
2018-08-14 14:30 ` Jeff King
2018-08-14 14:28 ` Jeff King
2018-08-27 13:34 ` Johannes Schindelin
2018-08-29 4:55 ` Jeff King
2018-08-29 14:46 ` Johannes Schindelin
2018-08-30 3:20 ` Jeff King
2018-08-30 11:36 ` Johannes Schindelin
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=nycvar.QRO.7.76.6.1808271754140.73@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sbeller@google.com \
--cc=stolee@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.
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 NNTP newsgroup(s).