linaro-infrastructure-stakeholders team mailing list archive

[James Westby <james.westby@xxxxxxxxxx>]

[ Replying with the correct list address ]

I have created a skeleton spec for this project at

  https://wiki.linaro.org/Platform/Infrastructure/Specs/BugMetrics

please help me to fill it out, starting with the questions below.

If any other group would like to be a stakeholder please speak up.

Thanks,

James


On Fri, 10 Dec 2010 16:40:36 -0500, James Westby <james.westby@xxxxxxxxxx> wrote:
> Hi,
> 
> Thanks for the proposal, I have some questions inline to get started on
> understanding the scope of the proposal better.
> 
> On Fri, 10 Dec 2010 14:45:55 -0600, Mounir Bsaibes <mounir.bsaibes@xxxxxxxxxx> wrote:
> > Subject: [Proposal] Metrics for Launchpad Tickets (bugs).
> > 
> >   Stakeholders: Mounir Bsaibes, Michael Hope and all tech leads
> >   Deadlines: After completing blueprints reports ( otherwise ASAP !).
> >   Estimated work: 2 weeks
> >   Contact: Mounir Bsaibes
> >   Summary: In order to correctly assess and track engineers' workload
> > and in order to monitor potential risks to the project,
> >   it is necessary to have some metrics that represent the bugs
> > assigned to each engineer and each Engineering Unit
> 
> Who is the intended audience for these metrics?  Just the tech leads?
> 
> >   These metrics can be:
> > 
> > 
> >    - Tickets Vs Time
> 
> This is a raw count of tickets? Do you care about different
> status/importance/etc?
> 
> Are you interested in the raw numbers or trends?
> 
> What do you want to be able to learn from this information?
> 
> >    - Age of tickets
> 
> I assume this is the length of time that tickets have been open?
> 
> Are you interested in all bugs, or particular statuses/importances?
> 
> Do you want a distinction between still open and recently closed
> tickets?
> 
> >    - Opened Vs Closed
> 
> Do you want any smoothing applied to this graph? Are you interested in
> "fixed", or just "closed"?
> 
> >    - Tickets per Engineer (and their status)
> 
> You are just interested in the open tickets assigned to each engineer,
> rather than the number they are closing or similar?
> 
> You want this in a graph form as well?
> 
> Are you interested in historical data?
> 
> 
> Do you have any constraints on the freshness of the data displayed?
> Are there any privacy concerns?
> Are there any constraints on how the graphs would be distributed (this
> may impact what technology is used to draw the graphs).
> 
> Thanks,
> 
> James
> 
> 
From: James Westby <james.westby@xxxxxxxxxx>
Subject: Re: [proposal] New Stakeholder Proposal: Metrics for Launchpad Tickets
To: Mounir Bsaibes <mounir.bsaibes@xxxxxxxxxx>
Cc: Michael Hope <michael.hope@xxxxxxxxxx>
Bcc: jw+debian@xxxxxxxxxxxxxxx
In-Reply-To: <AANLkTiko4hWuX3B_cbTs2FbrV6mAzSW99n6sA3YtEToV@xxxxxxxxxxxxxx>
References: <AANLkTiko4hWuX3B_cbTs2FbrV6mAzSW99n6sA3YtEToV@xxxxxxxxxxxxxx>

On Fri, 10 Dec 2010 14:45:55 -0600, Mounir Bsaibes <mounir.bsaibes@xxxxxxxxxx> wrote:
> Subject: [Proposal] Metrics for Launchpad Tickets (bugs).
> 
>   Stakeholders: Mounir Bsaibes, Michael Hope and all tech leads
>   Deadlines: After completing blueprints reports ( otherwise ASAP !).
>   Estimated work: 2 weeks
>   Contact: Mounir Bsaibes
>   Summary: In order to correctly assess and track engineers' workload
> and in order to monitor potential risks to the project,
>   it is necessary to have some metrics that represent the bugs
> assigned to each engineer and each Engineering Unit
>   These metrics can be:
> 
> 
>    - Tickets Vs Time
>    - Age of tickets
>    - Opened Vs Closed
>    - Tickets per Engineer (and their status)
Non-text part: text/html