First evaluation result
I have a (pretty terrible) result: with the way things stand right now, tracSnap is able to predict 16% of the people who comment on tickets related to Hadley model defects.
How I arrived at this result:
- Jon gave me a list of tickets (defects) that he was able to associate with a specific revision of the repository.
- For each such ticket, I looked at the files that were involved in its associated revision, and used tracSnap to get the "experts" for those files.
- I compared this list of experts with the people who actually helped to fix the defect, and checked to see if they are the same people.
As of yet, I've only looked at the prediction rate using the "experts", and not the ticket reporter's "suggested contacts". I suspect that both analyses will produce similar results, since the suggested contacts and experts are not independent (contact suggestions rely partially on the expertise calculations).
16%... lame.
-- Edit: November 24 --
The 16% was the recall percentage. Precision seems to be 63%. That's a happier number.

2 Comments:
Hmm... Is this 16% precision or recall? (And what's your result for the other metric?)
Using merges to broaden who's considered an expert is a neat idea --- if it dramatically increases the hit rate, what does that tell you about the underlying software development process? If it has little or no effect on the hit rate, what does that tell you?
Post a Comment
<< Home