code review thoughts

[Gary Poster]

On Friday, I'm going to ask that we consider trying out a single review
for GUI branches.  Juju core is trying that out, and the dev list had an
interesting thread about it, led by John Meinel.  I'm very open to it:
that's the number of reviews I had on every project prior to the GUI.
Alternatively, maybe we say we must have one review and one qa.  They
can be the same person or divided up.  In any case, we can talk it
through on Friday.

Relatedly, I also saw this link somewhere in the thousands of emails I
slogged through this week:
https://www.ibm.com/developerworks/rational/library/11-proven-practices-for-peer-review/
.

If you haven't clicked through already, I thought it was worth a 60
second scan.  In particular, item 1 seemed like something in particular
to strive for, and item 4 seemed like an interesting idea to ruminate
on.  Item 6 looked familiar....

Gary