[sldev] sljirastats.com Linden Metrics Report

Rob Lanphier robla at lindenlab.com
Wed Apr 16 13:40:06 PDT 2008


Hi Gigs,

This is great information.  Thanks for compiling it.

A couple of questions/comments below:

On 4/16/08 12:02 PM, Jason Giglio wrote:
> "Open" bugs have been on a steady climb.  It started at 1547 when
> sljirastats.com began collecting data, and is now at 2717.   This means
> we are averaging 8.6 additional unresolved bugs per day.  This is after
> subtracting fixed and resolved issues.  This number is a critical
> metric; Linden Lab is falling more and more behind every day.
>   

How does this compare to other open source and public projects?  My 
suspicion is that almost every active open source project experiences 
net positive growth in number of open bugs.  I'd like to make sure we're 
not being measured against an unreasonably high standard.

We have a resolution internally called "someday maybe", which is one I'm 
personally not a fan of (since the issue isn't "resolved", just 
acknowledged as a wart we're going to have to live with for a while).  
We've recently discussed making a matching PJIRA resolution, and 
concluded that a) we can't, because we still want to allow votes and b) 
we'd get a public flogging over it.  The conclusion of that discussion 
is to represent that as "small" priority, possibly renaming "small" to 
"someday maybe", or adding a new "someday maybe" priority, and I'm 
hoping we can actually change our internal usage to match.

> SVC-472 and SVC-85 remain the most hated bugs, for most of the time that
> sljirastats has existed.
>   

Hmmm....these are also somewhat subjective without clear victory 
conditions.  While I'm guessing the team will acknowledge that these 
aren't yet running at an acceptable baseline, it also strikes me that 
these both describe symptoms with multiple and ever-changing causes of 
failure that will probably always be with us in some form from time to 
time.  For both of these, I think we need to establish a victory 
condition that causes these issues to be closed and stay closed, to the 
point where a new issue gets opened if a problem with the same symptom 
occurs.  Otherwise, these will automatically be at the top of the list 
every time they get reopened, despite the fact that other issues may 
actually be more pressing.

What are good victory conditions for these?

Rob

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : http://lists.secondlife.com/pipermail/sldev/attachments/20080416/1b92083e/signature.pgp


More information about the SLDev mailing list