<p dir="ltr">About the screenshots, if you are able to use a VM with Ubuntu it would be great. If not, just create the screenshots in Windows. If I have time I will replace them by Ubuntu ones.</p>
<p dir="ltr">Yes, discussion about changes came with the PRs. But feel free to ask before starting some longer work.</p>
<p dir="ltr">Alexandre Neto</p>
<br><div class="gmail_quote"><div dir="ltr">A qui, 23/02/2017, 20:24, Janneke van Dijk <<a href="mailto:janneke.qgis@gmail.com">janneke.qgis@gmail.com</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  

    
  
  <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
    <p class="gmail_msg">Next try, it seems the message body too big.<br class="gmail_msg">
    </p>
    <div class="m_-8743146376449904345moz-forward-container gmail_msg"><br class="gmail_msg">
      -------- Forwarded Message --------
      <table class="m_-8743146376449904345moz-email-headers-table gmail_msg" border="0" cellpadding="0" cellspacing="0">
        <tbody class="gmail_msg">
          <tr class="gmail_msg">
            <th align="RIGHT" nowrap valign="BASELINE" class="gmail_msg">Subject:
            </th>
            <td class="gmail_msg">training manual update</td>
          </tr>
          <tr class="gmail_msg">
            <th align="RIGHT" nowrap valign="BASELINE" class="gmail_msg">Date: </th>
            <td class="gmail_msg">Thu, 23 Feb 2017 16:36:09 +0300</td>
          </tr>
          <tr class="gmail_msg">
            <th align="RIGHT" nowrap valign="BASELINE" class="gmail_msg">From: </th>
            <td class="gmail_msg">Janneke van Dijk <a class="m_-8743146376449904345moz-txt-link-rfc2396E gmail_msg" href="mailto:janneke.qgis@gmail.com" target="_blank"><janneke.qgis@gmail.com></a></td>
          </tr>
          <tr class="gmail_msg">
            <th align="RIGHT" nowrap valign="BASELINE" class="gmail_msg">To: </th>
            <td class="gmail_msg"><a class="m_-8743146376449904345moz-txt-link-abbreviated gmail_msg" href="mailto:qgis-community-team@lists.osgeo.org" target="_blank">qgis-community-team@lists.osgeo.org</a></td>
          </tr>
        </tbody>
      </table>
      <br class="gmail_msg">
      <br class="gmail_msg">
      
      <p class="gmail_msg">Dear Harissou, dear list,</p>
      <p class="gmail_msg">Let's see if this now works via the list, indeed better to keep
        it public.</p>
      <p class="gmail_msg">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 class="gmail_msg">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 class="gmail_msg">I'm sure I'll have plenty of questions tomorrow...</p>
      <p class="gmail_msg">Janneke<br class="gmail_msg">
      </p>
      <p class="gmail_msg"><br class="gmail_msg">
      </p>
      <p class="gmail_msg">Hi Janneke,<br class="gmail_msg">
        <br class="gmail_msg">
        <br class="gmail_msg">
      </p>
      <div class="gmail_quote gmail_msg">2017-02-21 17:33 GMT+01:00 Janneke van
        Dijk <span dir="ltr" class="gmail_msg"><<a href="mailto:jvandijk@chanzo.nl" class="gmail_msg" target="_blank">jvandijk@chanzo.nl</a>></span>:<br class="gmail_msg">
        <blockquote class="gmail_quote gmail_msg">
          <div class="gmail_msg">
            <div class="m_-8743146376449904345gmail-m_409028092341442216moz-cite-prefix gmail_msg">Hi
              Harissou,<br class="gmail_msg">
              <br class="gmail_msg">
              Thanks for your extended explanation!<br class="gmail_msg">
              So, I've got a github account, set it up with source tree,
              cloned the repo.<br class="gmail_msg">
              <br class="gmail_msg">
            </div>
          </div>
        </blockquote>
        <div class="gmail_msg">Good. If you have question on github/git, do not hesitate
          either. <br class="gmail_msg">
        </div>
        <blockquote class="gmail_quote gmail_msg">
          <div class="gmail_msg">
            <div class="m_-8743146376449904345gmail-m_409028092341442216moz-cite-prefix gmail_msg"> 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 class="gmail_msg">
              <br class="gmail_msg">
            </div>
          </div>
        </blockquote>
        <div class="gmail_msg">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 class="gmail_msg">
          <br class="gmail_msg">
        </div>
        <div class="gmail_msg">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 class="gmail_msg">
        </div>
        <div class="gmail_msg"><br class="gmail_msg">
        </div>
        <blockquote class="gmail_quote gmail_msg">
          <div class="gmail_msg">
            <div class="m_-8743146376449904345gmail-m_409028092341442216moz-cite-prefix gmail_msg"> 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 class="gmail_msg"> </div>
        <div class="gmail_msg">Yes do it that way, and if you find issues you can't fix
          alone, please report it and we'll try together.<br class="gmail_msg">
        </div>
        <div class="gmail_msg"> </div>
        <blockquote class="gmail_quote gmail_msg">
          <div class="gmail_msg">
            <div class="m_-8743146376449904345gmail-m_409028092341442216moz-cite-prefix gmail_msg"> 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 class="gmail_msg">
              <br class="gmail_msg">
            </div>
          </div>
        </blockquote>
        <blockquote class="gmail_quote gmail_msg">
          <div class="gmail_msg">
            <div class="m_-8743146376449904345gmail-m_409028092341442216moz-cite-prefix gmail_msg"> Of
              course, if it doesn't make sense to get started already
              I'd better wait until further notice.<br class="gmail_msg">
            </div>
          </div>
        </blockquote>
        <div class="gmail_msg"><br class="gmail_msg">
          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 class="gmail_msg">
        </div>
        <div class="gmail_msg">- steps to reach some tools<br class="gmail_msg">
        </div>
        <div class="gmail_msg">- screenshots (some instructions at <a href="http://docs.qgis.org/testing/en/docs/documentation_guidelines/writing.html#managing-screenshots" class="gmail_msg" target="_blank">http://docs.qgis.org/testing/en/docs/documentation_guidelines/writing.html#managing-screenshots</a>)<br class="gmail_msg">
          <br class="gmail_msg">
          <br class="gmail_msg">
          <br class="gmail_msg">
          <br class="gmail_msg">
        </div>
        <div class="gmail_msg">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 class="gmail_msg">
        </div>
        <div class="gmail_msg">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 class="gmail_msg">
        </div>
        <div class="gmail_msg"><br class="gmail_msg">
          <br class="gmail_msg">
        </div>
        <div class="gmail_msg"> If there are any points I didn't address let me know...<br class="gmail_msg">
          Looking forward to writing doc with you,<br class="gmail_msg">
          <br class="gmail_msg">
        </div>
        <div class="gmail_msg">Harrissou<br class="gmail_msg">
        </div>
        <blockquote class="gmail_quote gmail_msg">
          <div class="gmail_msg">
            <div class="m_-8743146376449904345gmail-m_409028092341442216moz-cite-prefix gmail_msg"><br class="gmail_msg">
              thanks for your advice,<br class="gmail_msg">
              Janneke
              <div class="gmail_msg">
                <div class="m_-8743146376449904345gmail-h5 gmail_msg"><br class="gmail_msg">
                  <br class="gmail_msg">
                  <br class="gmail_msg">
                  <br class="gmail_msg">
                  On 20-Feb-17 19:17, DelazJ wrote:<br class="gmail_msg">
                </div>
              </div>
            </div>
            <div class="gmail_msg">
              <div class="m_-8743146376449904345gmail-h5 gmail_msg">
                <blockquote type="cite" class="gmail_msg">
                  <div dir="ltr" class="gmail_msg">
                    <div class="gmail_msg">
                      <div class="gmail_msg">
                        <div class="gmail_msg">Hi Janneke,<br class="gmail_msg">
                          <br class="gmail_msg">
                        </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 class="gmail_msg">
                      </div>
                      <br class="gmail_msg">
                      What are the plans... ?<br class="gmail_msg">
                       * Except for fixes, we no longer work on QGIS
                      2.14 documentation<br class="gmail_msg">
                      <br class="gmail_msg">
                       * For QGIS Documentation, I think that due to
                      some recent news, there will probably be a 2.18
                      (LTR?) doc release.<br class="gmail_msg">
                        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 class="gmail_msg">I set to myself </b>to stop
                      contributing to the 2.x bug fixes). Of course, we
                      can extend that if need be.<br class="gmail_msg">
                      <br class="gmail_msg">
                      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 href="https://lists.osgeo.org/pipermail/qgis-psc/2017-January/005048.html" class="gmail_msg" target="_blank">https://lists.osgeo.org/pipermail/qgis-psc/2017-January/005048.html</a>).
                      Maybe he has a better overview and can help you
                      decide.<br class="gmail_msg">
                      <br class="gmail_msg">
                      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 href="https://github.com/qgis/QGIS-Documentation/issues?q=is%3Aopen+is%3Aissue+label%3A%22Training+Manual%22" class="gmail_msg" target="_blank">https://github.com/qgis/QGIS-Documentation/issues?q=is%3Aopen+is%3Aissue+label%3A%22Training+Manual%22</a>).<br class="gmail_msg">
                    </div>
                    <br class="gmail_msg">
                     * 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 class="gmail_msg">
                    <div class="gmail_msg"><br class="gmail_msg">
                      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 href="http://docs.qgis.org/testing/en/docs/documentation_guidelines/index.html" class="gmail_msg" target="_blank">http://docs.qgis.org/testing/en/docs/documentation_guidelines/index.html</a>.
                      The <a href="http://qgis.org/en/site/getinvolved/document.html" class="gmail_msg" target="_blank">http://qgis.org/en/site/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 class="gmail_msg">
                      <br class="gmail_msg">
                    </div>
                    <div class="gmail_msg">Regards,<br class="gmail_msg">
                      <br class="gmail_msg">
                      Harrissou<br class="gmail_msg">
                    </div>
                    <div class="gmail_msg"><br class="gmail_msg">
                    </div>
                  </div>
                  <div class="gmail_extra gmail_msg"><br class="gmail_msg">
                    <div class="gmail_quote gmail_msg">2017-02-20 12:50 GMT+01:00
                      Janneke van Dijk <span dir="ltr" class="gmail_msg"><<a href="mailto:jvandijk@chanzo.nl" class="gmail_msg" target="_blank">jvandijk@chanzo.nl</a>></span>:<br class="gmail_msg">
                      <blockquote class="gmail_quote gmail_msg">
                        <div class="gmail_msg"> Dear all,
                          <div class="m_-8743146376449904345gmail-m_409028092341442216m_-1005408186484475721moz-forward-container gmail_msg">
                            <p class="gmail_msg">I'm struggling contacting the community
                              list directly, so I'm trying directly to
                              the three of you now (advised by Richard).<br class="gmail_msg">
                            </p>
                            <p class="gmail_msg">As far as I can tell the Training Manual
                              is based on 2.0 (<a class="m_-8743146376449904345gmail-m_409028092341442216m_-1005408186484475721moz-txt-link-freetext gmail_msg" href="http://docs.qgis.org/testing/en/docs/training_manual/introduction/preparation.html" target="_blank">http://docs.qgis.org/testing/en/docs/training_manual/introduction/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 class="gmail_msg">
                            </p>
                            <p class="gmail_msg">Thanks,</p>
                            <p class="gmail_msg">Janneke<span class="m_-8743146376449904345gmail-m_409028092341442216HOEnZb gmail_msg"><br class="gmail_msg">
                              </span></p>
                            <span class="m_-8743146376449904345gmail-m_409028092341442216HOEnZb gmail_msg">
                              <br class="gmail_msg">
                              <div class="m_-8743146376449904345gmail-m_409028092341442216m_-1005408186484475721moz-signature gmail_msg">--
                                <br class="gmail_msg">
                                <p class="gmail_msg">Janneke van Dijk<br class="gmail_msg">
                                  Geographical Information Systems
                                  specialist<br class="gmail_msg">
                                  mobile: <a href="tel:+255%20784%20684%20835" value="+255784684835" class="gmail_msg" target="_blank">+255 784 684835</a><br class="gmail_msg">
                                  email: <a class="m_-8743146376449904345gmail-m_409028092341442216m_-1005408186484475721moz-txt-link-abbreviated gmail_msg" href="mailto:jvandijk@chanzo.nl" target="_blank">jvandijk@chanzo.nl</a><br class="gmail_msg">
                                </p>
                              </div>
                            </span></div>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </blockquote></div></div></div></blockquote></div></div></div></blockquote></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature"><div dir="ltr"><div>Alexandre Neto</div><div>---------------------</div><div>@AlexNetoGeo</div><div><a href="http://sigsemgrilhetas.wordpress.com">http://sigsemgrilhetas.wordpress.com</a></div><a href="http://gisunchained.wordpress.com">http://gisunchained.wordpress.com</a><br></div></div>