<p dir="ltr">It sounds great. I agree that QGIS Server needs a dedicated effort and coordination.<br>
We (gis3w) will try to contribute. We are not C++ devs but we have summed a significative experience with QGIS Servers's strengths and weeknesses. We will partecipate to the discussions on the "high level" roadmap ;)</p>
<p dir="ltr">giovanni</p>
<div class="gmail_extra"><br><div class="gmail_quote">Il 26 set 2016 15:35, "René-Luc Dhont" <<a href="mailto:rldhont@gmail.com">rldhont@gmail.com</a>> ha scritto:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi Alessandro,<br>
<br>
I'm working with my colleague David on the QEP about new server
architecture.<br>
<br>
Regards,<br>
<br>
<div>Le 25/09/2016 à 10:06, Alessandro
Pasotti a écrit :<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Hi,<br>
<br>
</div>
I'm glad that Matthias's semi-serious threats
to remove the server from source tree and
Nyall's complaints have shaken the souls of
the server people!<br>
<br>
</div>
I insist that the server remains a first class
citizen and a full featured tool within the QGIS
project, but I understand that it should not be
a brake for the core refactoring ,slowing down
the amazing development that QGIS dev team is
doing on the core and gui libraries.<br>
<br>
</div>
I've just started a small WIP contribution aimed
to solve a first issue (<a href="https://github.com/qgis/QGIS/pull/3528" target="_blank">https://github.com/qgis/QGIS/<wbr>pull/3528</a>).<br>
<br>
</div>
I wonder what would be the better way to coordinate
the efforts, gain in efficience and avoid
duplication.<br>
<br>
</div>
This is a possible roadmap (suggestions welcome!):<br>
<br>
</div>
- start a QEP for the new server architecture (C++
plugins for the core services etc.) (@rldhont, can you
take care of this?)<br>
</div>
- a list of prioritized issues (on the qgis hub?, on
github? no idea here) ( @nyall, @mkuhn: you know the new
and old API very well, if you could start creating a list
of must-have, should-have, nice-to-have issues it would be
very helpful)<br>
</div>
- create a formal (but completely open) dedicated team of
developers and assign issues<br>
</div>
<div>- possibly, meet periodically to coordinate the
development<br>
</div>
<br>
</div>
Am I dreaming?<br clear="all">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div><br>
-- <br>
<div>Alessandro
Pasotti<br>
w3: <a href="http://www.itopen.it" target="_blank">www.itopen.it</a></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br>
Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br></blockquote></div></div>