Rank developer by touch of file ?

[Cedric Teyton]

Hello,

I was wondering whether BOA allows to focus on certain developers expertise.
For instance, assume i want the top-10 commiters that touched the most Java files. (or even POM.xml files).

My intuition is BOA can handle it somehow, i'm just not familiar enough to answer these questions.

Thank you for you help !

Best,

Cédric Teyton

[Hoan Nguyen]

Hi Cedric,

This Boa program could be a starting point for answering your question.

http://boa.cs.iastate.edu/boa/?q=boa/job/2387

It counts the number of files each committer has touched. Currently in our data, the committers' names are anonymized.

Please refer to the Programming Guide http://boa.cs.iastate.edu/docs/index.php if you want to change the file matching or use other data types to filter the "touch".

Hope this help.

Best,

Hoan

[Robert Dyer]

I believe Hoan gave the wrong URL, here is the correct one:

   http://boa.cs.iastate.edu/boa/?q=boa/job/public/2387

And just to build on what he provided, here is my version:

   http://boa.cs.iastate.edu/boa/?q=boa/job/public/2389

This job computes the top-10 committers.  It is also coded to easily modify what file names you match against (the array 'searchNames' at the top).

The basic intuition is to iterate over each code repository (line 6), then over each revision (line 7), then over each file (line 8), and if a file matches (line 9) any of the provided regex's (line 4) then we increase the count for that particular user.  This is done by emitting their name and a weight of '1' (line 10).  The top aggregator (line 2) then groups by each user's name, sums all their weights, sorts by the total weight, and gives the top (in this case, 10) results.

- Robert

[Robert Dyer]

And here is the same query, but using our visitor syntax:

   http://boa.cs.iastate.edu/boa/?q=boa/job/public/2390

I personally think this is easier to understand! :-)

- Robert

[Robert Dyer]

A couple of minor changes to my previous example:

   http://boa.cs.iastate.edu/boa/?q=boa/job/public/2392

1) I made the match case-insensitive (by lowercasing everything)

2) The searchNames are regex strings, so I escaped the period '.' to make it more correct

- Robert

[Cedric Teyton]

Thank you for being so responsive ! :)

I understand your answers and i think the answer.
Just a last question, i see in your domain-specific type an entry
"Person A unique person's information".

I just wonder what is the relation with the commiter's name you
extract in this query ?

Best,

Cédric

[Robert Dyer]

In my last query, you see in the visitor for the Revision type there is 'rev.author.username'.  In this expression, 'rev' is the Revision, the attribute 'author' gives you a Person (the Person who authored the commit) and the attribute 'username' is from that type Person, giving you that Person's user name.

- Robert