I was thinking that the OpenStreetMap booksprint wasn't so different from the Open Media Culture "booksprint" we had in Finnish earlier this year. None of the participants had ever participated in a booksprint by English FM, so we were just doing what seemed to work for us. The difference was that the Open Media Culture manual was a project of a few weeks, we had several live sessions and a lot of the writing was done at home, while OpenStreetMap was squeezed into three days. But the interaction was pretty much the same. Both of these were pretty painless, there were no serious arguments about the table of contents or anything like that. <br>
<br>I don't know about the role, since I was mostly just writing and doing minor editing without being a part of the software team, I was probably filling the professional role of a "Crowdsourced Non-Random Character String Generator". Although I took some screenshots too, so I was also filling the role of an "Artistic Screenshotography Director". <br>
<br>Regards<br>Tomi<br><br><div class="gmail_quote">2011/10/24 helen varley jamieson <span dir="ltr"><<a href="mailto:helen@creative-catalyst.com">helen@creative-catalyst.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
what is interesting for me is that the booksprint model breaks open traditional methods for book production and offers the possibility for different processes, according to the strengths of the collaborators. a key task of the facilitator is to observe the group then subtly or overtly get people to work on the particular things that they can do best. i've gone in to a sprint as a proofreader but ended up doing all kinds of other things as well, from structure & editing to writing. the combination of the need to just get stuck in & get the job done, along with the flexibility to put down one task & pick up another, means that you don't lose time struggling with something - you change to something you can do better and allow someone else to bring their perspective to whatever you were struggling with.<br>
<br>
this does result in a broad range of voices within one book, which isn't desirable according to traditional book production methods; but within a networked, open source environment, what it says to me is that this is a book that was created by a community & that has the richness of that community embedded within it. it's also never "finished" in the finite sense of traditional publishing; it can be updated and improved on an ongoing basis.<br>
<br>
i think we will evolve new "roles" within the book sprint methodology & that at this stage it's important to be as open as possible about how it can be.<br>
<br>
h : )<div><div></div><div class="h5"><br>
<br>
On 24/10/11 6:56 AM, <a href="mailto:adam@flossmanuals.net" target="_blank">adam@flossmanuals.net</a> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Just landed in frankfurt. I think we are talking in fundamentally<br>
different languages andy. I don't challenge the importance of an editor at<br>
a publisher like oreilly. I do challenge that role in a book sprint.<br>
Adam<br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Had a day to think about editing and group writing...<br>
<br>
FLOSS Manuals has shown some pretty surprising things about group<br>
development. It shows that cooperating amateur authors can produce<br>
long content. Wikipedia, in contrast, shows that they can produce a<br>
lot of content, but in relatively short pages. The other achievement<br>
FLOSS Manuals is striving for, as I understand it, is long content<br>
that's cohesive and builds from start to finish, like good books<br>
traditionally do. That's where you have to measure your output against<br>
the top authors and editors. I admit, lots of traditionally published<br>
books lack cohesion and don't build well. But we want great results,<br>
not average results.<br>
<br>
I think you've shown that the cooperating authors can present content<br>
from the reader's point of view. They can choose relevant topics and<br>
arrange them in a reasonable order. They can even eliminate most of<br>
the redundancy that tends to insert itself when many people write at<br>
the same time. But I don't believe you've shown that they can do all<br>
the things I do as editor, such as make sure introductory material<br>
appears in the right place, justify new material to make readers see<br>
its relevance, and highlight the most important concepts (which are<br>
often implicit). In short, there's kind of a high-level overview of<br>
the manual that is more likely to come from an editor than from<br>
authors (or from tech reviewers, as I noticed at O'Reilly). This is<br>
why I noticed lots of scattered problems along those lines in the<br>
second edition of the CiviCRM manual after it was finished, although<br>
it was still an impressive product.<br>
<br>
Andy<br>
______________________________<u></u>_________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.flossmanuals.net" target="_blank">Discuss@lists.flossmanuals.net</a><br>
<a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/<u></u>listinfo.cgi/discuss-<u></u>flossmanuals.net</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.flossmanuals.net" target="_blank">Discuss@lists.flossmanuals.net</a><br>
<a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/<u></u>listinfo.cgi/discuss-<u></u>flossmanuals.net</a><br>
<br>
</blockquote>
<br>
<br></div></div><font color="#888888">
-- <br>
______________________________<u></u>______________________________<br>
<br>
helen varley jamieson: creative catalyst<br>
<a href="mailto:helen@creative-catalyst.com" target="_blank">helen@creative-catalyst.com</a><br>
<a href="http://www.creative-catalyst.com" target="_blank">http://www.creative-catalyst.<u></u>com</a><br>
<a href="http://www.avatarbodycollision.org" target="_blank">http://www.<u></u>avatarbodycollision.org</a><br>
<a href="http://www.upstage.org.nz" target="_blank">http://www.upstage.org.nz</a><br>
______________________________<u></u>______________________________</font><div><div></div><div class="h5"><br>
<br>
______________________________<u></u>_________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.flossmanuals.net" target="_blank">Discuss@lists.flossmanuals.net</a><br>
<a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/<u></u>listinfo.cgi/discuss-<u></u>flossmanuals.net</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Best Regards<br>Tomi Toivio<br>Open Source Coordinator<br><a href="http://fi.flossmanuals.net/" target="_blank">http://fi.flossmanuals.net/</a><br><a href="mailto:tomi@flossmanuals.net" target="_blank">tomi@flossmanuals.net</a><br>
+358445488856<br>