<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi<div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 14 Nov 2016, at 6:31 PM, Yves Jacolin <<a href="mailto:yjacolin@free.fr" class="">yjacolin@free.fr</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hello,<br class=""><br class="">From my first email a lot of good news appear. We have now 4 sponsors so we <br class="">probably ok with the fundings. We need to focus now on the lunch and dinner.<br class=""></div></div></blockquote><div><br class=""></div><div>This is good news! Go French chapter go!</div><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class=""><br class="">While I think that meetings are useful/important to discuss things,<br class="">meetings usually are not the place where much code is produced. Besides,<br class="">with github and mailing lists we have good platforms to discuss issues<br class="">also without a meeting. I think we should concentrate our meeting<br class="">expenses to the two annual global meetings we have - as it is at these<br class="">meetings where most core devs meet at once. It is also quite unlikely<br class="">that most core devs can come to much more than two meetings in a year,<br class="">because they are either too far away or have contract work to do.<br class=""></blockquote>Well, I kindly disagree with this. Meeting could be a good way to get much <br class="">code produced.<br class=""></div></div></blockquote><div><br class=""></div><div>I'm in the middle : I don't think we want to get into the position where we are being continually asked for funds for things that are better managed at local country level. But I also don't think we should be too rigid, and if it looks like using QGIS funds will accelerate or facilitate development work through a sprint, it should be at least considered. Having a bit of discretionary funding set aside would be useful for future budgets.</div><div><br class=""></div><div>Regards</div><div><br class=""></div><div>Tim</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">Let see after the 13rd of december :)<br class=""><br class="">Y.<br class=""><br class=""><blockquote type="cite" class="">This is my personal opinion.<br class=""><br class="">Andreas<br class=""><br class="">On 2016-11-10 17:36, Tim Sutton wrote:<br class=""><blockquote type="cite" class="">Hi Yves<br class=""><br class=""><blockquote type="cite" class="">On 07 Nov 2016, at 7:27 PM, Yves Jacolin <<a href="mailto:yjacolin@free.fr" class="">yjacolin@free.fr</a>> wrote:<br class=""><br class="">Dear PSC,<br class=""><br class="">Several french(-swiss) companies are interested to organized a code<br class="">sprint<br class="">before the end of the year.<br class=""><br class="">As said in a previous mail last week, we (OSGeo-fr) are organizing an<br class="">user<br class="">meeting on the 1st and 2nd of December in Montpellier. Unfortunately we<br class="">can't organized a code sprint there and decided to organized it<br class="">independently of the user meeting.<br class=""><br class="">This code sprint would take place in Lyon either in 29-29 November or<br class="">12-13<br class="">December in regards of the feedback of the community [1].<br class=""><br class="">We (Camptocamp, 3Liz, Oslandia) will focuse on QGIS v3, especially QGIS<br class="">Server (but other developers are welcome to work on other parts).<br class=""><br class="">We asked support from OSGeo-fr and still waiting the answer. We would<br class="">like<br class="">with this email to formalize the QGIS Code sprint organisation and<br class="">discuss the possibilities to QGIS org to fund some developer trip if<br class="">needed.<br class=""><br class="">This is quiet short to organized this so we will focused on lunch and<br class="">dinner and location, no more (well if we find a location for a nice<br class="">dinner it will be great). We will share a call for sponsorship program<br class="">quickly this week.<br class=""><br class="">Régis and I are the current organizer team and official contacts. Régis<br class="">will post here the wiki page for the code sprint so you can register<br class="">soon.> <br class=""></blockquote>Sorry from my side also for the lack of feedback sooner. I think<br class="">everything you present in the email sounds fine (and great to see local<br class="">sprint efforts). In terms of funding, Andreas would be better informed if<br class="">we have any spare funds but there is also the larger question of if when<br class="">and how we should fund local events. Personally I think first priority<br class="">should go to our twice yearly international events, but I think it would<br class="">not be unreasonable to plan some part of our budget to ad hoc regional<br class="">events on a first come first served basis until the budget is used up.<br class="">Perhaps this is something we can incorporate into our next annual budget<br class="">Andreas?<br class=""><br class="">Regards<br class=""><br class="">Tim<br class=""><br class=""><blockquote type="cite" class="">Thanks,<br class=""><br class="">Y.<br class="">[1]<br class=""><a href="https://framadate.org/qgisCodeSprintv3-2016_____________________________" class="">https://framadate.org/qgisCodeSprintv3-2016_____________________________</a><br class="">__________________ Qgis-psc mailing list<br class="">Qgis-psc@lists.osgeo.org<br class="">http://lists.osgeo.org/mailman/listinfo/qgis-psc<br class=""></blockquote></blockquote><br class="">Links:<br class="">------<br class="">[1] <a href="http://QGIS.org" class="">http://QGIS.org</a><br class="">[2] <a href="http://kartoza.com/" class="">http://kartoza.com/</a><br class="">[3] <a href="http://freenode.net" class="">http://freenode.net</a><br class=""></blockquote><br class="">_______________________________________________<br class="">Qgis-psc mailing list<br class=""><a href="mailto:Qgis-psc@lists.osgeo.org" class="">Qgis-psc@lists.osgeo.org</a><br class="">http://lists.osgeo.org/mailman/listinfo/qgis-psc</div></div></blockquote></div><br class=""><div class="">
<span><img height="65" width="59" apple-inline="yes" id="55CD2735-70C4-4566-A0B0-BB1C75154AF4" apple-width="yes" apple-height="yes" src="cid:879A6E78-CA46-47B2-AA0E-1810BD833229" class=""></span><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; line-height: normal; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="font-weight: normal;" class=""><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">---</div><div style="font-weight: normal;" class=""><br class=""></div><div class=""><b class="">Tim Sutton</b></div><div style="font-weight: normal;" class="">QGIS Project Steering Committee Chair</div><div style="font-weight: normal;" class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a></div><div style="font-weight: normal;" class=""><br class=""></div></div><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; line-height: normal;"><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
</div>
<br class=""></div></body></html>