Commenting on the Seastead Book

Notes on previous review guidelines and commenting system:

Editing Guidelines

The destiny of this book is to be self-published for a niche market. While we're happy to hear about spelling/grammar errors and awkward sentences, we do plan to have the manuscript professionally (though cheaply) edited. What's more important is a slightly higher-level viewpoint from people who are part of our niche. So we're looking for things like:

• Does each section feel complete? Have we hit on all the major points? Is there something you really think should go in this section? (Check to see if its anywhere else)
• Are there major technical errors? We've done a lot of reviewing, analyzing, and summarizing fields we're not expert in, so this is quite possible.
• Is our line of reasoning convincing? Given that we can't address every point, have we left out a big one?
• Is the tone appropriate for the material? Were we too technical, too light-hearted, too dry, too ranty, not ranty enough?
• Was it fun to read?

Other suggestions:

• The more specific the criticism the better, and suggestions for improvement are better yet.
• Note that some sections have specific comments for revisers, indicated by { curly braces }.
• We'd prefer not to hear about catchy-but-unproven technologies. There are zillions of them which could potentially be relevant, and describing them is best saved for later editions. Of course, if there is some proven method we missed, let us know.

We understand that revising the whole book is a large task, so feel free to just sign up for a few sections.

Commenting System

This book draft uses the Simple Online Commenting System written by Patri. Most sections of the paper have comment buttons, and clicking them takes you to a page where you can add your comments. We'll be using these comments to help improve the paper. You may also be interested in the guidelines for reviewers.

• You may have to reload comments pages in order to see recently-added comments. You may need to reload paper pages to see updated comment-button numbers.
• Note that the day/week/month links at the top of each page are broken if there has not been a comment on the page in that period.
• Comments may be removed if we feel we've addressed them, decided we aren't going to address them, or think they are inappropriate.
• SOCS is very new code, if you find bugs please email Patri (patri-at-clevername-dot-net) or comment on the SOCS page.
• Text in curly braces {} indicates comments from the authors, both to each other, and posing specific questions to readers.
• { Anything else we should say here? - P}