<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Anita<div class=""><br class=""></div><div class="">Are you going to put it on the QGIS blog? Could you share the draft then it is on WP so I can make some edits?</div><div class=""><br class=""></div><div class="">For now I also put your text as a placeholder in the changelog for 3.0 here</div><div class=""><br class=""></div><div class=""><a href="http://changelog.qgis.org/en/qgis/version/3.0.0/#qgis-server-overhaul" class="">changelog.qgis.org/en/qgis/version/3.0.0/#qgis-server-overhaul</a></div><div class=""><br class=""></div><div class="">By the way I’d love it if non-coders (and of course coders also welcome) out there who are looking for a way to contribute to QGIS could contact me and help to write up the changelog for 3.0….Its going to be a massive job since our developer community have been rather busy adding lots of new features and tweaks in QGIS 3.0!</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Tim<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 17 Oct 2017, at 22:36, Anita Graser <<a href="mailto:anitagraser@gmx.at" class="">anitagraser@gmx.at</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-size:small"><div style="font-size:12.8px" class="">I've extended Régis' draft with some of the more recent information. Please let me know what you think. I'll try to publish in a couple of days.</div><div style="font-size:12.8px" class=""><br class=""></div><div style="font-size:12.8px" class="">-- start --</div><div style="font-size:12.8px" class=""><b class=""><br class=""></b></div><div style="font-size:12.8px" class=""><b class="">QGIS server refactoring is done!<br class=""></b><br class="">As you may know, QGIS is jumping to a new major version (yes!). Doing so was made necessary because of the need to switch to python 3, QT5, but also because we needed to break the QGIS API in several places. (<a href="http://blog.qgis.org/2016/02/10/qgis-3-0-plans/" target="_blank" class="">http://blog.qgis.org/2016/02/<wbr class="">10/qgis-3-0-plans/</a>) </div><span class="gmail-im"><div style="font-size:12.8px" class=""><br class="">A year ago, a <a href="https://github.com/qgis/qgis3.0_api/issues/63" target="_blank" class="">tiny troll </a>from switzerland rang a bell about the strong need for love server code base required. <span style="font-size:12.8px" class="">Indeed, the API was locked by some old methods of QGIS server. In short, QGIS server was reparsing the qgs project file in his own way, and created dependencies to part of QGIS we needed to drop.</span></div><div style="font-size:12.8px" class=""> <br class="">As outsourcing the server code base was not an option, so we had to refactor it. The involved parties decided to get engaged in a <a href="https://github.com/qgis/QGIS/wiki/QGIS3---QGIS-Server-code-sprint-Notes" target="_blank" class="">code sprint</a> in the city of Lyon , France dedicated to sharing their vision, planning the work and finally making all the <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/74" target="_blank" class="">following</a> happen:</div></span><div style="font-size:12.8px" class=""><div class=""><br class=""></div><div class=""><b class="">Higher level refactoring</b></div><div class=""><br class=""></div><div class="">All services (WMS GetMap, WFS GetFeature, GetLegendGraphics, WCS, GetPrint etc..) have been rewritten. Some like WMS were entirely rewritten. Kudos to the devs!</div><div class=""><br class=""></div><div class=""><b style="font-size:12.8px" class="">New features</b><br class=""></div><div class=""><br class=""></div><div style="font-size:12.8px" class="">- <a href="https://github.com/qgis/QGIS/pull/3886" target="_blank" class="">Multi-thread rendering</a> like in the desktop</div><div style="font-size:12.8px" class=""><br class=""></div><div style="font-size:12.8px" class=""><span style="font-size:12.8px" class="">- A new option to </span><a href="https://github.com/qgis/QGIS/pull/5094" target="_blank" style="font-size:12.8px" class="">trust layer metadata</a><span style="font-size:12.8px" class=""> and thus speed up project loading</span><br class=""></div><div style="font-size:12.8px" class=""><br class=""></div><div style="font-size:12.8px" class=""><span style="font-size:12.8px" class="">- WFS 1.1 support <a href="https://github.com/qgis/QGIS/pull/5297" target="_blank" class="">https://github.com/<wbr class="">qgis/QGIS/pull/5297</a> </span><br class=""></div><div style="font-size:12.8px" class=""><span style="font-size:12.8px" class=""><br class=""></span></div><div style="font-size:12.8px" class="">- Full Python bindings for the server API</div><div style="font-size:12.8px" class=""><br class=""></div><div class=""><span style="font-size:12.8px" class=""></span>- Server Services as plugins like providers</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><span class="gmail-im"><b style="font-size:12.8px" class="">Deep, complex and unrewarding tasks<br class=""></b><div style="font-size:12.8px" class=""><br class=""></div><div style="font-size:12.8px" class="">- Remove all singleton calls</div><div style="font-size:12.8px" class=""><br class=""></div></span><div style="font-size:12.8px" class="">- Cut all the dependencies to the old QGIS project file parser</div><span class="gmail-im"><div style="font-size:12.8px" class=""><br class=""></div><div style="font-size:12.8px" class="">- Minimize dependencies to GUI library. Since fonts are necessary to render maps, totally removing them was not feasable. </div></span></div><div class=""><br class=""></div><span class="gmail-im"><div class=""><b style="font-size:12.8px" class="">Infrastructure tasks</b><br class=""></div><div class=""><br class=""></div><div class="">- <a href="http://oslandia.com/en/2017/06/16/qgis-server-ogc-cite-compliance-testing/" target="_blank" class="">Build a OGC compliancy platform</a> and integrate it to a continuous integration platform. Conformity reports are now pushed to <a href="http://tests.qgis.org/" target="_blank" class="">tests.qgis.org</a> </div><div class=""><i style="background-color:rgb(255,0,0)" class=""><br class=""></i></div></span><div class="">- Add unit tests ... and again more unit tests</div><div class=""><br class=""></div><div class="gmail-adL"><span class="gmail-im"><div class="">-<a href="http://oslandia.com/en/2017/06/14/qgis-server-security-aspect/" target="_blank" style="" class=""> Stress QGIS server against security leaks</a> (SQL injections and other malicious attacks)</div><div class=""><br class=""></div><div class="">- Start profiling and bench marking performances. This work still need some love - and funding - to be achieved</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">A <a href="https://git.osgeo.org/gogs/foss4g-europe/foss4g-europe-2017-paris/src/master/presentations/2017-07-20/general_track/foss4g-europe-2017-QGIS_3_Refactoring_and_enhancement-DMarteau-PBlottiere.pdf" target="_blank" class="">presentation</a> was given at FOSS4G-EU in July. <br class=""></div><div class=""><br class=""></div><div class=""><b class="">Congratulations</b> to the developers who worked hard on that work. </div><div class=""><br class=""></div><div class="">Now this deserves to be well tested, please report back any issues!</div></span></div></div></div></div>
_______________________________________________<br class="">QGIS-Developer mailing list<br class=""><a href="mailto:QGIS-Developer@lists.osgeo.org" class="">QGIS-Developer@lists.osgeo.org</a><br class="">List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer<br class="">Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer</div></blockquote></div><br class=""></div></body></html>