<div dir="ltr"><div><div><div>Hi<br><br></div>I think it's a good move to include these libraries as they are an integral part of QGIS and if excluded, this will only encourage devs to write hacks on qgis side rather than fixing things at the right spot in the stack.<br><br></div>Do you think it's reasonable to add an (obvious) "... if in the best interest for QGIS" clause to the PSC decision for this kind of fixes and a requirement for an issue report on QGIS to highlight the relevance? (P.S. while I'm a proponent of low admin overhead, I think issue reports help a lot to work with a focus on problems and denote relevance. I often create issue reports even if the fix is already implemented to separate requirement and solution. If others feel like this requirement is too much of a burden, please object!)<br><br></div>Matthias<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 21, 2020 at 11:02 AM Andreas Neumann <<a href="mailto:andreas@qgis.org">andreas@qgis.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>So it seems like everyone is in favor of also including GEOS and GDAL/OGR library improvements in our QGIS bug fixing effort.</div><div><br></div><div>For me it is ok, if next to Even and strk also others (like Nyall and Alessandro) work on these libraries.<br></div><div><br></div><div>Do we need to write this down as a PSC decision?</div><div><br></div><div>Greetings,</div><div>Andreas<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 21 Sep 2020 at 03:01, Nyall Dawson <<a href="mailto:nyall.dawson@gmail.com" target="_blank">nyall.dawson@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sun, 20 Sep 2020 at 01:12, Alessandro Pasotti <<a href="mailto:apasotti@gmail.com" target="_blank">apasotti@gmail.com</a>> wrote:<br>
><br>
> Hi PSC,<br>
><br>
> I'd like to ask for permission that myself could work on GDAL<br>
> enhancements on behalf of the QGIS bug fixing effort, in a similar<br>
> manner like other developers often fix issues in GDAL/OGR/GEOS when<br>
> fixing issues in QGIS.<br>
<br>
Can I also ask this same permission please? There's a couple of bugs<br>
I've tracked down to sitting in the GDAL library and I'd like to<br>
address these as part of the current round of fixes too...<br>
<br>
Nyall<br>
<br>
><br>
> Specifically, while working on<br>
> <a href="https://github.com/qgis/QGIS/issues/38092" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS/issues/38092</a> I've added the possibility<br>
> to interrupt/abort running queries through the QGIS connection API<br>
> (which is part of the ongoing effort to bury DB-Manager in favor of a<br>
> core C++ implementation).<br>
><br>
> In order for this to fully work, the data providers need to support<br>
> the cancellation of a running SQL query but GDAL does not currently<br>
> support this feature which is necessary for both GPKG and SPATIALITE<br>
> QGIS data providers.<br>
><br>
> I've spoken to Even who is not available at the moment but is happy to<br>
> help me polishing the feature if I take care of the implementation in<br>
> GDAL.<br>
><br>
> So I'm asking for the possibility to use a few hours from the QGIS bug<br>
> fixing to make this GDAL enhancement for GPKG and SPATIALITE drivers.<br>
><br>
> Alessandro<br>
><br>
> --<br>
> Alessandro Pasotti<br>
> QCooperative: <a href="http://www.qcooperative.net" rel="noreferrer" target="_blank">www.qcooperative.net</a><br>
> ItOpen: <a href="http://www.itopen.it" rel="noreferrer" target="_blank">www.itopen.it</a><br>
> _______________________________________________<br>
> Qgis-psc mailing list<br>
> <a href="mailto:Qgis-psc@lists.osgeo.org" target="_blank">Qgis-psc@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a><br>
_______________________________________________<br>
Qgis-psc mailing list<br>
<a href="mailto:Qgis-psc@lists.osgeo.org" target="_blank">Qgis-psc@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a></blockquote></div><br clear="all"><br>-- <br><div dir="ltr"><div dir="ltr"><div><br>--<br>Andreas Neumann<br></div><a href="http://QGIS.ORG" target="_blank">QGIS.ORG</a> board member (treasurer)<br></div></div>
_______________________________________________<br>
Qgis-psc mailing list<br>
<a href="mailto:Qgis-psc@lists.osgeo.org" target="_blank">Qgis-psc@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a></blockquote></div>