资 源 简 介
When working in teams, I find it important that developers check in often, and in small chunks to avoid a lot of merging conflicts.
Also it is important that they feel responsible that what they check in works!
When using Cruise Control (.Net) the definition of "works" is of course a green build.
So what this program does is to calculate a score for each developer on how well he follows that pattern.
I made the initial program when working professionally in a project where developers simply had not learned how to work as a team. Members sat with huge check-outs for days or even weeks, making a lot of changes at a time, when in fact the work could have been broken into very small slices.
Also, when the cc build turned red, no one felt responsible to fix it, making cc useless as no one cared. This also made fixing a build harder, since someone could suddenly check in new (possibly erraneous code), while someone else was tugging his hair off to fix the build.
