[Qgis-community-team] Tasks for writing Documentation

[DelazJ]

Hi,

Larissa, I can not answer your request for structuring and strategy but, if
you are looking for 3.4 issues, no need for a label, everything is already
there:
#. Go to the issues page https://github.com/qgis/QGIS-Documentation/issues
#. Press the "milestones" drop-down menu
#. Choose whatever is lesser than 3.6 and you have issues potentially
compatible with 3.4
An alternative is to go to
https://github.com/qgis/QGIS-Documentation/milestones and pick whatever is
<3.6 and you get the lists.

To understand, most of the documentation issues are automatically generated
(by the so called "QGIS-feature-tracker" author) when a new feature is
added to the software and assigned the release number they belong to in the
"milestone" property.

Side note: It would be nice we go through 2.x remaining issues and check
whether these features are still compatible with 3.x and upgrade their
milestone (in order to close 2.x milestones).

Regards,
Harrissou

Le jeu. 1 août 2019 à 18:00, Larissa Junek <l.junek at gmx.net> a écrit :

> Hello,
>
> I'd like to go back to the discussion below. Can we structure our work on
> the documentation?
>
> I would be interested in working only on issues that are dedicated to the
> 3.4 user manual. At my work, my colleagues really need a complete
> documentation.
>
> I can work for up to 5hours a week on the documentation.
>
> Actually, I need an updated issue list with the label backport to 3.4.
>
> Do you guys have any other suggestions?
>
> Cheers, Larissa
> Am 30.03.2019 um 00:44 schrieb Alexandre Neto:
>
> I see Larissa point, maybe we could give a look and pick some priorities.
> For example, big features that are totally undocumented.
>
> A sex, 29/03/2019, 16:17, matteo <matteo.ghetta at gmail.com> escreveu:
>
>> Hi Larissa,
>>
>> > Hello guys,
>> > I started writing documentation for qgis 3.4 in march. For me it would
>> > be easier to contribute if there is a guideline about which tasks I will
>> > have until next year.
>> > Can we define tasks for me?
>> >
>> > I started with the snap-to-grid feature and the print composer.
>> >
>> > From your point of view: what are the priorities (at the moment)?
>>
>> I suggested to start having an issue triage of the doc repository. I
>> really think this is the right place where to start
>>
>> https://github.com/qgis/QGIS-Documentation/issues
>>
>> by picking up an issue you can add a comment to it saying you are
>> working on that and nobody will take the same issue
>>
>> We can still try to figure out the main priorities, but starting by
>> picking up some issue is a good start IMHO
>>
>> Cheers and thanks
>>
>> Matteo
>>
>> _______________________________________________
>> 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
>
> --
> Alexandre Neto
> ---------------------
> @AlexNetoGeo
> http://sigsemgrilhetas.wordpress.com
> http://gisunchained.wordpress.com
>
> _______________________________________________
> Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..Qgis-community-team at lists.osgeo.orghttps://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/20190801/0765e562/attachment.html>