[Qgis-psc] Supporting QGIS Server development

Andreas Neumann a.neumann at carto.net
Mon Jun 26 09:59:37 PDT 2017


Hi all,

Ok - here is my proposal of wording for the Loomio vote.

-------------

During the work of QGIS 3.0 not only the Desktop and core code base 
received a lot of refactoring and API improvements, but also the server 
part. QGIS server is quite popular among users, due to the ease of use 
regarding configuration of symbology, feature information

and print layouts. Users also like the fact that the rendering between 
QGIS Desktop and QGIS server is identical. From version to version it 
grew more powerful and extensible, due to Python plugin extensions. 
However, the code base grew more and more complex, partially due to 
technical restrictions in the 2.x API when the majority of the QGIS 
server code base was written. However, while a lot of work already went 
into refactoring of the QGIS server code base, implemented by french and 
swiss companies 3Liz, Oslandia and Camptocamp, the work is not close to 
being finished. Financial support from QGIS.ORG would help developers to 
dedicate more time and help finish the refactoring and de-coupling 
between core and GUI, and rewriting essential parts of QGIS Server. In 
addition, effort would go into making sure that QGIS server is OGC 
compliant.

Fortunately, the financial situation of QGIS.ORG allows us to support 
the QGIS server development in addition to our commitments in the QGIS 
grants program and the bug fixing effort.

QGIS voting members are kindly asked to approve dedicating 13 k € 
towards the improvement of the QGIS server code base. 3k € would be 
dedicated to 3Liz and the rewriting of the QGSWxS project file parser. 
The other 10k € would be distributed between the companies 3Liz, 
Oslandia and Camptocamp, according to availability and expertise of 
their developers. The three companies should use the available funds to 
ensure the best possible outcome for the QGIS server community. Upcoming 
work includes:

- Finishing refactoring of GetPrint command

- Finishing refactoring of GetLegendGraphics command

- Refactoring of GetFeatureInfo

- Refactoring of DXF output in the GetMap command

- Ensure and Increase OGC compliance and performance

------------------

Tim - can you please set up Loomio voting and use the above text - feel 
free to improve upon it.

Thanks to all,

Andreas


