<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Also: those Boston folx host a great code sprint.<br><br><div id="AppleMailSignature"><strong style="font-size: 13pt; background-color: rgba(255, 255, 255, 0);">Stephen V. Mather </strong><div><span style="background-color: rgba(255, 255, 255, 0);">+1 (216) 339-6347 (Signal, Telegram, Cell, and WhatsApp)</span></div></div><div><br>On Jun 21, 2018, at 20:29, Regina Obe <<a href="mailto:lr@pcorp.us">lr@pcorp.us</a>> wrote:<br><br></div><blockquote type="cite"><div><span>If we do Boston, I'd be happy to host at my place - great view :)</span><br><span>We can use some of the money to pay for hotel and plane accommodations and try to get some other sponsors too.</span><br><span></span><br><span>Thanks,</span><br><span>Regina</span><br><span></span><br><span></span><br><blockquote type="cite"><span>-----Original Message-----</span><br></blockquote><blockquote type="cite"><span>From: postgis-devel [<a href="mailto:postgis-devel-bounces@lists.osgeo.org">mailto:postgis-devel-bounces@lists.osgeo.org</a>] On</span><br></blockquote><blockquote type="cite"><span>Behalf Of Paul Ramsey</span><br></blockquote><blockquote type="cite"><span>Sent: Monday, June 18, 2018 10:12 AM</span><br></blockquote><blockquote type="cite"><span>To: PostGIS Development Discussion <<a href="mailto:postgis-devel@lists.osgeo.org">postgis-devel@lists.osgeo.org</a>></span><br></blockquote><blockquote type="cite"><span>Subject: Re: [postgis-devel] PostGIS Code Sprint?</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Well, we have, hiding in the archives somewhere, a nice long list of "big</span><br></blockquote><blockquote type="cite"><span>project" problems that maybe we want to dust off? But it doesn't have to be</span><br></blockquote><blockquote type="cite"><span>a big project necessarily. Could just be the impetus to finish some unfinished</span><br></blockquote><blockquote type="cite"><span>things (on my side, harmonizing the row-based output formats, or the</span><br></blockquote><blockquote type="cite"><span>internally indexed distance code) that need input from multiple folks.</span><br></blockquote><blockquote type="cite"><span>P</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On Mon, Jun 18, 2018 at 6:32 AM, Daniel Baston <<a href="mailto:dbaston@gmail.com">dbaston@gmail.com</a>></span><br></blockquote><blockquote type="cite"><span>wrote:</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>Hi Paul,</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Sounds fun. Are you thinking of doing something to prepare for a 2.5</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>release, or to kick off a larger project for 2.6? It would be great to</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>tackle something thorny like the validity flag.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Dan</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>On Sat, Jun 16, 2018 at 12:34 PM Paul Ramsey</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><<a href="mailto:pramsey@cleverelephant.ca">pramsey@cleverelephant.ca</a>></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Hey devs,</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>I just noticed a line item in the OSGeo budget... [1] I vaguely</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>remember some discussion about getting our oar in when the call for</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>budget items went out, I guess we put that oar in? Which brings me</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>to: should we do this then? :) ATB, P</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>[1] <a href="https://wiki.osgeo.org/wiki/OSGeo_Budget_2018#Code_Sprints">https://wiki.osgeo.org/wiki/OSGeo_Budget_2018#Code_Sprints</a></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>_______________________________________________</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>postgis-devel mailing list</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span><a href="mailto:postgis-devel@lists.osgeo.org">postgis-devel@lists.osgeo.org</a></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span><a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>_______________________________________________</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>postgis-devel mailing list</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="mailto:postgis-devel@lists.osgeo.org">postgis-devel@lists.osgeo.org</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a></span><br></blockquote></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>postgis-devel mailing list</span><br></blockquote><blockquote type="cite"><span><a href="mailto:postgis-devel@lists.osgeo.org">postgis-devel@lists.osgeo.org</a></span><br></blockquote><blockquote type="cite"><span><a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a></span><br></blockquote><span></span><br><span>_______________________________________________</span><br><span>postgis-devel mailing list</span><br><span><a href="mailto:postgis-devel@lists.osgeo.org">postgis-devel@lists.osgeo.org</a></span><br><span><a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a></span></div></blockquote></body></html>