<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Barry,<div><br></div><div>does this mean you don't have enough trust in the community voting that they will filter out anything inappropriate?</div><div><br></div><div>I see this as an unnecessary and confusing step.</div><div><br></div><div>Best regards,</div><div>Bart</div><div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; ">-- <br>Bart van den Eijnden<br>OSGIS - <a href="http://osgis.nl">http://osgis.nl</a></span>
</div>
<br><div><div>On May 22, 2013, at 4:50 PM, Barry Rowlingson <<a href="mailto:b.rowlingson@lancaster.ac.uk">b.rowlingson@lancaster.ac.uk</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Wed, May 22, 2013 at 2:49 PM, Bart van den Eijnden <<a href="mailto:bartvde@osgis.nl">bartvde@osgis.nl</a>> wrote:<br><br><blockquote type="cite">But apparently the selection committee filtered out abstracts based on the<br>words open and or free, which seems a weird and error-prone approach to me.<br></blockquote><br> We did *not* purely filter out based on words.<br><br> We looked at the title, short abstract, and long abstract. If from<br>those items we could not see a free/open-source, open-data, or<br>geospatial angle, we *thought carefully* about whether that should be<br>included in the conference.<br><br><blockquote type="cite">My second talk was about GeoExt and since I thought since everybody knows<br>GeoExt is about open source, I did not mention those words explicitly in my<br>abstract.<br></blockquote><br> Yes, we have enough expertise on the panel to know our open source<br>packages. Anything we didn't know, we looked up. However we can't look<br>up something omitted from an abstract...<br><br><blockquote type="cite">Someone had a great abstract on big data, but it wasn't selected<br>because it can be used with both open source software and closed source<br>software, and it's not about open data specifically.<br></blockquote><br> An abstract that doesn't mention any open geospatial technology could<br>well be about doing analysis in ArcGIS or Oracle Spatial. Its not the<br>committee's job to second-guess the presenter or ask the presenter for<br>clarification - the abstract is space enough to provide clarity and<br>full details.<br><br><blockquote type="cite">My personal opinion is<br>that if the general public wants to see this talk, it should not matter if<br>the abstract contains the words free or open.<br></blockquote><br> Again, we did not filter on the words. We took the totality of the<br>submission and checked appropriateness for the Free and Open Source<br>for Geospatial Conference, amongst the other criteria.<br><br><blockquote type="cite">Also, if this is filtering would be done, it should be done *prior* to the<br>community voting phase IMHO.<br></blockquote><br> Personal opinion: there's no point - the outcome will be the same, it<br>will just require a committee to review everything before and after<br>the community voting. There were very few inappropriate submissions.<br><br><blockquote type="cite">Can the selection committee elaborate on the approach they used?<br></blockquote><br> I think we've discussed this at great lengths on this and other<br>mailing lists. Basically: First pass: include community vote top 100.<br>Second pass: include committee vote top 100 (giving us ~130 included).<br>Discuss, eliminate anything inappropriate. Next pass: include lower<br>ranked community votes. Next: lower ranked committee votes. Check for<br>multiple submissions, similarities with workshop sessions, and make a<br>decision on near-duplicates (which may include rejections, choices, or<br>mergers). Keep going until coffee runs out or all slots filled. We did<br>not run out of coffee.<br><br>I think fuller details will be posted to the lessons learned/cookbook<br>wiki pages.<br><br>Barry<br></blockquote></div><br></div></body></html>