<div dir="ltr"><div>Hi,</div><div><br></div><div>I'm not so sure we want someone who knows about the software, the code and the command line. We want to write a documentation that is understandable by everyone, right? So someone who has little or no idea about this can be also helpful from that perspective.</div><div><br></div><div>They need to know about Git and Github to be able to write and push the documentation.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 9, 2019 at 1:25 PM Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com">cameron.shorter@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF">
    <p>Thanks for the suggestions Jo. I've updated to:</p>
    <p>* It will be helpful if you understand the basics of software
      development, including:<br>
      **  Installing software on Linux, windows and mac, from the
      command line<br>
      ** Using basic git and github functionality to update
      documentation<br>
      ** Writing in wiki, markdown and restructured text formats<br>
      ** Bonus points if you can read code and understand it<br>
    </p>
    <div class="gmail-m_-1455849449029606522moz-cite-prefix">On 9/5/19 9:00 pm, Jo Cook wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="ltr">
        <div dir="ltr">Hi Cameron,
          <div><br>
          </div>
          <div>I think the only area of that list that I think needs
            some work is the section on software development. </div>
          <div><br>
          </div>
          <div>
            <div>* You can install software on linux, windows and mac
              from the command line<br>
            </div>
            <div>Yes, this makes sense- we need to highlight differences
              between installation methods<br>
            </div>
            <div><br>
            </div>
            <div>* You understand basic git commands</div>
            <div>What did you have in mind here- is this for committing
              documentation to github? I think this needs expanding a
              bit- people need to be familiar with using git and github</div>
            <div><br>
            </div>
            <div>* You can read code and understand it</div>
            <div>As it stands, this would put me off as I always think
              of myself as a non-coder. Could we expand it to say
              "understand it enough to follow an instruction through or
              track down where an issue occurs". Otherwise what did you
              have in mind for this point?</div>
            <div><br>
            </div>
            <div>* You are comfortable writing in wiki formats</div>
          </div>
          <div>Wiki, and markdown, restructured text</div>
          <div><br>
          </div>
          <div>All the best</div>
          <div><br>
          </div>
          <div>Jo</div>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Thu, May 9, 2019 at 9:19 AM
          Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div dir="ltr">
            <div dir="ltr">Hi folks,</div>
            <div dir="ltr">I've taken a first cut at what I think we
              should use as guidelines for selecting our paid
              contributors. I'd be interested to hear feedback. Are
              there other things we should be considering?</div>
            <div dir="ltr">--</div>
            <div dir="ltr">
              <div><a href="https://wiki.osgeo.org/wiki/Season_of_Docs_Ideas_2019#Selection_criteria_for_paid_role" target="_blank">https://wiki.osgeo.org/wiki/Season_of_Docs_Ideas_2019#Selection_criteria_for_paid_role</a></div>
              <div><br>
              </div>
              <div>
                <p style="margin:0.5em 0px;line-height:inherit;color:rgb(37,37,37);font-family:sans-serif;font-size:14px">For
                  the paid <a rel="nofollow" class="gmail-m_-1455849449029606522gmail-m_-2472303497591104105external gmail-m_-1455849449029606522gmail-m_-2472303497591104105gmail-text" href="https://developers.google.com/season-of-docs/docs/tech-writer-guide" style="text-decoration-line:none;color:rgb(102,51,102);background-color:initial;padding-right:13px" target="_blank">senior
                    technical writer role</a>, we are looking for
                  someone to help us reach our goals of being impactful,
                  sustainable and effective. In responding, consider:</p>
                <ul style="margin:0.3em 0px 0px 1.6em;padding:0px;color:rgb(37,37,37);font-family:sans-serif;font-size:14px">
                  <li style="margin-bottom:0.1em">How will your
                    contributions be valuable beyond the SeasonOfDocs
                    period, beyond the initiative you take on, beyond
                    the specific project(s) you help?</li>
                  <li style="margin-bottom:0.1em">How will you be
                    helping others become more effective? Look at
                    profiles of volunteers interested so far.</li>
                  <li style="margin-bottom:0.1em">We have technical
                    expertise. We are looking for someone with a breadth
                    and depth of writing experience. You are familiar
                    with various style guides, writing styles,
                    information design, writing tools, etc. You’ll have
                    opinions on which should be used and why and will
                    help shape our communication strategies.</li>
                  <li style="margin-bottom:0.1em">Will you be able to
                    help us find and then become involved in best
                    practice documentation communities? You might
                    already be part of such communities.</li>
                  <li style="margin-bottom:0.1em">You are nice and
                    friendly, in line with our <a rel="nofollow" class="gmail-m_-1455849449029606522gmail-m_-2472303497591104105external gmail-m_-1455849449029606522gmail-m_-2472303497591104105gmail-text" href="https://www.osgeo.org/code_of_conduct/" style="text-decoration-line:none;color:rgb(102,51,102);background-color:initial;padding-right:13px" target="_blank">code-of-conduct</a>.</li>
                  <li style="margin-bottom:0.1em">You know the basics of
                    software development:
                    <ul style="list-style-type:disc;margin:0.3em 0px 0px 1.6em;padding:0px">
                      <li style="margin-bottom:0.1em">You can install
                        software on linux, windows and mac from the
                        command line</li>
                      <li style="margin-bottom:0.1em">You understand
                        basic git commands</li>
                      <li style="margin-bottom:0.1em">You can read code
                        and understand it</li>
                      <li style="margin-bottom:0.1em">You are
                        comfortable writing in wiki formats</li>
                    </ul>
                  </li>
                  <li style="margin-bottom:0.1em">Google offers
                    standard-length (3 months) and long-running (6
                    months) options (for the same stipend funds). The
                    longer timeframe is better suited to working with
                    volunteers and our goal of sustainability.</li>
                  <li style="margin-bottom:0.1em">It will be challenging
                    for us to have the bandwidth to assess whether you
                    are both competent and will sustain your involvement
                    long term. Are you able to reference your volunteer
                    involvement in other communities? How can you
                    concisely reference your communication expertise?</li>
                </ul>
                <p style="margin:0.5em 0px;line-height:inherit;color:rgb(37,37,37);font-family:sans-serif;font-size:14px">Does
                  all this sound exciting, but you suspect you don’t
                  have the bandwidth or expertise for the paid senior
                  technical writer role? Why not join our volunteers?</p>
              </div>
              <div><br clear="all">
                <div><br>
                </div>
                -- <br>
                <div dir="ltr" class="gmail-m_-1455849449029606522gmail-m_-2472303497591104105gmail_signature">
                  <div dir="ltr">
                    <div>
                      <div dir="ltr">
                        <div dir="ltr">
                          <div dir="ltr">
                            <div dir="ltr">
                              <div dir="ltr">
                                <div>
                                  <div><span style="font-size:12.8px">Cameron
                                      Shorter</span><br>
                                  </div>
                                  <div>Technology Demystifier</div>
                                  <div>Open Technologies and Geospatial
                                    Consultant</div>
                                  <div><br>
                                  </div>
                                  <div>M +61 (0) 419 142 254</div>
                                  <div><br>
                                  </div>
                                </div>
                                <div><br>
                                  <br>
                                </div>
                              </div>
                            </div>
                          </div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
          _______________________________________________<br>
          SeasonOfDocs mailing list<br>
          <a href="mailto:SeasonOfDocs@lists.osgeo.org" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
          <a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
        </blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      -- <br>
      <div dir="ltr" class="gmail-m_-1455849449029606522gmail_signature">------------------------<br>
        <a href="http://about.me/jocook" target="_blank">http://about.me/jocook</a></div>
    </blockquote>
    <pre class="gmail-m_-1455849449029606522moz-signature" cols="72">-- 
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant

M +61 (0) 419 142 254</pre>
  </div>

_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote></div>