[I apologize for odd quoting, but I dislike sending html emails]<br>"I do like the idea of developing a table of contents first and
backfilling it, though. I would amend the process, however, to avoid
the WikiBloat that seems to inevitably follow when documentation
projects get too open. Instead of Wikifying it, I'd suggest instead
that a "call for proposals" be put on the mailing list. "I'm working
on a chapter dealing with database programming. I need to know how to
do <insert whatever> in Haskell. Could anybody interested in
helping please submit some commented, functioning code for possible
inclusion?" Then the submissions could be made by email (and possibly
even discussed on-list) and the editor/author of the book can take an
executive decision and choose one if there are competing camps."<br><br>Instead of having someone work in solitude with occasional mailings back and forth on the list, I would rather have an open wiki for the collection of ideas from everyone. Then, if you really wanted, a single person can use those to create an 'editor edition' page that is only editable by them. Best of both worlds, or do you see it differently?
<br><br>-- <br>Joe Re