Hi all,<div>I step back too. </div><div>I don't want to rise problems or whatever, and I think that LOC can decide what they think is better, and.... after all its their conference ;-)</div><div><br></div><div>I have already clearly stated my point of view, and I have just to add that in Denver the Journal was the same that is proposed for Nottingam (TGIS) and in my opinion publishing 6 months after the conference is not a drama.</div>
<div><br></div><div>My little 1 cents..</div><div>Maxi</div><div><br></div><div><br></div><div> but just remind that the conference of Sept. 2013 in my opinion should present work done in 2013 an<br><br><div class="gmail_quote">
On Mon, Jan 28, 2013 at 4:22 PM, Jeff McKenna <span dir="ltr"><<a href="mailto:jmckenna@gatewaygeomatics.com" target="_blank">jmckenna@gatewaygeomatics.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Jo,<br>
<br>
Indeed I fully agree with you.<br>
<br>
There seemed to be some confusion on past vs present. My goal was only<br>
to clear that up.<br>
<br>
I'll step back and let the Academic committee decide on all that.<br>
<br>
-jeff<br>
<div class="im"><br>
<br>
<br>
On 13-01-28 10:59 AM, Jo Cook wrote:<br>
> Hi Jeff and the rest of the list,<br>
><br>
> I'm speaking from a position of ignorance about this, but surely the<br>
> academic track submission process will need to change from year to year<br>
> depending on the journal that papers are to be submitted to? Surely the<br>
> process is driven mainly by the demands and deadlines of the journal,<br>
> rather than any arbitrary date chosen by a committee?<br>
><br>
> I think the only way you could set the dates and process in stone would<br>
> be to guarantee publication in the same journal each year (as well as<br>
> the OSGeo journal).<br>
><br>
> Happy to be corrected on any of these points though!<br>
><br>
> Jo<br>
><br>
><br>
><br>
> On Sun, Jan 27, 2013 at 4:03 PM, Jeff McKenna<br>
</div>> <<a href="mailto:jmckenna@gatewaygeomatics.com">jmckenna@gatewaygeomatics.com</a> <mailto:<a href="mailto:jmckenna@gatewaygeomatics.com">jmckenna@gatewaygeomatics.com</a>>><br>
<div><div class="h5">> wrote:<br>
><br>
> Here's another thought for our "lessons learned" wiki: For the next<br>
> FOSS4G event, the first step in the Academic submission process could be<br>
> an "extended abstract" due for something like Feb 1st. How I am coming<br>
> up with that idea? On this past Friday was a deadline for a "CoastGIS"<br>
> event, and all presentation abstracts were to follow an "extended"<br>
> abstract template (min 2 pages max 4 pages, including listing your<br>
> peer-reviewed sources); selected extended abstracts will be invited to<br>
> submit full papers. Could this be the first step someday for a FOSS4G<br>
> Academic track? I've leave that to the FOSS4G Academic leaders to<br>
> discuss (again I am not one of those leaders).<br>
><br>
> For the record here was the "extended" abstract template (sorry for the<br>
> M$ file, I have no relation to this event):<br>
> <a href="http://coinatlantic.ca/coastgis2013/docs/CoastGIS_2013_Extended_Abstract_Template.doc" target="_blank">http://coinatlantic.ca/coastgis2013/docs/CoastGIS_2013_Extended_Abstract_Template.doc</a><br>
><br>
> Thanks for listening.<br>
><br>
> -jeff<br>
><br>
><br>
><br>
> On 13-01-27 11:49 AM, Jeff McKenna wrote:<br>
> > Hello Barend, Venka, Andy, Max, Nick, and Puneet,<br>
> ><br>
> > First I want to thank the Academic chairs Barend and Franz-Josef for<br>
> > volunteering for the management of the difficult process of the<br>
> > selection of papers for the FOSS4G 2013 event. I am impressed by<br>
> their<br>
> > passion and dedication to getting papers published in the Transactions<br>
> > in GIS journal, this is very important.<br>
> ><br>
> > I want to make a strong reminder to all of the FOSS4G 2013 local<br>
> > committee (academic or otherwise) to make sure to be adding to your<br>
> > "Lessons Learned" wiki page as you travel down this path (the time<br>
> to be<br>
> > adding thoughts is now not later when you have forgotten: as a<br>
> > documenter, I know those that say "oh I'll do that later" never<br>
> ever do,<br>
> > ever). Please begin writing your thoughts for 2013 at:<br>
> > <a href="http://wiki.osgeo.org/wiki/FOSS4G_2013_Lessons_Learned" target="_blank">http://wiki.osgeo.org/wiki/FOSS4G_2013_Lessons_Learned</a> You will<br>
> notice<br>
> > that is is blank for 2013. These thoughts are very important to<br>
> share,<br>
> > as future local committees will be reviewing these (take a look at all<br>
> > the wonderful lessons learned from previous events linked from that<br>
> > page, really wonderful to have). Thank you, and future event<br>
> committees<br>
> > will thank you.<br>
> ><br>
> > Regarding the Academic track call for papers for 2013, of course<br>
> we must<br>
> > respect the local committees decisions. I am listening to Barend's<br>
> > thoughts, as well as long-time FOSS4G academic leaders like Venka and<br>
> > Massimiliano. I feel that the 2013 committee could consider their<br>
> > feedback, and possibly extend the deadline by a month to March<br>
> 1st. It<br>
> > would give researchers some breathing room to prepare their papers,<br>
> > which, yes is earlier than past FOSS4G events but if we all want<br>
> papers<br>
> > within these journals we must respect these early deadlines. Of<br>
> course<br>
> > the local committee doesn't have to make an extension, I am only<br>
> making<br>
> > a suggestion.<br>
> ><br>
> > Another idea, or reminder, I have for the committee is to be as<br>
> open as<br>
> > possible; for example, there is a mailing list setup just for FOSS4G<br>
> > Academic discussions (I believe this was probably last used in<br>
> 2010, but<br>
> > it is there to discuss openly with academic FOSS4G leaders). Again,<br>
> > there is no official requirement for local committees to use these<br>
> > mailing lists.<br>
> <a href="http://lists.osgeo.org/mailman/listinfo/foss4g-academic" target="_blank">http://lists.osgeo.org/mailman/listinfo/foss4g-academic</a><br>
> ><br>
> > Finally, I just now went back to examine the FOSS4G 2011 Academic<br>
> Track<br>
> > process used. In fact that year I was also on the Academic Selection<br>
> > committee, which was led wonderfully by the hard-working Rafael<br>
> Moreno.<br>
> > On February 1st a "Call for Papers" was released for the Academic<br>
> > track, and the call was actually for abstracts (yes google<br>
> archives can<br>
> > trick you sometimes, as the title was for "Call for Papers" but if you<br>
> > read the release the first step was abstract submission). The<br>
> deadline<br>
> > for academic abstracts was April 15th. We received approximately 60<br>
> > academic abstracts (note that the day before the deadline, on April<br>
> > 14th, we only had 9 submissions so far - Paul Ramsey would be nodding<br>
> > his head at this, as this is very common, the many submitted right at<br>
> > the deadline). Rafael then instructed us to have our abstract<br>
> rankings<br>
> > back to him by May 16th. From those rankings the plan was: the<br>
> top 11 +<br>
> > 2 (backup) were invited to submit a paper for TGIS; the next 11 + 2<br>
> > (backup) were invited to submit a paper for the OSGeo Journal.<br>
> > According to my email archives the deadline for those full papers was<br>
> > July 30th; and we received a total of 17 full papers. The rest<br>
> > (history) should be discussed on the FOSS4G Academic list with the<br>
> > academic leaders (I am not one), but I hope this little history<br>
> summary<br>
> > helps the 2013 committee move forward.<br>
> ><br>
> > Again thanks for the hard work of the 2013 local committee.<br>
> ><br>
> > And thank you all for your FOSS4G passion (Puneet was right to put it<br>
> > all in perspective).<br>
> ><br>
> > -jeff<br>
> > OSGeo President<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > On 13-01-25 7:26 AM, <a href="mailto:b.j.kobben@utwente.nl">b.j.kobben@utwente.nl</a><br>
</div></div><div><div class="h5">> <mailto:<a href="mailto:b.j.kobben@utwente.nl">b.j.kobben@utwente.nl</a>> wrote:<br>
> >> Dear Venka and Massimiliano,<br>
> >><br>
> >> I feel we have to defend the Foss4G2013 AT a bit here (as AT<br>
> co-chairs we<br>
> >> should ;-)<br>
> >><br>
> >> It is actually not true that "Previous FOSS4G's had abstract<br>
> review by the<br>
> >> academic committee<br>
> >> and selected authors were asked to submit full papers closer to the<br>
> >> conference dates."<br>
> >> Both in the 2010 and 2011 conferences we had submission of full<br>
> papers,<br>
> >> not abstracts.<br>
> >><br>
> >> The reason for this is that academics nowadays need to publish,<br>
> if we want<br>
> >> or not, and that means we have to offer a possibility of official<br>
> >> publishing for the AT papers. The only way to achieve that is<br>
> have journal<br>
> >> outlets secured well beforehand and for that you need to set up a<br>
> "Journal<br>
> >> Type" submission and reviewing system, which means selection of full<br>
> >> papers. Having to first select promising abstract, then ask these<br>
> people<br>
> >> to write full papers, and then have these properly peer-reviewed, all<br>
> >> before the conference publication deadline, would mean we'd need<br>
> an even<br>
> >> earlier deadline.<br>
> >> This by the way is nowadays accepted academic practice at<br>
> conferences that<br>
> >> offer Jopurnal publication outputs.<br>
> >><br>
> >> I agree that 7 months before the conference seems like a very early<br>
> >> deadline, but for the reviewing process, the editing and<br>
> processing of<br>
> >> accepted papers and preparation of manuscripts for publication, it<br>
> >> actually is quite a tight time table. Note that the advantage is<br>
> that if<br>
> >> your paper is accepted, you are assured of it being actually<br>
> published at<br>
> >> the conference date, something may academics are keen for...<br>
> >><br>
> >> Note also that the normal (non AT) tracks at Foss4G continue to offer<br>
> >> submission and reviewing based on abstracts.<br>
> >><br>
> >> We will have this year (as in previous years) an Academic<br>
> Committee. These<br>
> >> are the people that will be asked to do the full paper reviewing,<br>
> and we<br>
> >> have just this week invited candidates and have asked them to<br>
> agree to do<br>
> >> this important task. The list will appear on the site once the<br>
> reviewing<br>
> >> process starts.<br>
> >><br>
> >> I hope this answers some of your questions.<br>
> >><br>
> >><br>
> >> For further questions, comments and remarks, please don't hesitate to<br>
> >> contact the Academic Track co-chairs:<br>
> >><br>
> >> * Franz-Josef Behr (Stuttgart University of Applied Sciences):<br>
> >> <a href="mailto:franz-josef.behr@hft-stuttgart.de">franz-josef.behr@hft-stuttgart.de</a><br>
</div></div>> <mailto:<a href="mailto:franz-josef.behr@hft-stuttgart.de">franz-josef.behr@hft-stuttgart.de</a>><br>
<div class="im">> >> * Barend Köbben (ITC-University of Twente): <a href="mailto:kobben@itc.nl">kobben@itc.nl</a><br>
</div>> <mailto:<a href="mailto:kobben@itc.nl">kobben@itc.nl</a>><br>
<div class="HOEnZb"><div class="h5">><br>
><br>
_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.osgeo.org">Discuss@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/discuss" target="_blank">http://lists.osgeo.org/mailman/listinfo/discuss</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><b style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12px">Massimiliano Cannata</b><br><p style="margin:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="color:gray;font-size:9pt">Professore SUPSI in ingegneria Geomatica</span></p><p style="margin:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><span style="color:gray;font-size:9pt">Responsabile settore Geomatica</span></p>
<p style="margin:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><span style="color:gray;font-size:9pt"><br></span></p><p style="margin:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="color:gray;font-size:9pt">Istituto scienze della Terra</span></p><p style="margin:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"></p><p style="margin:0px">
<span lang="IT" style="font-size:9pt;color:gray">Dipartimento ambiente costruszione e design</span></p><p style="color:rgb(0,0,0);font-family:arial;font-size:small;margin:0px"><span lang="IT" style="font-size:12px"><font color="#808080" face="arial, sans-serif">Scuola universitaria professionale della Svizzera italiana</font></span></p>
<p style="color:rgb(0,0,0);font-family:arial;font-size:small;margin:0px"><span style="color:gray;font-size:9pt;font-family:arial,sans-serif">Campus Trevano, </span><span style="color:gray;font-size:9pt;font-family:arial,sans-serif">CH - 6952 Canobbio</span></p>
<p></p><p style="margin:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><span lang="IT" style="font-size:9pt;color:gray">Tel. +41 (0)58 666 62 14<u></u><u></u></span></p>
<p style="margin:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><span lang="EN-US" style="font-size:9pt;color:gray">Fax +41 (0)58 666 62 09<u></u><u></u></span></p><p style="margin:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span lang="EN-US" style="font-size:9pt"><a href="mailto:massimiliano.cannata@supsi.ch" target="_blank">massimiliano.cannata@supsi.ch</a></span></p><p style="margin:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<u><span lang="EN-US" style="font-size:9pt;color:blue"><span style="color:blue"><a href="http://www.supsi.ch/ist" target="_blank">www.supsi.ch/ist</a></span></span></u></p>
</div>