On 23.06.2017 20:22, Tim Sutton wrote:
> Hi Andreas
>
> If the amounts will probably be above and beyond our discretionary 
> spend budget, we should just call for a loomio vote to keep things 
> transparent. If it is within a budget allocation then please just move 
> forward and do it. If we need to go the loomio route, I think we can 
> do it with a 1 week time frame. Can you provide me with the wording 
> for the proposal and I will post it?
>
> Regards
>
> Tim
>
> On Fri, Jun 23, 2017 at 5:57 PM, Andreas Neumann <andreas at qgis.org 
> <mailto:andreas at qgis.org>> wrote:
>
>     HI all,
>
>     So I wonder how we can proceed here. Some agree, there is noone
>     that disagrees but no decision?
>
>     How can we proceed? Do we need a Loomio vote from voting members
>     or is a PSC decision enough?
>
>     It seems like all agree about the 3k contribution for the WXS
>     parser removal project from 3Liz, but how about the other plans
>     from Oslandia? Do we need more information about these additional
>     projects?
>
>     Tim - I am specifically asking you for a decision on the way
>     forward - otherwise we will still discuss the same issues in 2-3
>     weeks from now and QGIS 3 will be released without a proper
>     rewrite of QGIS server.
>
>     If we can set a transparent decision process we can use the same
>     process for other similar projects (in or outside of the QGIS
>     grants process).
>
>     Thanks,
>     Andreas
>
>     On 20 June 2017 at 22:47, Tim Sutton <tim at qgis.org
>     <mailto:tim at qgis.org>> wrote:
>
>         Hi
>
>         +1 from me to support the refactoring work with 3k EUROS.
>
>         Regards
>
>         Tim
>
>         On Fri, Jun 16, 2017 at 5:32 PM, Régis Haubourg
>         <regis.haubourg at gmail.com <mailto:regis.haubourg at gmail.com>>
>         wrote:
>
>             Hi all,
>             that is very good news that we find some QGIS.org funds to
>             support some low level tasks that remain really hard to
>             fund otherwise.
>             3liz truely deserve this support since they put huge
>             efforts in QGIS server refactoring, thanks again to them
>             for that. Thanks Andreas for pushing this topic again.
>
>
>             Following the status update on qgis server refactoring
>             made here [0], here another update:
>
>             - we finally have our new website and published two web
>             articles on QGIS server security stress tests [1] and OGC
>             compliancy testing framework [2]
>
>             - Paul finished GetLegend graphics refactor [3]
>
>             - René Luc finished GetCapabilities /  GetContext /
>             DescribeLayer / GetStyles (GetStyle)
>
>             So now, mandatory actions pending now, René-Luc, Yves,
>             please correct me and tell us how much you need  :
>
>             - Richard, we got distracted by some mail routing
>             troubles, did you have Paul's mail for finding a way to
>             push the OGC html reports to test.qgis.org
>             <http://qgis.org> ?
>
>             -  GetPrint todo by Oslandia.  ~ at least 5000 euros but
>             composer rework can change it all.
>
>             - GetFeatureInfo, DXFWriter by 3Liz
>             - Testing by Real Users before during feature freeze :)
>
>             - Try to reach a 100 % OGC compliancy by fixing issues or
>             disabling some very edge cases. We are currently limited
>             by TeamEgine tool crashes. Paul is hot on doing the job,
>             but we'll need funding. I would start asking to something
>             like 5000 euros and see what we can do with it.
>
>             I can't evaluate the other tasks like pushing the
>             performance benchmark framework and define the reference
>             test set in it.
>
>             Cheers
>             Régis
>
>             [0]
>             https://lists.osgeo.org/pipermail/qgis-psc/2017-May/005316.html
>             <https://lists.osgeo.org/pipermail/qgis-psc/2017-May/005316.html>
>             [1]
>             http://oslandia.com/en/2017/06/14/qgis-server-security-aspect/
>             <http://oslandia.com/en/2017/06/14/qgis-server-security-aspect/>
>
>             [2]
>             http://oslandia.com/en/2017/06/16/qgis-server-ogc-cite-compliance-testing/
>             <http://oslandia.com/en/2017/06/16/qgis-server-ogc-cite-compliance-testing/>
>             [3] https://github.com/qgis/QGIS/pull/4699
>             <https://github.com/qgis/QGIS/pull/4699>
>
>             2017-06-13 12:50 GMT+02:00 Paolo Cavallini
>             <cavallini at faunalia.it <mailto:cavallini at faunalia.it>>:
>
>                 Hi all,
>
>                 Il 13/06/2017 10:23, Andreas Neumann ha scritto:
>
>                 > We briefly started discussing the support of the
>                 QGIS server refactoring.
>                 >
>                 > I would now propose that we pay 3Liz (René-Luc
>                 D'Hont) the quoted 3k €
>                 > for the QGIS server enhancement
>                 (QgsWXSProjectParser). Refactoring work
>                 > and under-the-hood changes that don't add new
>                 features is exactly that
>                 > kind of work that should be funded from QGIS.ORG
>                 <http://QGIS.ORG> <http://QGIS.ORG> in my
>                 > opinion.
>
>                 Agreed fully
>
>                 > Can the PSC decide on this, or do we need to ask our
>                 voting members? Do
>                 > we start a Loomio voting? I would like a quick
>                 decision - time is
>                 > ticking for QGIS 3 and there is summer break ...
>                 >
>                 > For your information, here is the financial
>                 situation of QGIS.ORG <http://QGIS.ORG>
>                 > <http://QGIS.ORG>:
>                 >
>                 https://docs.google.com/spreadsheets/d/18gwm83ENnIqNk0Hul-OlqggTHU4QeTqA-DvPmX8kK88/edit#gid=0
>                 <https://docs.google.com/spreadsheets/d/18gwm83ENnIqNk0Hul-OlqggTHU4QeTqA-DvPmX8kK88/edit#gid=0>
>                 > <https://docs.google.com/spreadsheets/d/18gwm83ENnIqNk0Hul-OlqggTHU4QeTqA-DvPmX8kK88/edit#gid=0
>                 <https://docs.google.com/spreadsheets/d/18gwm83ENnIqNk0Hul-OlqggTHU4QeTqA-DvPmX8kK88/edit#gid=0>>
>                 > with our actual expenses and income.
>                 >
>                 > I expect an addition 15k of income during June
>                 (sponsorings, PayPal,
>                 > contributions to Essen HF from FOSSGIS e.V. and
>                 QGIS-DE). On the
>                 > expenses side I expect invoices for 2.18 bug fixing
>                 at around 15k. The
>                 > Essen HF is almost fully covered by payments from
>                 FOSSGIS e.V. and
>                 > QGIS-DE. So we are financially in a good shape to
>                 fund additional work
>                 > around QGIS server.
>
>                 thanks for the update, quite reassuring
>
>                 > In addition, we should ask QGIS server devs (3Liz,
>                 Oslandia, Camptocamp,
>                 > Sourcepole) what other server work is pending to get
>                 it in a good state.
>
>                 agreed, it will be good to have a clear picture of
>                 what is missing, and
>                 the eventual stubling blocks
>
>                 thanks again
>                 --
>                 Paolo Cavallini - www.faunalia.eu <http://www.faunalia.eu>
>                 QGIS & PostGIS courses:
>                 http://www.faunalia.eu/training.html
>                 <http://www.faunalia.eu/training.html>
>                 https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis
>                 <https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis>
>                 _______________________________________________
>                 Qgis-psc mailing list
>                 Qgis-psc at lists.osgeo.org <mailto:Qgis-psc at lists.osgeo.org>
>                 https://lists.osgeo.org/mailman/listinfo/qgis-psc
>                 <https://lists.osgeo.org/mailman/listinfo/qgis-psc>
>
>
>
>             _______________________________________________
>             Qgis-psc mailing list
>             Qgis-psc at lists.osgeo.org <mailto:Qgis-psc at lists.osgeo.org>
>             https://lists.osgeo.org/mailman/listinfo/qgis-psc
>             <https://lists.osgeo.org/mailman/listinfo/qgis-psc>
>
>
>
>
>         -- 
>
>
>
>         *Tim Sutton*
>         QGIS Project Steering Committee Chair
>         tim at qgis.org <mailto:tim at qgis.org>
>
>         _______________________________________________
>         Qgis-psc mailing list
>         Qgis-psc at lists.osgeo.org <mailto:Qgis-psc at lists.osgeo.org>
>         https://lists.osgeo.org/mailman/listinfo/qgis-psc
>         <https://lists.osgeo.org/mailman/listinfo/qgis-psc>
>
>
>
>
>     -- 
>
>     --
>     Andreas Neumann
>     QGIS.ORG <http://QGIS.ORG> board member (treasurer)
>
>
>
>
> -- 
>
>
>
> *Tim Sutton*
> QGIS Project Steering Committee Chair
> tim at qgis.org <mailto:tim at qgis.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20170626/72dcfdcd/attachment.html>


More information about the Qgis-psc mailing list