[Qgis-community-team] Proposal: destination tag for issues

[DelazJ]

Hi,

For reference, the random issue report mentioned by alexis is
https://github.com/qgis/QGIS-Documentation/issues/6331

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.
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 ;)

So far, the logic I followed is to split in kind of "themes" and the more
labels the more accurate the chapter indication. eg:
* "vector" + "properties" --> This info should go to the properties chapter
of vector
* "vector" + "raster" + "properties" --> This info should go in both the
properties chapters of vector and raster
* "style manager" + "labels" --> this belongs to the labels chapter under
the style manager chapter
* "vector" + "labels" --> belongs to labels section in the vector layer
properties chapter (so probably, "properties" would also be added)
*...

Opinions?
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.

Regards,
Harrissou

Le mer. 21 avr. 2021 à 18:28, Alexandre Neto <senhor.neto at gmail.com> a
écrit :

> Hi,
>
> Thanks for raising this
>
> 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.
>
> 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.
>
> All the best,
>
> Alexandre Neto
>
>
>
> A quarta, 21/04/2021, 16:46, Alexis R.L. <alroyliz0 at gmail.com> escreveu:
>
>> Greetings,
>>
>> I would like to propose something that I mentioned as a comment on a
>> random issue.
>>
>> I think that adding tags to show where documentation should be added to
>> resolve issue would be of great help to any potential contributors.
>>
>> Currently the documentation process is pretty dry. Documentation is
>> mostly done by a handful of people that are quite familiar with the
>> documentation.
>>
>> 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.
>>
>> The tags could also be used to solve all outstanding issues with a single
>> file more efficiently.
>>
>> 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.
>>
>> This would also help when doing community events to make things less
>> intimidating.
>>
>> 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.
>>
>> Thanks and have a nice day!
>>
>> Alex
>> _______________________________________________
>> Qgis-community-team mailing list for organizing community resources such
>> as documentation, translation etc..
>> Qgis-community-team at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/qgis-community-team
>>
> _______________________________________________
> Qgis-community-team mailing list for organizing community resources such
> as documentation, translation etc..
> Qgis-community-team at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-community-team
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-community-team/attachments/20210421/30455fbc/attachment.html>