<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Next try, it seems the message body too big.<br>
</p>
<div class="moz-forward-container"><br>
-------- Forwarded Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
</th>
<td>training manual update</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Thu, 23 Feb 2017 16:36:09 +0300</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td>Janneke van Dijk <a class="moz-txt-link-rfc2396E" href="mailto:janneke.qgis@gmail.com"><janneke.qgis@gmail.com></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:qgis-community-team@lists.osgeo.org">qgis-community-team@lists.osgeo.org</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<p>Dear Harissou, dear list,</p>
<p>Let's see if this now works via the list, indeed better to keep
it public.</p>
<p>I will use 2.18.3 as reference. I'm working on Windows, not
sure what to do with the screenshots as the 'standard' is to use
linux for uniformity, but VM is not working very smoothly for
me. Any suggestions?</p>
<p>I'll have some time tomorrow to get into it, will start from
the beginning and see what it brings. Is there a practical way
to discuss proposed changes, something similar to comments in
Word? Or does that come for each change following a PR?</p>
<p>I'm sure I'll have plenty of questions tomorrow...</p>
<p>Janneke<br>
</p>
<p><br>
</p>
<p>Hi Janneke,<br>
<br>
<br>
</p>
<div class="gmail_quote">2017-02-21 17:33 GMT+01:00 Janneke van
Dijk <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jvandijk@chanzo.nl" target="_blank">jvandijk@chanzo.nl</a>></span>:<br>
<blockquote class="gmail_quote">
<div>
<div class="gmail-m_409028092341442216moz-cite-prefix">Hi
Harissou,<br>
<br>
Thanks for your extended explanation!<br>
So, I've got a github account, set it up with source tree,
cloned the repo.<br>
<br>
</div>
</div>
</blockquote>
<div>Good. If you have question on github/git, do not hesitate
either. <br>
</div>
<blockquote class="gmail_quote">
<div>
<div class="gmail-m_409028092341442216moz-cite-prefix"> I
had a look at the open issues you mentioned, but with none
of them it's completely clear to me what should be done (I
guess I was hoping there was a very concrete and clear
issue to be starting with and get me over my cold water
fear....). In addition, should these be done bearing in
mind 2.14 or 2.18? (not sure if it makes a difference).<br>
<br>
</div>
</div>
</blockquote>
<div>Yes.. To be honest, the easiest issues have been fixed and
those available mostly require to have a global overview of
the manual or a precise knowledge of the context - I guess
it's the main reason they are not yet tackled<br>
<br>
</div>
<div>About the release to focus on, I'd say: "Just forget 2.14";
it's now an old release and our main target is to release a
doc few weeks after a ltr is released (hopefully, for 3.2?),
so we should not spend energy on such an old release.<br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote">
<div>
<div class="gmail-m_409028092341442216moz-cite-prefix"> As
it is my plan for the next few days to go systematically
through the training manual, it would make sense to me to
either make necessary changes/updates as I encounter them,
or somehow keep track of them.</div>
</div>
</blockquote>
<div> </div>
<div>Yes do it that way, and if you find issues you can't fix
alone, please report it and we'll try together.<br>
</div>
<div> </div>
<blockquote class="gmail_quote">
<div>
<div class="gmail-m_409028092341442216moz-cite-prefix"> To
make the changes as I encounter them, I would need to know
what version to change it for, wouldn't I? If it were for
2.18, would I still have to wait until further notice, or
could I get started already? As I'm completely new to
github and collaborating this way I have no idea what the
most efficient/useful workflow would be in this situation.
<br>
<br>
</div>
</div>
</blockquote>
<blockquote class="gmail_quote">
<div>
<div class="gmail-m_409028092341442216moz-cite-prefix"> Of
course, if it doesn't make sense to get started already
I'd better wait until further notice.<br>
</div>
</div>
</blockquote>
<div><br>
Target 2.18, please. There are imo less changes between 2.18
and 3.0 than between 2.0 and 2.18. So the doc would still be
more up to date when time comes for a newer release. Some
points that we'd need to check in the manual:<br>
</div>
<div>- steps to reach some tools<br>
</div>
<div>- screenshots (some instructions at <a
moz-do-not-send="true"
href="http://docs.qgis.org/testing/en/docs/documentation_guidelines/writing.html#managing-screenshots">http://docs.qgis.org/testing/en/docs/documentation_guidelines/writing.html#managing-screenshots</a>)<br>
<br>
<br>
<br>
<br>
</div>
<div>In your first message, you mentioned that you were
struggling to reach qgis-community list. Any news on this
issue? I think it'd be nice to discuss doc contribution steps
(and especially beginners integration) in that list to attract
more users and help demystify things.<br>
</div>
<div>I've been contacted recently by another user willing to
contribute so maybe we are at a period where we can catch more
writers.... and "coaching" in mailing-list sounds more
long-term efficient (and helpful for more people) than
chatting in a restricted group: let's be open... :)<br>
</div>
<div><br>
<br>
</div>
<div> If there are any points I didn't address let me know...<br>
Looking forward to writing doc with you,<br>
<br>
</div>
<div>Harrissou<br>
</div>
<blockquote class="gmail_quote">
<div>
<div class="gmail-m_409028092341442216moz-cite-prefix"><br>
thanks for your advice,<br>
Janneke
<div>
<div class="gmail-h5"><br>
<br>
<br>
<br>
On 20-Feb-17 19:17, DelazJ wrote:<br>
</div>
</div>
</div>
<div>
<div class="gmail-h5">
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>Hi Janneke,<br>
<br>
</div>
Thanks for offering your help. The Training
Manual is indeed from an old release and would
really deserve some love and time (few fixes
these last years). So, if you wish to
improve/update it, I can ensure you that you are
more than welcome. Everybody is welcome to
contribute to QGIS (including documentation,
translation, bug reports and fixes...)<br>
</div>
<br>
What are the plans... ?<br>
* Except for fixes, we no longer work on QGIS
2.14 documentation<br>
<br>
* For QGIS Documentation, I think that due to
some recent news, there will probably be a 2.18
(LTR?) doc release.<br>
When? Don't know yet. But unless there's enough
activity in the repo to fix remaining bugs, I'd
say maybe middle march (this is actually the
deadline <b>I set to myself </b>to stop
contributing to the 2.x bug fixes). Of course, we
can extend that if need be.<br>
<br>
That means that with the 2.18 doc release, we'd
embed a Training manual which could be updated or
no, depending on contributions. However, I'm not
enough involved in this chapter to tell you if you
should better rework it from a 2.18 perspective or
wait for a 3.0. In a recent discussion in
psc-list, Paolo Cavallini (cc-ed) offered to
maintain the Processing part of the manual (<a
moz-do-not-send="true"
href="https://lists.osgeo.org/pipermail/qgis-psc/2017-January/005048.html"
target="_blank">https://lists.osgeo.org/<wbr>pipermail/qgis-psc/2017-<wbr>January/005048.html</a>).
Maybe he has a better overview and can help you
decide.<br>
<br>
Meanwhile, given that you are ready to help now,
there still are some issues in the
QGIS-Documentation repo that need to be tackled (<a
moz-do-not-send="true"
href="https://github.com/qgis/QGIS-Documentation/issues?q=is%3Aopen+is%3Aissue+label%3A%22Training+Manual%22"
target="_blank">https://github.com/qgis/QGIS-<wbr>Documentation/issues?q=is%<wbr>3Aopen+is%3Aissue+label%3A%<wbr>22Training+Manual%22</a>).<br>
</div>
<br>
* we might be waiting for a consensus or an
authoritative decision (?) to begin working on QGIS
3 doc (so no plans for the moment)<br>
<div><br>
As I have already mentioned, you are welcome. Feel
free to ping any of us if you need some help. Note
that we've set up a doc guidelines to help people
contribute at <a moz-do-not-send="true"
href="http://docs.qgis.org/testing/en/docs/documentation_guidelines/index.html"
target="_blank">http://docs.qgis.org/testing/<wbr>en/docs/documentation_<wbr>guidelines/index.html</a>.
The <a moz-do-not-send="true"
href="http://qgis.org/en/site/getinvolved/document.html"
target="_blank">http://qgis.org/en/site/<wbr>getinvolved/document.html</a>
page might also be of interest. Use it and never
hesitate to ask for clarifications so that we
guide you or send feedbacks so that we improve it.
<br>
<br>
</div>
<div>Regards,<br>
<br>
Harrissou<br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2017-02-20 12:50 GMT+01:00
Janneke van Dijk <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:jvandijk@chanzo.nl"
target="_blank">jvandijk@chanzo.nl</a>></span>:<br>
<blockquote class="gmail_quote">
<div> Dear all,
<div
class="gmail-m_409028092341442216m_-1005408186484475721moz-forward-container">
<p>I'm struggling contacting the community
list directly, so I'm trying directly to
the three of you now (advised by Richard).<br>
</p>
<p>As far as I can tell the Training Manual
is based on 2.0 (<a moz-do-not-send="true"
class="gmail-m_409028092341442216m_-1005408186484475721moz-txt-link-freetext"
href="http://docs.qgis.org/testing/en/docs/training_manual/introduction/preparation.html"
target="_blank">http://docs.qgis.org/testing/<wbr>en/docs/training_manual/introd<wbr>uction/preparation.html</a>).
Are there plans to update it to
2.14/2.18/3? I may be able to contribute
time for this, but I will need some help
getting started. Let me know if I can
contribute.<br>
</p>
<p>Thanks,</p>
<p>Janneke<span
class="gmail-m_409028092341442216HOEnZb"><br>
</span></p>
<span
class="gmail-m_409028092341442216HOEnZb">
<br>
<div
class="gmail-m_409028092341442216m_-1005408186484475721moz-signature">--
<br>
<p>Janneke van Dijk<br>
Geographical Information Systems
specialist<br>
mobile: <a moz-do-not-send="true"
href="tel:+255%20784%20684%20835"
value="+255784684835"
target="_blank">+255 784 684835</a><br>
email: <a moz-do-not-send="true"
class="gmail-m_409028092341442216m_-1005408186484475721moz-txt-link-abbreviated"
href="mailto:jvandijk@chanzo.nl"
target="_blank">jvandijk@chanzo.nl</a><br>
</p>
</div>
</span></div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>