[I apologize for odd quoting, but I dislike sending html emails]<br>&quot;I do like the idea of developing a table of contents first and
backfilling it, though.&nbsp; I would amend the process, however, to avoid
the WikiBloat that seems to inevitably follow when documentation
projects get too open.&nbsp; Instead of Wikifying it, I&#39;d suggest instead
that a &quot;call for proposals&quot; be put on the mailing list.&nbsp; &quot;I&#39;m working
on a chapter dealing with database programming.&nbsp; I need to know how to
do &lt;insert whatever&gt; in Haskell.&nbsp; Could anybody interested in
helping please submit some commented, functioning code for possible
inclusion?&quot;&nbsp; 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.&quot;<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.&nbsp; Then, if you really wanted, a single person can use those to create an &#39;editor edition&#39; page that is only editable by them.&nbsp; Best of both worlds, or do you see it differently?
<br><br>-- <br>Joe Re