Changes

He also suggests that such data would allow a community to better understand itself from a developer's perspective. An example he gives surrounds the unknown period of time a developer has to wait after submitting a patch but before it gets reviews. Since this process is not standardized, it often leads to frustrations which might convert to quits. According to Eaves, average wait times will become self-apparent, and if they begin to slide in individual cases, then moderators could be chastized for their delays. In this way, community data can be used to introspection to find efficiencies and standards.

Finally Eaves gives an example of how open data has helped a client of his in the open government model. The city of Los Angeles recently made restaurant inspection data open, and required it to be posted on every establishment's door (much like in Toronto.) According to Eaves, this led to restaurants with poor records receiving fewer customers and those with better records a higher number. In other words, good restaurants were rewarded and poor restaurants punished. He also noted that there has been a decline in the number of patients that visit the emergency room with food poisoning, a fact that he says is likely grounded in this freeing of information.