
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>

<p>Hi all, Hi Nathan,</p>

<p>I am looking at the QEPs from time to time that and I think it needs a little attention. Quite a few proposals would be ready to make a decision. Some QEPs are ready but lack funding. Perhaps we can introduce a new label stating "Needs funds" or something similar? It would help potential funders to pick things they like to see implemented. Quite a few of the proposals are already implemented, sometimes even if they don't have the "Accepted label" - i guess some of the implementations had time pressure due to the 2.16 list and thus couldn't wait for voting/acceptance.</p>

<p>Devs want to start working on many of the issues mentioned in the QEPs - so decisions need to be taken in a timely manner.</p>

<p>Here are some of my personal suggestions for changes / closings:</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/42">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/42</a> (Compulsory Unit Tests for Core Changes) - discussion stalled - but I think now would be the perfect timing to implement this proposal.</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/40">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/40</a> (Geometry redesign) - was implemented already 2 or 3 versions ago - should be accepted and closed</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/59">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/59</a> (aggregate functions) is accepted, implemented - it can be closed</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/58">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/58</a> (QGIS Styles, Symbols ans SVG Markers Sharing Repository) - is currently being implemented by Akbar - shouldn't it be voted on/accepted?</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/53">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/53</a> (WFS provider enhancements) - is already implemented and should be closed</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/49">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/49</a> (Label mask) - would be ready to implement, but lacks funding (add the new "Needs funds" label?)</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/46">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/46</a> (Labling path) - <span>would be ready to implement, but lacks funding (add the new "Needs funds" </span><span>label</span><span>?)</span></p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/45">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/45</a> (Long term releases) - implemented - should be closed</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/43">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/43</a> (Rename Compositions to Print Layouts) - would be good to be addressed during work for 3.x - can we continue discussion and vote on it?</p>

<p> - <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/39">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/39</a> (Layout rework (composer v2)) - Nyall wants to start on this - so it should be discussed and accepted</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/38">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/38</a> (Inheritable property collections) - unsure about the status here, apparently it has a prototype implementation. How does this relate to the variable system introduced recently?</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/37">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/37</a> (Fields and Forms Redesign) - would be a good candidate to be implemented during QGIS 3.x - probably lacks funding</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/35">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/35</a> (Authentication configuration system with master password) - already implemented. Should be accetped and closed.</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/32">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/32</a> (Add QGIS server access control interface for python plugins) - already implemented. Should be accepted and closed:</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/31">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/31</a> (QGIS Legal Entity) - accepted by Loomio vote and mostly implemented. Should be acepted and closed.</p>

<p>- <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/29">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/29</a> (QGIS 3.0) - discussion maybe a bit outdated? Close?</p>

<p> </p>

<p>It would be good, if we, as the project would take the QEPs a bit more seriously and maintain them accordingly. Seems like some devs do, some don't. Any comments?</p>

<p>Thanks and greetings,</p>

<p>Andreas</p>

<div> </div>

</body></html>