How about some fine grained control over what metric people/projects want to
collect and display?
Supposing Kibble collects data on 100 different metrics , how about you do not
turn on and collect and display all 100, but rather a common subset, the rest
can be turned on/off at will.
On 10/21/2017 06:11 PM, Rich Bowen wrote:
> I think it's important that we are neutral in terms of saying that a
> particular metric is important, useful, necessary, so on. That is, while it
> may be obvious to us that a more corporately-diverse developer pool is a
> good thing, that is an opinion
I think it's important that we are neutral in terms of saying that a
particular metric is important, useful, necessary, so on. That is, while it
may be obvious to us that a more corporately-diverse developer pool is a
good thing, that is an opinion based in dogma, not in science. What's a
"good"
I'd like to kick off a larger discussion around what we hope Kibble can
achieve, and how this will come about.
For starters, what sort of data should we collect and display, what
types of visualizations should we offer, and are there special formulas
or algorithms (like Pony Factor) that we'd
