Nothing about setting up a wiki in Drupal... The review doesn't bring it up, and as far as I can tell from the online table of contents, the book doesn't either. That was sort of surprising, for a book about community sites.

-Karl Fogel

For some statistical evidence (built on a very small sample size) that code review is worth it, see this section of a chapter from O'Reilly Media's book Beautiful Teams:

    http://www.red-bean.com/kfogel/beautiful-teams/bt-chapter-21.html#gumption-sink

That section is not about code review per se (it's about how a seemingly trivial interface decision affected code review), but it includes some code review stats from two projects, and discusses how frequently one project's code review catches mistake from previous changes.

(Disclaimer: I wrote the chapter, but it seems pertinent enough to this discussion to be worth posting.)

--Karl Fogel

Andy Oram, an editor at O'Reilly, wrote this essay on Wolfram Alpha and how it fits (or doesn't fit) into the "tech-splicing" revolution:

Results from Wolfram Alpha: All the Questions We Ever Wanted to Ask About Software as a Service

(Disclaimer: Andy is my editor. But it's a good article; check it out.)

A lot of free software documentation is released under free licenses these days. Was this? Or maybe a non-free but still liberal license like CreativeCommons Attribution-NonCommercial or something?

(Might be good to tweak the Slashdot book review guidelines to make stating the license a standard part of these reviews...)