I think this drills down to an important underlying point. Which parties are contributing bits of code into upstream. Isn't that the fundamental friction being expressed?
If Canonical wants to get ahead of the perception problem, they need to be able to track patch flow as well as ticket comment flow. Downstream supplied patched do matter, and may not show up in the the commit stats in the same way that direct developer involvement does. You obviously can't directly compare upstream developer activity done on company time, to volunteer patch submission efforts. So watching how patches come in via a bug tracking interface isn't going to tell the whole story but it may help turn the corner on Canonical's upstream relation issue.