From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Kurt Taylor" <kurt.r.taylor@gmail.com>,
"OpenBMC Maillist" <openbmc@lists.ozlabs.org>
Subject: Re: OpenBMC Project metrics
Date: Thu, 05 Dec 2019 09:03:36 +1030 [thread overview]
Message-ID: <1fdc7be1-71f7-4926-83aa-a531de6d5b81@www.fastmail.com> (raw)
In-Reply-To: <CAG5OiwjaiBnGw17NZdW4=XDmiWpuEM=z5_jsTcJ8ws=p1umeRQ@mail.gmail.com>
On Thu, 5 Dec 2019, at 05:14, Kurt Taylor wrote:
> All, I just posted the project merge metrics for September and
> October. I will be updating the company/developer lists for November
> and posting those shortly. Enjoy.
>
> https://github.com/openbmc/openbmc/wiki/Project-Metrics
>
> NOTE: these metrics should be used *very carefully*. They do not
> represent the total contributions to the project. We value
> contributions many that do not show up in these charts, including
> reviews, mail list involvement, IRC involvement, etc.
Given all the caveats and the lopsided view the graphs display, what
are we trying to achieve by graphing the metric of commits per company?
It's also not clear to me what the inputs to these graphs are, for instance
whether changes to Linux, u-boot, qemu or other major projects that we
consume and contribute to are included or whether it's just repositories
under the openbmc org on github. If we're excluding upstream projects,
why?
Where are the scripts to reproduce the graphs? Can you contribute them
to openbmc-tools?
Andrew
next prev parent reply other threads:[~2019-12-04 22:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 18:44 OpenBMC Project metrics Kurt Taylor
2019-12-04 22:33 ` Andrew Jeffery [this message]
2019-12-06 13:33 ` krtaylor
2019-12-06 16:51 ` Patrick Williams
2019-12-09 18:41 ` krtaylor
2019-12-09 0:06 ` Andrew Jeffery
2019-12-09 18:24 ` krtaylor
2019-12-10 23:15 ` Andrew Jeffery
2020-01-06 22:36 ` James Mihm
2020-03-23 12:44 ` Brad Bishop
2020-03-23 20:21 ` Kurt Taylor
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=1fdc7be1-71f7-4926-83aa-a531de6d5b81@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=kurt.r.taylor@gmail.com \
--cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.