<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Paolo, Hi all,<br>
</p>
<p>We just had the annual Swiss QGIS user group meeting yesterday.
Obviously we had to tell our users a little bit about what is
already finished, what is currently being worked on and what still
has to be worked on. So I had to compile a list:<br>
</p>
<p>What is already done:</p>
<ul>
<li>Migration to qt5 and Python 3</li>
<li>Python plugin update helper 2 to 3</li>
<li>Inheritable flexible properties framework (QEP 22)<br>
</li>
<li>Inbuilt task manager in QGIS for long running background tasks</li>
</ul>
<p>What is currently being worked on:</p>
<ul>
<li>QGIS 3 Windows packages (Jürgen)<br>
</li>
<li>Layer registry and legend tree refactoring (Martin) (QEP 76)<br>
</li>
<li>QGIS Server refactoring (devs from 3Liz, Alessandro,
Oslandia/Camptocamp?) (QEP 74)<br>
</li>
<li>Multiple canvas within a single project (Alvarao and Nyall)
(QEP 70)<br>
</li>
<li>Application Profiles and Unified Settings (Nathan) (QEP 50)</li>
<li>Generic Helping System for QGIS (Richard) (QEP 32)</li>
<li>Improved Node Tool (Martin) (QEP 69)<br>
</li>
</ul>
<p>What still needs to be worked on:</p>
<ul>
<li>Print composer refactoring (QEP 23) (Nyall)<br>
</li>
<li>Reporting mode for print composer (Nyall)<br>
</li>
<li>Porting core of Processing to C++ (Nyall)<br>
</li>
<li>Redesign of GUI of fields/widgets/forms (QEP 21) (Matthias)<br>
</li>
<li>Improving the loading/display performance for complex forms
with lots of relations (Matthias)<br>
</li>
<li>Rename compositions to layouts (QEP 25) (Nyall)</li>
<li>Project backup and versioning (Nathan)<br>
</li>
<li>More unit tests (QEP 17, QEP 24) (all devs)<br>
</li>
<li>Documentation of API changes (all devs)<br>
</li>
<li>Finishing registration of QGIS legal entity, logo, etc. (QGIS
board and PSC)<br>
</li>
<li>Visual changelog (all)<br>
</li>
</ul>
<p>I probably missed a lot of stuff in the above lists, and it is my
own point of view, but it may help for a dicussion around the
current state of QGIS 3.<br>
</p>
<p>From the above list it is obvious that we can't feature-freeze
soon (with a single three-month dev cycle) and that we need the
double dev cycle we already discussed. One realistic feature
freeze time could be somewhere in May, and a possible release date
could be around July. But obviously it is Jürgen who decides. He
may have different ideas.</p>
<p>Some good news:</p>
<p>The Swiss QGIS user group decided yesterday to fund a few of the
above "what still needs to be worked on" list:</p>
<ul>
<li>Print composer refactoring (Nyall)</li>
<li>Porting core of Processing to C++ (Nyall)</li>
<li>Redesign of GUI of fields/widgets/forms (Matthias)</li>
<li>Improving the loading/display performance for complex forms
with lots of relations (Matthias)<br>
</li>
</ul>
<p>Further print composer work and work on the new reporting mode
still needs funding. Probably also processing work could use some
love and funding, esp. once the porting of Processing core to C++
is finished.<br>
</p>
Hope all of this helps a bit to get a picture where we are. Please
help complement the picture!<br>
<br>
Finally, I propose that we very soon do another round of QGIS
grants. We are doing quite well financially (the call for funding
helped) and can now afford to spend another 20k € on more grant
projects.<br>
<br>
Andreas<br>
<br>
<div class="moz-cite-prefix">On 26.01.2017 19:32, Paolo Cavallini
wrote:<br>
</div>
<blockquote
cite="mid:441ce7a6-fbe4-8aa3-263c-113bbc309674@faunalia.it"
type="cite">
<pre wrap="">Hi all,
I have to give a short talk on the current status of QGIS3 and the
outlook for the future. The main aim is to grow interest, and ultimately
attract testers, developers, and sponsors.
Topics I thought of are:
* current development state
* what's new for the user
* what's new for the developer
* what's the most likely roadmap and timing
* what to do about plugins (when starting to upgrade, how to do it).
I thought to dig through commits and QEPs, but it' a big amount of work,
and from this fine graded scale it's very difficult to get the whole
picture, not to say about outlooks.
I think this is of relevance to this list, as it could be a good chance
to have a clear picture to communicate to users. I'd be glad of doing
this as a cooperative effort, so this could be used to communicate it
worldwide.
I'd therefore be grateful of any suggestion.
Thanks for any hint.
</pre>
</blockquote>
<br>
</body>
</html>