Comment by quadrifoliate
4 years ago
If you don't want the pointy-haired bosses to start measuring productivity by number of commits, start with not doing so yourself.
Commit count is largely meaningless and a low-effort way to fling around "contribution" numbers. For example, large commit numbers could be a reflection of a specific company's internal conventions around making a larger number of small changes as their own commit.
Now it's certainly plausible to me that Google is a much more major contributor to Kubernetes than Apple, but you need better numbers for showing that. For example, which companies have contributed to designing and implementing the major features in the last 5 releases?
Yeah, I'm thinking of some colleagues that can't remember any syntax that do 20 commits on the same line of code and don't clean it up.