[Tracker-discuss] [Python-Dev] Summary of Python tracker Issues

[Daniel Diniz]

Hi David,

On Fri, Apr 3, 2009 (sorry about replying this late!) R. David Murray wrote:
> On Fri, 3 Apr 2009 at 18:06, Python tracker wrote:
[...]
>> 2272 open (+59) / 15229 closed (+39) / 17501 total (+98)
>>
[...]
>> Open Issues Breakdown
>>  open  2222 (+57)
>> pending    50 ( +2)
>>
>> Issues Created Or Reopened (103)
>> ________________________________
>>
> [...]
>>
>> Issues Now Closed (233)
>> _______________________
>>
>
> Let's see if I understand this.  So there were 98 new issues opened,
> of which 39 were closed in the reporting period and 50 were left open.
> Then in a disjoint reporting, 103 items become opened either by being
> created or by being reopened, and 233 bugs in total went from some open
> state to closed during the reporting period.
>
> OK.  But that first line is _really discouraging_.

Yep, I had the same problem[1].

>  I suggest we change
> this report to provide statistics that are designed to encourage people
> using the tracker when they make progress on reducing the total number
> of outstanding bugs, or at least make it clear that the open bug count
> isn't increasing as fast as the above report format makes it seem.

I'll try to implement this today.

> (An aside: I don't think I care how many total bugs there are.  IMO that's
> just noise in a report like this.)

I think it helps giving some perspective to newcomers, but it might be
better to move it to the bottom of the report.

> I'd like to see something more like:
>
>    New issues this week:            98
>    Old issues reopened:              5
>                                    ---
>    Additional open this week:      103
>
>    New issues closed this week:     39
>    New issues set close pending:     2
>    Old issues closed this week:    194
>                                    ---
>    Total issues closed this week:  233
>
>
>    Open issue count on 03/27:     2353
>    Open issue count on 04/03:     2222
>                                   ----
>    Net decrease in open issues:    131

Looks good, I'll add this to our current report (as opposed to
replacing the corresponding bits) and ping this list and  #python-dev
so we can compare and improve the format.

> Presumably there is also an 'old issues set pending' line to add
> in the second set.

Just to be clear,  'Old issues reopened' includes old issues that were
'pending' and are now 'open', right?

> Would this be possible?

Yes :)

>  Any other suggestions for clearer and/or more moral building reporting?

I'd like to add line graphs to show how the numbers change during
time, preferably using the Google Chart API[2] (and maybe TinyURLs).
Also, I think we might include a link to Facundo's report[3] (I wish
the activity graph as bigger and started at, say, 2006).

Best regards,
Daniel

[1] http://mail.python.org/pipermail/python-dev/2009-February/086269.html
[2] http://code.google.com/apis/chart/
[3] http://www.taniquetil.com.ar/cgi-bin/pytickets.py