<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi Martin<div class=""><br class=""><blockquote type="cite" class="">On 24 Nov 2015, at 18:14, Martin Dobias <<a href="mailto:wonder.sk@gmail.com" class="">wonder.sk@gmail.com</a>> wrote:<br class=""><br class="">Hi Andreas<br class=""><br class="">In order to keep spending of <a href="http://qgis.org" class="">QGIS.ORG</a> efficient and transparent, it<br class="">would make sense to undertake bigger projects through a simple bidding<br class="">process. The board would prepare a specification with requirements and<br class="">any interested party would be allowed to participate. Bidders would<br class="">submit their proposals and the board would then award the contract to<br class="">the best bid. A proposal would include 1. total cost, 2. delivery<br class="">date, 3. draft QEP, so that it is clear what the developers want to<br class="">do.<br class=""><br class=""></blockquote><div class=""><br class=""></div><div class="">As Anita mentioned, we started to compile a bidding proposal document yesterday. I totally agree that we should do it in a transparent way. That way we can evaluate the SP offer alongside other potential solutions. Rest assured that we will do everything transparently and not make any decisions without giving all interested parties an opportunity to pitch for the work.</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Tim</div><br class=""><blockquote type="cite" class="">Regards<br class="">Martin<br class=""><br class=""><br class="">On Tue, Nov 24, 2015 at 11:58 AM, Neumann, Andreas <<a href="mailto:a.neumann@carto.net" class="">a.neumann@carto.net</a>> wrote:<br class=""><blockquote type="cite" class="">Hi <a href="http://qgis.org" class="">QGIS.ORG</a> board,<br class=""><br class="">As you may know, Sourcepole developed the Vector analysis tools from Scratch<br class="">for QGIS enterprise. They are apparently willing to port it into QGIS master<br class="">- but there are several things missing. They would do the missing parts for<br class="">25k CHF (Swiss franks) - it probably also contains a smaller share of the<br class="">initial dev costs they had.<br class=""><br class="">The missing bits are:<br class=""><br class="">- porting into QGIS master<br class=""><br class="">- moving the code from plugin to QGIS core analysis library<br class=""><br class="">- create Python bindings<br class=""><br class="">- create unit tests<br class=""><br class="">-----------------------<br class=""><br class="">What they already did:<br class=""><br class="">Complete Rewrite in C++ of:<br class=""><br class="">- Convex Hull<br class=""><br class="">- Buffer<br class=""><br class="">- Intersect<br class=""><br class="">- Union<br class=""><br class="">- Symmetric difference<br class=""><br class="">- Clip<br class=""><br class="">- Difference<br class=""><br class="">- Dissolve<br class=""><br class="">- Eliminate sliver poylgons<br class=""><br class="">It allows to save the result as any OGR format, supports multi-threading and<br class="">comes with a detailed error log in case of problems with invalid geometries.<br class=""><br class="">---------------------------<br class=""><br class="">Some additional background: they already invested >200 hours for the<br class="">re-development of the above methods. This equals about 35 kCHF.<br class=""><br class="">----------------------------<br class=""><br class="">Timing: they could probably do it for the QGIS 2.16 release (feature freeze<br class="">May 20, 2016). They are busy with contracts - they cannot do it earlier with<br class="">the resources they have.<br class=""><br class="">To me, personally, this sounds like a good offer.<br class=""><br class="">We would have to find a solution for our short-term problems with fTools -<br class="">but to me this is a very good proposal to have a good fTools replacement in<br class="">the future.<br class=""><br class="">Andreas<br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">Qgis-psc mailing list<br class=""><a href="mailto:Qgis-psc@lists.osgeo.org" class="">Qgis-psc@lists.osgeo.org</a><br class="">http://lists.osgeo.org/mailman/listinfo/qgis-psc<br class=""></blockquote>_______________________________________________<br class="">Qgis-psc mailing list<br class=""><a href="mailto:Qgis-psc@lists.osgeo.org" class="">Qgis-psc@lists.osgeo.org</a><br class="">http://lists.osgeo.org/mailman/listinfo/qgis-psc<br class=""></blockquote><br class=""><div class=""><span><img height="60" width="60" apple-inline="yes" id="1C3F124F-383E-42B5-98B6-5058DA60B8C8" apple-width="yes" apple-height="yes" src="cid:DDEF9B12-67C3-4498-BD7D-EC3563CC35A4" class=""></span><br class=""><br class=""><br class="">Tim Sutton<br class="">QGIS Project Steering Committee Member<br class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a><br class=""><br class=""><br class=""><br class=""></div><br class=""></div></body></html>