[postgis-devel] PostGIS Code Sprint?

[Paul Ramsey]

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