<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="">+1 to starting 2017 in 6/15 and 2018 in 12/15<div class=""><br class=""></div><div class="">After those to Calls have been completed we can assess whether any further change is needed<br class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">______<br class="">Steven<br class=""><br class=""></span>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 23 Dec 2014, at 07:13, Bart van den Eijnden <<a href="mailto:bartvde@osgis.nl" class="">bartvde@osgis.nl</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">I think Cameron is saying start the process for 2017 in 6 months from now and for 2018 in 12 months from now.<br class=""><br class="">Bart<br class=""><br class="">Sent from my iPhone<br class=""><br class=""><blockquote type="cite" class="">On 22 dec. 2014, at 22:38, Eli Adam <<a href="mailto:eadam@co.lincoln.or.us" class="">eadam@co.lincoln.or.us</a>> wrote:<br class=""><br class="">On Mon, Dec 22, 2014 at 12:09 PM, Cameron Shorter<br class=""><<a href="mailto:cameron.shorter@gmail.com" class="">cameron.shorter@gmail.com</a>> wrote:<br class=""><blockquote type="cite" class="">I'm +0 for moving the conference selection forward.<br class="">I suggest start by selecting foss4g-na in 6 months time, foss4g-(elsewhere)<br class="">in 12 months.<br class="">If that suites people from NA, I suggest raising a motion.<br class=""></blockquote><br class="">Selecting FOSS4G 2017 12 months from now would be keeping things about<br class="">the same, I don't think a motion is needed to do that.<br class=""><br class="">Eli<br class=""><br class=""><blockquote type="cite" class=""><br class=""><br class=""><blockquote type="cite" class="">On 23/12/2014 4:13 am, Eli Adam wrote:<br class=""><br class="">On Mon, Dec 22, 2014 at 5:48 AM, Steven Feldman <<a href="mailto:shfeldman@gmail.com" class="">shfeldman@gmail.com</a>><br class="">wrote:<br class=""><blockquote type="cite" class=""><br class="">Fair points Arnulf<br class=""><br class="">Surely the announcement requesting LoI’s can be anticipated by potential<br class="">bid<br class="">teams who can start their venue planning etc before the official<br class="">announcement.<br class=""></blockquote><br class="">Writing LoI's is easy and can be done years in advance or the week in<br class="">advance. Reserving venues with a deposit is more of a commitment.<br class=""><br class=""><blockquote type="cite" class="">We know 2016 is Europe, 2017 is America, 2018 is somewhere else 2019 is<br class="">Europe, 2020 America and 2012 is somewhere else - do teams bidding for<br class="">2017<br class="">onwards need any more notification than that?<br class=""></blockquote><br class="">Yes, LOCs need a decision so that they can pay a deposit on their<br class="">venue. Most venues will not reserve without a deposit and most LOCs<br class="">won't pay a deposit without a decision that they have been awarded the<br class="">bid.<br class=""><br class="">Where is PyCon in 2017? Oh, Portland [1], they already know far in<br class="">advance and will be reserving venues, the same venues that FOSS4G<br class="">might be considering. Same for other cities and other conferences.<br class="">The conferences that book the same venues as FOSS4G reserve 2-3 years<br class="">in advance, for FOSS4G to have a chance at those venues we need to<br class="">reserve on similar time frames (or rely on luck or alternate venues or<br class="">adjust the dates).<br class=""><br class=""><br class="">Best regards, Eli<br class=""><br class=""><br class="">[1]<br class=""><a href="http://pyfound.blogspot.com/2014/08/portland-chosen-as-pycon-20162017.html" class="">http://pyfound.blogspot.com/2014/08/portland-chosen-as-pycon-20162017.html</a><br class=""><br class=""><br class=""><blockquote type="cite" class="">______<br class="">Steven<br class=""><br class=""><br class="">On 19 Dec 2014, at 11:52, Seven (aka Arnulf) <seven@arnulf.us> wrote:<br class=""><br class="">-----BEGIN PGP SIGNED MESSAGE-----<br class="">Hash: SHA1<br class=""><br class="">Steven,<br class="">in my experience there are several distinct phases and the very initial<br class="">phase of selecting a venue, coordinating with parallel events, starting<br class="">dialogs about co-location etc. need to be done with enough time to go.<br class="">This will typically be done by a small team of initial firestarters.<br class=""><br class="">Later on the team will grow and include others. The last sprint planning<br class="">meeting will take place just a few months prior to the conference.<br class=""><br class="">Therefore I would not think that an early CfP will result in a tired or<br class="">burnt-out team. It is the responsibility of the LOC chair to manage<br class="">accordingly (as you have brilliantly managed to) and take care that the<br class="">team will not be stretched too hard (...until a few weeks prior to the<br class="">event when the team has to go full throttle).<br class=""><br class="">Cheers,<br class="">Arnulf<br class=""><br class="">On 19.12.2014 08:33, Steven Feldman wrote:<br class=""><br class="">I am not sure that I agree that LOCs need or want more than 18-20<br class="">months notice. Whilst there may be a benefit in terms of venue<br class="">booking, there could be a downside in team fatigue and drop out<br class=""><br class="">For FOSS4G2013 we started thinking about the event and putting a team<br class="">together in September 2011. We were ready with a venue (provisional<br class="">booking) by the time the call for LoIs came out.<br class=""><br class="">Steven<br class=""><br class="">On 19 Dec 2014, at 01:13, Eli Adam <eadam@co.lincoln.or.us> wrote:<br class=""><br class="">Conference Committee,<br class=""><br class="">Consistent feedback from previous LOCs is "make the FOSS4G LOC<br class="">decision with more time before the event". The 2016 decision is<br class="">slated to be made on 2015-03-01 [1]. Should we launch the 2017<br class="">process on 2015-03-02? It seems that LOCs are eagerly awaiting<br class="">the opportunity to bid and are more than prepared once the process<br class="">happens.<br class=""><br class="">A LOC decision with more time before the event may also be the<br class="">single best way to ensure success and reduce risk. It is also<br class="">super easy. I suggest moving up the 2017 and 2018 timelines.<br class="">Until there are complaints from potential LOCs that the decision is<br class="">too early or more importantly if there are no quality bids, then I<br class="">think the decision can be made sooner.<br class=""><br class="">Claude, Sorry to hear that there is not suitable date availability<br class="">at your top choice venue. I'm sure that if Lausanne bids it would<br class="">be one of several very excellent bids. Had the bid been earlier<br class="">and awarded to Lasanne, I'm sure that the LOC would already be well<br class="">on the way to a great conference.<br class=""><br class="">Best regards, Eli<br class=""><br class=""><br class="">[1] http://www.osgeo.org/conference/rfp/<br class=""><br class="">_______________________________________________ Conference_dev<br class="">mailing list Conference_dev@lists.osgeo.org<br class="">http://lists.osgeo.org/mailman/listinfo/conference_dev<br class=""><br class=""><br class=""><br class="">- --<br class="">Exploring Space, Time and Mind<br class="">http://arnulf.us<br class="">-----BEGIN PGP SIGNATURE-----<br class="">Version: GnuPG v1.4.11 (GNU/Linux)<br class=""><br class="">iEYEARECAAYFAlSUEZoACgkQXmFKW+BJ1b3Q4ACeK9zadq5oE4s9IqhUAUm2DZT9<br class="">lM8AnRKDuLTKE2mWxymvfYO1ekiMVqiz<br class="">=l4Nu<br class="">-----END PGP SIGNATURE-----<br class="">_______________________________________________<br class="">Conference_dev mailing list<br class="">Conference_dev@lists.osgeo.org<br class="">http://lists.osgeo.org/mailman/listinfo/conference_dev<br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">Conference_dev mailing list<br class="">Conference_dev@lists.osgeo.org<br class="">http://lists.osgeo.org/mailman/listinfo/conference_dev<br class=""></blockquote><br class="">_______________________________________________<br class="">Conference_dev mailing list<br class="">Conference_dev@lists.osgeo.org<br class="">http://lists.osgeo.org/mailman/listinfo/conference_dev<br class=""></blockquote><br class=""><br class="">--<br class="">Cameron Shorter,<br class="">Software and Data Solutions Manager<br class="">LISAsoft<br class="">Suite 112, Jones Bay Wharf,<br class="">26 - 32 Pirrama Rd, Pyrmont NSW 2009<br class=""><br class="">P +61 2 9009 5000, W <a href="http://www.lisasoft.com" class="">www.lisasoft.com</a>, F +61 2 9009 5099<br class=""><br class=""><br class="">_______________________________________________<br class="">Conference_dev mailing list<br class=""><a href="mailto:Conference_dev@lists.osgeo.org" class="">Conference_dev@lists.osgeo.org</a><br class="">http://lists.osgeo.org/mailman/listinfo/conference_dev<br class=""></blockquote>_______________________________________________<br class="">Conference_dev mailing list<br class=""><a href="mailto:Conference_dev@lists.osgeo.org" class="">Conference_dev@lists.osgeo.org</a><br class="">http://lists.osgeo.org/mailman/listinfo/conference_dev<br class=""></blockquote>_______________________________________________<br class="">Conference_dev mailing list<br class=""><a href="mailto:Conference_dev@lists.osgeo.org" class="">Conference_dev@lists.osgeo.org</a><br class="">http://lists.osgeo.org/mailman/listinfo/conference_dev</div></blockquote></div><br class=""></div></body></html>