<div dir="ltr"><div>Hi,</div><div><br></div><div>For reference, the random issue report mentioned by alexis is <a href="https://github.com/qgis/QGIS-Documentation/issues/6331">https://github.com/qgis/QGIS-Documentation/issues/6331</a></div><div><br></div><div>There was a time Havard and myself used to add the section in which an issue report could be adressed but we were unfortunately most of the times the ones who finally addressed them so we stopped doing it.</div><div>Following Alexis request I added a bunch of new labels, indicating the main chapters in which they could be addressed. Yes, we have tens of labels ;( but seems that we are still far behind the code repo ;)</div><div><br></div><div> So far, the logic I followed is to split in kind of "themes" and the more labels the more accurate the chapter indication. eg:</div><div>* "vector" + "properties" --> This info should go to the properties chapter of vector</div><div>* "vector" + "raster" + "properties" --> This info should go in both the properties chapters of vector and raster<br></div><div>* "style manager" + "labels" --> this belongs to the labels chapter under the style manager chapter</div><div>* "vector" + "labels" --> belongs to labels section in the vector layer properties chapter (so probably, "properties" would also be added)</div><div>*...</div><div><br></div><div>Opinions?<br></div><div>If we go that way (if, not scratching that wouldn't take time, no worries!), what remains is to describe each label, so that potential contributors can understand, and apply them to reports. Also worth a line in the guidelines or readme. I think a team for triaging (same as the QGIS repo has) is necessary and my attempt to create one few hours ago just failed.</div><div><br></div><div>Regards,</div><div>Harrissou<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 21 avr. 2021 à 18:28, Alexandre Neto <<a href="mailto:senhor.neto@gmail.com">senhor.neto@gmail.com</a>> a écrit :<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="auto"><div dir="auto">Hi,</div><div dir="auto"><br></div><div dir="auto">Thanks for raising this </div><div dir="auto"><br></div>I am not sure tags would work. We already have tags for which documents should be affected (users manual, training, pyqgis cookbook, etc) but indicating where in each document to edit would fill the tags list.<div dir="auto"><br></div><div dir="auto">Nevertheless, maybe a comment from an seasoned writer suggesting places in each doc that need to be updated could be of great help for new comers.</div><div dir="auto"><br></div><div dir="auto">All the best,</div><div dir="auto"><br></div><div dir="auto">Alexandre Neto</div><div dir="auto"><br></div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">A quarta, 21/04/2021, 16:46, Alexis R.L. <<a href="mailto:alroyliz0@gmail.com" target="_blank">alroyliz0@gmail.com</a>> escreveu:<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"><div dir="ltr"><div>Greetings,</div><div><br></div><div>I would like to propose something that I mentioned as a comment on a random issue.</div><div><br></div><div>I think that adding tags to show where documentation should be added to resolve issue would be of great help to any potential contributors.</div><div><br></div><div>Currently the documentation process is pretty dry. Documentation is mostly done by a handful of people that are quite familiar with the documentation.</div><div><br></div><div>I think that adding tags to issue in order to indicate where the information should be modified would be of great help. Knowing if only one or more place must be modified and where the information must be modified is crucial to help people less familiar with the documentation.</div><div><br></div><div>The tags could also be used to solve all outstanding issues with a single file more efficiently.</div><div><br></div><div>I totally agree that this would be an additional burden. I can propose something more concrete in terms of naming and coloring for tags and tag some issues to alleviate some issues.</div><div><br></div><div>This would also help when doing community events to make things less intimidating.</div><div><br></div><div>I am not sure if this will be touched by Alessandro in his proposal following the exchanges on the other mailing list. Otherwise I think this is quite complimentary.</div><div><br></div><div>Thanks and have a nice day!</div><br clear="all"><div><div dir="ltr"><div dir="ltr">Alex</div></div></div></div></div>
_______________________________________________<br>
Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..<br>
<a href="mailto:Qgis-community-team@lists.osgeo.org" rel="noreferrer" target="_blank">Qgis-community-team@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a><br>
</blockquote></div>
_______________________________________________<br>
Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..<br>
<a href="mailto:Qgis-community-team@lists.osgeo.org" target="_blank">Qgis-community-team@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a><br>
</blockquote></div>