<div dir="ltr"><div><br class="gmail-Apple-interchange-newline">Hi all, <div>we had a chat with 3liz to share a common view of current refactoring status and next priorities:</div><div><br></div><div><br></div><div><div><b>What the refactor is expected to adress :</b></div><div><br></div><div> It is a blocking part since it is quite hard to find funds for "plumbery" tasks and make it understandable by users. </div><div> The refactor is obviously made mandatory by the move to QGIS3 API. </div><div> Obviously again, it will help in having a clearer codebase, easier to maintain , faster and more modular.</div><div> For instance, having the ability to generate on the fly some project and layer definition will help a lot in GeoNode integration.</div></div><div><br></div><div><br></div><div><div></div></div><div><b>What has been done :</b></div><div><b><br></b></div><div> - <b>3liz</b> has created a new <b>modular architecture</b> allowing to refactor each services independently. It exposes a clean API, and if I get it well, <b>Alessandro</b> already used it to rework the server plugin python API. </div><div><br></div><div> - <b>3liz</b> is refactoring progressively all the <b>services</b>. All WFS, all WCS and WMS GetCapabilities are done. GetContext is being worked on. </div><div><b><br></b></div><div><b> - Oslandia : </b>Paul is almost done with a full WMS rewrite now only using core classes and no more XML parsing</div><div><br></div><div> - <b>Oslandia : </b>OGC CITE compliancy docker testing framework - see [1]</div><div><br></div><div> - <b>Oslandia</b> : Speed improvements for getcapabilities where datasource are massive views or materialized views (or layers with definition filters / joins). AKA "trust project" option. </div><div><br></div><div> - <b>Camptocamp</b> created a docker platform for performance benchmark between qgis server / mapserver and geoserver - see [3]</div><div><br></div><div><b><br></b></div><div><b>What needs to be finished before 3.0, where funding will help a lot :</b></div><div><b><br></b></div><div><div> - <b>all</b>: a lot of work has been done to remove the projectParser and singletons, but there is still some work to do.</div><div><br></div><div> - <b>services rewrite</b> <b>(3liz)</b>: getContext / DescribeLayer / GetFeatureInfo, GetStyle, DXFWriter</div><div><br></div><div> - <b>service rewrite (Oslandia): </b>GetLegendGraphics / GetPrint</div><div><br></div><div><br></div></div><div><b>What would be (really) nice to have :</b></div><div><b><br></b></div><div><div> - <b>OGC CITE (Oslandia)</b> : Automate running and publishing html reports to a public ressource, if possible hosted by QGIS.org. (small task)</div><div> - <b>OGC CITE</b> : debug existing failures and apply for an official OGC certification. No idea how much time this can take. </div><div> -<b> Performance benchmark platform</b> : define reference tests, automate them and track regressions or improvements over time. This is a tricky topic, but performances tests with reference platforms helped a lot in raising some issues. </div><div> - <b>Communication</b> : push a blog post from QGIS.org for an official support of the project and advertising there all the funders and involved parties. That would help a lot in raising new funds too.. </div><div><br></div><div><b>What is not yet planned :</b></div><div><br></div><div>- Implement a caching strategy for scalability</div><div>- vector tiles ?</div><div><br></div></div><div><div>note: A detailed view is available in QEP74 [0] and all related PR are here [4].</div></div><div><br></div><div>So, in short, if some funds are available from QGIS.org, I think we have some candidates and priorities to discuss here. We also need to estimate more precisely each task...</div><div><br></div><div><br></div><div>Opinions welcome !</div><div><br></div><div><br></div><div>[0] <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/74">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/74</a></div><div><div style="line-height:normal">[1] <a href="https://hub.docker.com/r/oslandia/qgis-server-ogc-cite/">https://hub.docker.com/r/oslandia/qgis-server-ogc-cite/</a></div><div style="line-height:normal">[3] <a href="https://github.com/camptocamp/ms_perfs">https://github.com/camptocamp/ms_perfs</a></div><div style="line-height:normal">[4] <a href="https://github.com/qgis/QGIS/pulls?q=is%3Apr+label%3AServer+milestone%3A%22QGIS+3%22+is%3Aclosed">https://github.com/qgis/QGIS/pulls?q=is%3Apr+label%3AServer+milestone%3A%22QGIS+3%22+is%3Aclosed</a> </div><div style="line-height:normal"><div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-05-21 16:35 GMT+02:00 Tim Sutton <span dir="ltr"><<a href="mailto:tim@qgis.org" target="_blank">tim@qgis.org</a>></span>:<br><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">Hi All<div><br></div><div>From my side I am ok with <a href="http://QGIS.ORG" target="_blank">QGIS.ORG</a> funding work where we feel it is in the good of the project. I think the simple solution if we have the cash is to just raise a Loomio proposal with the Voting Members and let them decide. I think there should be some leeway for QGIS to make discretionary sponsorships of features or bug fixing etc. outside of the normal budget plans (so that we can e.g. capitalise on budget savings as per your example above) but I am worried that we will appear to subvert the QGIS Grant Programme process if we do it in this case. Getting it done by a loomio vote (with a nice clear explanation of why it is useful) should be quick and easy and transparent.</div><div><br></div><div>BTW I am also very -1 on you spending your personal cash on this - we (<a href="http://QGIS.ORG" target="_blank">QGIS.ORG</a>) already use a lot of your time (which equates to lost earnings potential) via your work in the PSC and I would not like to see you putting in your cash too when probably the community would be happy to fund it.</div><div><br></div><div>I am also thinking it might be useful to broaden our scope a bit and collect up any other QGIS Server work that needs funding into one work package and make the proposal to fund everything that we can. I would not like to see QGIS Server get left behind as we forge on to QGIS 3.0 and we should support it as strongly as possible from the <a href="http://QGIS.ORG" target="_blank">QGIS.ORG</a> funds. I think this approach might also be more effective than a crowd funding drive too which may result in a lengthy wait for no result.</div><div><br></div><div>Regards</div><div><br></div><div>Tim</div></div><div class="gmail_extra"><div><div class="gmail-m_8456366466323088333m_1505267715302890283h5"><br><div class="gmail_quote">On Sat, May 20, 2017 at 9:37 PM, Régis Haubourg <span dir="ltr"><<a href="mailto:regis.haubourg@gmail.com" target="_blank">regis.haubourg@gmail.com</a>></span> wrote:<br><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">Hi All, <div>Sorry for being late here. </div><div><br></div><div>The big picture of what needs to be done has been drawn at the codesprint in Lyon [0].</div><div><br></div><div>We know that Camp2Camp has a benchmark framework that would address the performance driven coding. </div><div><br></div><div>3liz is involved in adding more modularity and refactors other services. </div><div><br></div><div>Alessandro Passoti is committed in refactoring the plugin API. </div><div><br></div><div>Beyond those cleanups or rewrites, we also identified the need to find a common strategy to allow scalability of QGIS server (caching layers and project over server clusters)</div><div><br></div><div><div>At Oslandia, we have funders that helped us in refactoring of WMS services, OGC compliancy, security and performance issues. We keep working on these items on our owns resources. </div><div><br></div><div>Currently, our partners claim for some feedback before considering funding more work :</div><div><br></div><div> - Having some official feedback that this work is appreciated and welcome by the <a href="http://qgis.org" target="_blank">qgis.org</a> project</div><div><br></div><div> - Having some references (web pages, blog, talks) showing that pushing this work is triggering commitment from others parties, if possible other corporations. </div><div><br></div><div> - and of course, see some real preliminary results of the already done tasks.</div><div><br></div><div>I think that the PSC could help in the communication plan to help funders feel that they are not alone, and that there is a large community trusting in the future of QGIS server and working hard on it. </div><div><br></div><div>On our side, we have some web articles ready to publish, we will have a common talk with 3liz at the Foss4G Europe in Paris. </div></div><div><br></div><div>That said, any additional funding is more than welcome, but I'd prefer to set up a common strategy than individual fundings. </div><div>Crowdfunding initiative in France are almost impossible to raise for private structures, so if QGIS.org is going this way, we'll need a proxy in front the different involved parties, and we'll have to coordinate on the funding attributions. </div><div>Last point, Nyall has already a crowdfuding campaign opened, so not sure if that could interfer or not (and we need that composer rewrite :) )</div><div><br></div><div>Cheers, and thanks for all the good energy being given here!</div><div><br></div><div>[0] <a href="https://github.com/qgis/QGIS/wiki/Code-Sprint-QGIS-3-Lyon,-end-2016" target="_blank">https://github.com/qgis/QGIS/w<wbr>iki/Code-Sprint-QGIS-3-Lyon,-e<wbr>nd-2016</a></div></div><div class="gmail-m_8456366466323088333m_1505267715302890283m_-9001834449369623934HOEnZb"><div class="gmail-m_8456366466323088333m_1505267715302890283m_-9001834449369623934h5"><div class="gmail_extra"><br><div class="gmail_quote">2017-05-20 15:10 GMT+02:00 Matthias Kuhn <span dir="ltr"><<a href="mailto:matthias@opengis.ch" target="_blank">matthias@opengis.ch</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>On 5/19/17 5:15 PM, Paolo Cavallini wrote:<br>
<br>
> Il 19/05/2017 17:06, Matthias Kuhn ha scritto:<br>
><br>
>> A very good idea indeed.<br>
>> Are you proposing to have someone private take the lead, are you<br>
>> thinking of 3liz as developers or are you speaking of "we" with the<br>
>> Faunalia hat? Anything will do, just to make sure nobody feels<br>
>> responsible :)<br>
> sorry, I as in fact unclear: when I write here I speak as PSC member, so<br>
> we==<a href="http://QGIS.ORG" rel="noreferrer" target="_blank">QGIS.ORG</a> PSC<br>
</span>Sorry, I thought that <a href="http://qgis.org" rel="noreferrer" target="_blank">qgis.org</a> does not directly involve in crowdfunding<br>
projects, I must have missed the decision when this was changed. Are the<br>
requirements for a project to be executed by <a href="http://qgis.org" rel="noreferrer" target="_blank">qgis.org</a> available somewhere?<br>
<br>
All the best<br>
<span class="gmail-m_8456366466323088333m_1505267715302890283m_-9001834449369623934m_8304537503612976972HOEnZb"><font color="#888888">Matthias<br>
</font></span><div class="gmail-m_8456366466323088333m_1505267715302890283m_-9001834449369623934m_8304537503612976972HOEnZb"><div class="gmail-m_8456366466323088333m_1505267715302890283m_-9001834449369623934m_8304537503612976972h5">______________________________<wbr>_________________<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/mailma<wbr>n/listinfo/qgis-psc</a></div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<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/mailma<wbr>n/listinfo/qgis-psc</a><br></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="gmail-m_8456366466323088333m_1505267715302890283HOEnZb"><font color="#888888">-- <br><div class="gmail-m_8456366466323088333m_1505267715302890283m_-9001834449369623934gmail_signature"><div dir="ltr"><img src="https://docs.google.com/uc?export=download&id=0B__vDnQXCKiwQ3hfMHZxN0phaXM&revid=0B__vDnQXCKiwdkZZQ3krVFBOYmdMNkEvWEViTVM2OWY3ZTFRPQ"><br><div><br></div><div><br></div><div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px"><b>Tim Sutton</b></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px">QGIS Project Steering Committee Chair</div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px"><a href="mailto:tim@qgis.org" target="_blank">tim@qgis.org</a></div></div></div></div>
</font></span></div>
</blockquote></div><br></div></div></div>