From: Jeff King <peff@peff.net>
To: Philip Oakley <philipoakley@iee.org>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Git has a healthy truck factor..
Date: Tue, 14 Jul 2015 08:39:50 -0700 [thread overview]
Message-ID: <20150714153950.GA17709@peff.net> (raw)
In-Reply-To: <2E436A2846834D6CBD77FBEAD1EFB43C@PhilipOakley>
On Tue, Jul 14, 2015 at 12:05:58AM +0100, Philip Oakley wrote:
> It looks like Git has a healthy truck factor of 8, as reported in
> https://mtov.github.io/Truck-Factor/, which has Git eighth in the list of
> projects it analyzed, with Linux at second place.
>
> The analysis method paper is behind a pay wall, so I couldn't see how
> sensible the methodology, but it's nice to know Git's a broad team.
One thing I noticed is that Homebrew has an extremely high number. But I
suspect this is because it has a very large number of somewhat silo'd
files. That is, people work on package formulas for projects that
interest them, but what you really care about for the health of the
project is who is working on the base system. Maybe those formula
authors could step up, or maybe not, but I'm not sure that is reflected
in this analysis.
-Peff
next prev parent reply other threads:[~2015-07-14 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 23:05 Git has a healthy truck factor Philip Oakley
2015-07-14 15:39 ` Jeff King [this message]
2015-07-28 21:11 ` Junio C Hamano
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=20150714153950.GA17709@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.org \
/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).