<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello,</p>
<p>I'd like to go back to the discussion below. Can we structure our
work on the documentation?</p>
<p>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.</p>
<p>I can work for up to 5hours a week on the documentation. <br>
</p>
<p>Actually, I need an updated issue list with the label backport to
3.4.</p>
<p>Do you guys have any other suggestions?</p>
<p>Cheers, Larissa<br>
</p>
<div class="moz-cite-prefix">Am 30.03.2019 um 00:44 schrieb
Alexandre Neto:<br>
</div>
<blockquote type="cite"
cite="mid:CA+H0G_Fp-vO4PoEfHa37cnpZ+yG6_qk6+iDAmqX3=4dELu=3Kw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
I see Larissa point, maybe we could give a look and pick some
priorities. For example, big features that are totally
undocumented. <br>
<br>
<div class="gmail_quote">
<div dir="ltr">A sex, 29/03/2019, 16:17, matteo <<a
href="mailto:matteo.ghetta@gmail.com" moz-do-not-send="true">matteo.ghetta@gmail.com</a>>
escreveu:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Larissa,<br>
<br>
> Hello guys,<br>
> I started writing documentation for qgis 3.4 in march.
For me it would<br>
> be easier to contribute if there is a guideline about
which tasks I will<br>
> have until next year.<br>
> Can we define tasks for me?<br>
> <br>
> I started with the snap-to-grid feature and the print
composer.<br>
> <br>
> From your point of view: what are the priorities (at the
moment)?<br>
<br>
I suggested to start having an issue triage of the doc
repository. I<br>
really think this is the right place where to start<br>
<br>
<a href="https://github.com/qgis/QGIS-Documentation/issues"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/qgis/QGIS-Documentation/issues</a><br>
<br>
by picking up an issue you can add a comment to it saying you
are<br>
working on that and nobody will take the same issue<br>
<br>
We can still try to figure out the main priorities, but
starting by<br>
picking up some issue is a good start IMHO<br>
<br>
Cheers and thanks<br>
<br>
Matteo<br>
<br>
_______________________________________________<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" moz-do-not-send="true">Qgis-community-team@lists.osgeo.org</a><br>
<a
href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a></blockquote>
</div>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>Alexandre Neto</div>
<div>---------------------</div>
<div>@AlexNetoGeo</div>
<div><a href="http://sigsemgrilhetas.wordpress.com"
moz-do-not-send="true">http://sigsemgrilhetas.wordpress.com</a></div>
<a href="http://gisunchained.wordpress.com"
moz-do-not-send="true">http://gisunchained.wordpress.com</a><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-community-team@lists.osgeo.org">Qgis-community-team@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a></pre>
</blockquote>
</body>
</html>