Re: [RFC] Use cases for 'git statistics'

On Tue, May 13, 2008 at 3:07 PM, Jakub Narebski [off-list ref] wrote:

 And now you apparently forgot to add git mailing list to receipients...

I guess mailinglists are not my thing huh?

 > On Mon, May 12, 2008 at 2:40 PM, Jakub Narebski [off-list ref] wrote:
 > Ah, there is a lot more to this example than I thought. Perhaps this
 > data could all be shown and then, using some "importance" metric per
 > item a "grade" can be calculated?

 Weighting different statistics, bayesian hypotesis/filtering, expert
 system, machine learning... I guess that would be quite a work to do
 it well.  Probably would require to calculate and adjust scoring of code
 (difficulity) and authors (skill), and matching them...

 This is certainly in the "wishlist" scope.

Yeah, I think it would go in the 'c' of 'MoSCoW', but it could be very
useful when done right.

 >>  Details I think need to be provided by maintainer...
 >
 > Do you mean Junio, or the user of the program?

 I mean that all I can provide is speculation.  I'm not, and never was
 a maintainer of OSS project, and I don't know what criteria one use
 (perhaps unvoiced criteria) to decide whether given patch needs to be
 examined more closely, or the cursory browsing should be enough.

I reckon more input from actual maintainers would be needed then.
Junio: aside from the original list with suggestions you provided,
could you shine your light as git maintainer on this?

 I mean, given the code at given version, what happened to this code?
 Filtering "git blame --reverse" by user might be one way of solving it.

It sounds like it would not be too hard to implement' maybe another
'C' in 'MoSCoW' (or perhaps that first 'C' should be a 'W'...)

 What I had in mind here, but didn't explain clear enough, was an
 extension to pickaxe search.  You want to find when current error
 message was created, even if the way of handling it (fprintf vs. die)
 changed, or if code was indented, or was moved.

I'm not familiar with pickaxe, what you suggest sounds like grepping
the content also throughout history?

 Or find all error messages, in the order they were created, for example
 in git case to find ancient error messages and replace it by something
 more user-friendly (or less selective about choosing friends ;-).

I understand what you want, a search for specific content, from old to
new, stopping when you have a match?

 > Interesting article, I think integrating statistics
 > (http://www.statsvn.org/ for example) can be a very powerful tool for
 > project management.

 You meant http://git.koha.org/gitstat/, didn't you? ;-P

I used the former, never tried the latter :).

 Seriously, what I had in mind was to integrate author dates and commit
 dates into project management system scheduling.

I'm not sure what gain that would bring though, as it can only provide
end dates, not 'starting work now' timestamps...

-- 
Cheers,

Sverre Rabbelier