<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BLOCKQUOTE type="cite"><SPAN class="gmail_quote">On 6/2/07, <B>Paul Ramsey</B> <<A href="mailto:pramsey@refractions.net"> pramsey@refractions.net</A>> wrote:</SPAN><BLOCKQUOTE class="gmail_quote" style="border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); margin-top: 0pt; margin-right: 0pt; margin-bottom: 0pt; margin-left: 0.8ex; padding-left: 1ex; ">... that some volunteer will step up and say "*I* will<BR style="">ensure all the academic participants go home happy.") <BR style=""></BLOCKQUOTE></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Okay Paul, I'll bite - but I'll still leave room for others to raise their hands. :)</DIV><BR><DIV><DIV>On 2-Jun-07, at 8:11 AM, Daniel Ames wrote:</DIV><BLOCKQUOTE type="cite">OSGeo Journal already has an ISBN (right?) and publishing proceedings in our own journal probably makes sense. Perhaps conference attendees are just encouraged to submit their papers through the OSGeo Journal's existing processes, <BR></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I agree with the idea of having the Journal as a venue for publishing the proceedings. We can put select papers through the peer review process. We can consider how to also handle all the others that might be ready to publish. I look at this as a very convenient way to suddenly have lots of Journal content for our 3rd issue and also help the conference.</DIV><DIV><BR class="khtml-block-placeholder"></DIV>I assume we'd only need to take some of the presentations whose authors put together a more formal paper - not just reprint presentation files. Will that meet the needs? How much information do people need ahead of time? <DIV><BR class="khtml-block-placeholder"><DIV><DIV><DIV>Yes, OSGeo Journal has an official ISSN (it's like the ISBN but is for periodicals/serials, not books).</DIV><DIV><BR class="khtml-block-placeholder"></DIV></DIV></DIV></DIV></DIV>Tyler<BR></BODY></HTML>