<div dir="ltr"><div>HI All</div><div>I think we need to be kind here so I support a new label 'solution proposed' with the added automations in closing it. Whilst I agree with some sentiments in that users need to understand how a lot of info can get unmanageable and taxing on resources, we need to educate users on how this stuff works and how we need them to keep on bringing their input to the project. <br></div><div><br></div><div></div><div>So I think on the side of the developer (I am assuming here - please correct if wrong), when researching the issue, you have found a solution already and thus it's not too taxing to paste a link to the solution and label it 'solution proposed' - therefore no more work done.</div><div><br></div><div>On the side of the user reporting the issue (which I identify with more), you are providing an education on how to contribute to the project through this feedback. Once it is closed, an automatic message could include some of the following guidelines:</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">...tell that they are not a defect in<br>
the source code. If you are wrong and the person follows up with<br>
evidence, hit reopen - no big deal.<br>
<br>
For feature requests that are fuzzy, ask that they get shaken out on<br>
some other forum and then refiled, when they can say with some<br>
precision what the new feature should do.
</blockquote><div><br></div><div><br></div><div>Cheers</div><div>Em <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 19 Jan 2024 at 18:43, Thomas Larsen Wessel via QGIS-Developer <<a href="mailto:qgis-developer@lists.osgeo.org">qgis-developer@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Nyall wrote: "
It seems wrong to just close that issue without giving the reporter time to reply "<div><br></div><div>If a user spends a long time (for me it sometimes takes as much as a few hours, believe it or not) to write an issue, believing it actually is a bug or at least an issue with the docs that ought to be corrected, it will like seem unappreciated if the issue is closed in the very first response, specially if that response is very brief and does not contain any appreciation. Even if that is not how it is intended. </div><div><br></div><div>When I report issues it's not always because its a real problem for me; it is often simply because I believe it's in the interest of the project, and it's my tiny contribution to that project. <br></div><div><br></div><div>Tickets that are obviously just questions, should IMO be closed immediately, with advice on where to ask such questions. But when people report what to them seems like a bug, I would encourage a friendly response that signals that even if their effort was in vain because it was not a bug, it actually is appreciated. Especially if it's a well written issue. I'm afraid that "closed" signals very little appreciation; a lot less appreciation than "not a bug" and then closing a few days later. Having an issue closed like that seems/feels almost like having a forum thread deleted, does it not?</div><div><br></div><div>Apropos of appreciation, I really appreciate the work that all of you are doing for QGIS and other FOSS. Have a nice weekend :)</div><div><br></div><div>Sincerely, Thomas</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 18, 2024 at 10:01 PM Sandro Santilli via QGIS-Developer <<a href="mailto:qgis-developer@lists.osgeo.org" target="_blank">qgis-developer@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Jan 17, 2024 at 08:57:33AM -0500, Greg Troxel via QGIS-Developer wrote:<br>
<br>
> So I would say:<br>
> <br>
> Establish a policy that questions are not allowed in the issue<br>
> tracker. Follow it strictly.<br>
<br>
+1 and there's now an experimental Discourse service of OSGeo that<br>
could be used for questions: <a href="https://discourse.osgeo.org" rel="noreferrer" target="_blank">https://discourse.osgeo.org</a><br>
(an appropriate category could be added, on request)<br>
<br>
--strk;<br>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</blockquote></div>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div style="margin-bottom:20px;font-family:verdana,sans-serif;color:rgb(68,68,68)">Emma Hain — Product Manager/Senior GIS Analyst<br>
<a href="mailto:emma@north-road.com" style="color:rgb(78,141,175);text-decoration:none" target="_blank">emma@north-road.com</a> <br></div>
<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><table>
<tbody>
<tr>
<td><img alt="https://north-road.com" src="https://ci3.googleusercontent.com/mail-sig/AIorK4z-QyPD9kQRyEtpg0YHp_bVoq466HfPMkJXDWxnwTf1qCIBS8c19W29po6b7akLq2btEedEMKg"><br></td>
<td><font color="#444444"><font face="verdana, sans-serif"><b>North Road</b><br>Cartography • Development • Spatial Analysis</font><br><hr style="height:1px;background-color:rgb(219,210,143);color:rgb(219,210,143);border:medium">
<span><font face="verdana, sans-serif"><a href="http://north-road.com" style="color:rgb(78,141,175);text-decoration:none" target="_blank"><b>north-road.com</b></a><span></span><br><a href="https://twitter.com/northroadgeo" target="_blank"><img src="https://ci3.googleusercontent.com/mail-sig/AIorK4xbsQ72BNIM2cWMZcuEKVer1Bwaq_gqYkdbtrjK2ifrqv-4o7aWjcvilgYXtNGpXLNgD00xgmQ"></a></font></span></font><a href="https://www.linkedin.com/company/north-road-studios" target="_blank"><img src="https://ci3.googleusercontent.com/mail-sig/AIorK4zEBWGJKio8gqmFT0h_51t4ZnmoGgbmV7SeL-4FKvwWApFWDWyK7p-c0-cSskUe7pjQzjEZj9Q"></a><a href="https://www.facebook.com/North-Road-997236690392419/home" target="_blank"><img src="https://ci3.googleusercontent.com/mail-sig/AIorK4wlMciFPm8hqQZB_Qi57PUCv1dJqUC1A2i9qEMzWRFLcJ7Jil30YnULdJLxT6-qMfI6J4kcac4"></a><font color="#444444"><span><font face="verdana, sans-serif"><br><img src="https://womenindigital.org/wp-content/uploads/2023/03/WID-Membership-Badge.jpg" width="96" height="48"><br></font></span></font></td> </tr></tbody></table></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>