<html><head></head><body>Agreed, thanks Richard for the link, and Nyall for writing the article.<br><br><div class="gmail_quote">Il 9 aprile 2019 10:25:49 CEST, Richard Duivenvoorde <rdmailings@duif.net> ha scritto:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On 09/04/2019 03.41, Nyall Dawson wrote:<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">If you can suggest any ways to improve the wording of that post (while<br>keep the core message intact), please let me know.<br></blockquote><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;">On Mon, Apr 8, 2019 at 4:30 AM Paolo Cavallini <cavallini@faunalia.it> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;">may I suggest you an interesting read?<br><a href="https://nyalldawson.net/2016/08/how-to-effectively-get-things-changed-in-qgis/">https://nyalldawson.net/2016/08/how-to-effectively-get-things-changed-in-qgis/</a><br></blockquote></blockquote></blockquote></blockquote></blockquote><br>I want to second Cory, to me it also feels a little rude to tell a<br>'user' (not a developer) to try to code or pay for a dev. And I'm a<br>dutchie, known for their blunt talk :-)<br><br>@Nyall: in my opinion your followup article:<br><a href="http://nyalldawson.net/2016/08/how-to-effectively-get-things-changed-in-qgis-a-follow-up/">http://nyalldawson.net/2016/08/how-to-effectively-get-things-changed-in-qgis-a-follow-up/</a><br>has a better 'tone' for non developers.<br><br>We should probably mix your followup article with the first one and put<br>it in the website (in the 'user' section) so it is translatable, so<br>translators can maybe even add more 'cultural politness' to it if needed?<br><br>WHO wants to do that (you can earn karma points if you do this !!)??<br><br>We should also make clear that it IS OK to ask for the community to have<br>a look at the an issue which makes your(!) live a hell. But also make it<br>clear that to be fair your problems are not always the problems of<br>somebody else. Same goes for commercial software by the way, only they<br>are not as transparent as we are. And that we are humans with not enough<br>time to solve all the problems in the world.<br><br>STILL I'm not sure what the right tone is to tell people to read such a<br>text though... people (me included!) will feel a little offended anywat<br>when not helped but sent to a page to read what they should do...<br><br>I think Geoserver does a good job:<br><br><a href="https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer">https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer</a><br>And Ian's talk: (though it can maybe be polished a little):<br><a href="https://www.ianturton.com/talks/foss4g.html#/how-to-earn-support">https://www.ianturton.com/talks/foss4g.html#/how-to-earn-support</a><br><br><br>@Cory: please stay on the good side :-)<br><br>May I suggest to make your bug report even better by adding data and<br>instructions so for an average developer, it is 10 minutes work to<br>replicate your issue? Or should we just create the table and start<br>editing? If so please add some steps. For example some googling revealed<br>to me that I need: "CREATE EXTENSION IF NOT EXISTS "uuid-ossp";" to use<br>the uuid_generate_v4() function you use?<br><br>Also make sure it is actually a QGIS problem, looking into it, it is.<br>But it is also a data-schema issue, as you define the problematic<br>columns as:<br>predecessors uuid[] DEFAULT ARRAY[]::uuid[],<br>And the "uuid[]" is not a very common type in the gis world.<br><br>If I'm correct '{""}' (what QGIS now uses for NULL values if the column<br>has an array type) is a textual representation of an array with one<br>string in it. Would it be better to do '{null}' or even '{}' instead?<br>Can you try to create an update query with '{null}' and '{}' values in<br>the empty array fields?<br>And add these queriies to the bug report?<br><br>Regards,<br><br>Richard Duivenvoorde<hr>QGIS-Developer mailing list<br>QGIS-Developer@lists.osgeo.org<br>List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre></blockquote></div><br>-- <br>Sorry for being short</body></html>