[postgis-devel] PostGIS Code Sprint?

Regina Obe lr at pcorp.us
Fri Jun 22 10:07:20 PDT 2018


End of week is a little better so Sept 26-28

> -----Original Message-----
> From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On
> Behalf Of Paul Ramsey
> Sent: Thursday, June 21, 2018 1:33 PM
> To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
> Subject: Re: [postgis-devel] PostGIS Code Sprint?
> 
> If I floated: Boston, September 26-28, or 24-26, what would people say?
> 
> > On Jun 21, 2018, at 10:29 AM, Regina Obe <lr at pcorp.us> wrote:
> >
> > If we do Boston, I'd be happy to host at my place - great view :) We
> > can use some of the money to pay for hotel and plane accommodations
> and try to get some other sponsors too.
> >
> > Thanks,
> > Regina
> >
> >
> >> -----Original Message-----
> >> From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On
> >> Behalf Of Paul Ramsey
> >> Sent: Monday, June 18, 2018 10:12 AM
> >> To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
> >> Subject: Re: [postgis-devel] PostGIS Code Sprint?
> >>
> >> Well, we have, hiding in the archives somewhere, a nice long list of
> >> "big project" problems that maybe we want to dust off? But it doesn't
> >> have to be a big project necessarily. Could just be the impetus to
> >> finish some unfinished things (on my side, harmonizing the row-based
> >> output formats, or the internally indexed distance code) that need input
> from multiple folks.
> >> P
> >>
> >> On Mon, Jun 18, 2018 at 6:32 AM, Daniel Baston <dbaston at gmail.com>
> >> wrote:
> >>> Hi Paul,
> >>>
> >>> Sounds fun. Are you thinking of doing something to prepare for a 2.5
> >>> release, or to kick off a larger project for 2.6? It would be great
> >>> to tackle something thorny like the validity flag.
> >>>
> >>> Dan
> >>>
> >>> On Sat, Jun 16, 2018 at 12:34 PM Paul Ramsey
> >>> <pramsey at cleverelephant.ca>
> >>> wrote:
> >>>>
> >>>> Hey devs,
> >>>> I just noticed a line item in the OSGeo budget... [1] I vaguely
> >>>> remember some discussion about getting our oar in when the call for
> >>>> budget items went out, I guess we put that oar in? Which brings me
> >>>> to: should we do this then? :) ATB, P
> >>>>
> >>>> [1] https://wiki.osgeo.org/wiki/OSGeo_Budget_2018#Code_Sprints
> >>>> _______________________________________________
> >>>> postgis-devel mailing list
> >>>> postgis-devel at lists.osgeo.org
> >>>> https://lists.osgeo.org/mailman/listinfo/postgis-devel
> >>>
> >>>
> >>> _______________________________________________
> >>> postgis-devel mailing list
> >>> postgis-devel at lists.osgeo.org
> >>> https://lists.osgeo.org/mailman/listinfo/postgis-devel
> >> _______________________________________________
> >> postgis-devel mailing list
> >> postgis-devel at lists.osgeo.org
> >> https://lists.osgeo.org/mailman/listinfo/postgis-devel
> >
> > _______________________________________________
> > postgis-devel mailing list
> > postgis-devel at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/postgis-devel
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel



More information about the postgis-devel mailing list