linaro-infrastructure-stakeholders team mailing list archive

[Guilherme Salgado <salgado@xxxxxxxxxxxxx>]

On Mon, 2011-08-29 at 11:22 -0300, Christian Robottom Reis wrote:
> On Thu, Aug 25, 2011 at 05:32:28PM -0300, Guilherme Salgado wrote:
> > > > patches.linaro.org (which has been well received):
> > > >  1. Can we include a monthly stacked column showing patches per team
> > > 
> > > This may be straightforward based on the data that is already available,
> > > I'll ask Guilherme when he returns.
> > 
> > Yes, that can be done easily.  One concern someone had with this in the
> > past was that this could promote comparisons between teams.
> 
> I think we've learnt that /anything/ you look at on patches.linaro.org
> can be used to promote inappropriate comparisons. I kinda feel like

Fair enough. However, I'm convinced a chart is not the best option here,
given the number of teams we have and the abilities of the charting
framework we use.  Given enough time I could bend the charting framework
and make a big enough chart that would be at least readable, but it
certainly won't be trivial.  To give you an idea, this is what a stacked
chart looks like on my local instance -- on production the columns on
the right end would be much taller so the labels would overlap with
them.

  http://people.linaro.org/~salgado/teams.png

I'm thinking of doing it as a table instead. Something like

                     Number of patches submitted (and accepted)
Team           |  April    |    May     |   June     | ...         |
===================================================================
Foo bar        | 134 (79)  |   98 (56)  |  197 (135) | ...         |
...

How does that sound?

> putting "A Disclaimer from the Linaro VP of Engineering" on each page of
> the patch tracker, but let's see if the problem gets worse.
> 
> In this case the benefit of being able to easily see what the team has
> produced probably outweighs the comparison risk.

-- 
Guilherme Salgado <https://launchpad.net/~salgado>

Attachment: signature.asc
Description: This is a digitally signed message part