<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Thanks Jody,</p>
    <p>I think you have some good practical ideas here, which should be
      fairly easy to gain consensus around.</p>
    <p>I'd suggest the next step would be draw up ideas into a draft
      (probably using existing wiki as a basis) which we can comment on
      and then vote on.</p>
    <p>This is not time critical, so could wait until after marketing
      initiatives are less time consuming. <br>
    </p>
    <p>Cheers, Cameron<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 13/9/17 2:56 am, Jody Garnett wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAOhbgAmvmfAnGog=aXu7FwGXLGfX48YbfN9+=r1jadHU3Cq=LA@mail.gmail.com">
      <div dir="ltr">Morning Cameron good to hear from you.
        <div><br>
        </div>
        <div>In a couple email threads, and the most recent board
          meeting, we are getting input on what makes a good community
          project (and what kind of projects we wish to promote as open
          source spatial).</div>
        <div><br>
        </div>
        <div>I love the idea of aligning the very short community
          project checklist and the incubation checklist. In particular
          we hit on a great way to communicate our incubation ideals
          during the marketing/rebranding by emphasizing open,
          geospatial and fair.</div>
        <div><br>
        </div>
        <div>1) CONTIRBUTING.md and LICENSE.md are best practices from
          github allowing projects to be searched effectively, and the
          appropriate instructions shown to those making pull requests
          (not as effective as a CLA but something).</div>
        <div><br>
        </div>
        <div>2) Check the headers - I am hoping for something lighter
          weight then the provenance review (which requires checking
          history). Several projects have done multi-file searches (we
          can provide a grep example) to detect files without a header.
          This subject has been complicated by our recent osgeo legal
          advice that headers are not required as many of have been
          taught (but that LICENSE file is).</div>
        <div><br>
        </div>
        <div>This provides three easy checks, all of which introduce our
          priorities as a software foundation:</div>
        <div><br>
        </div>
        <div>- fair: Check for a <a href="http://contirbuting.md"
            moz-do-not-send="true">contirbuting.md</a> file (required
          for github, but need should be met somehow for other
          platforms)</div>
        <div>- open: The quick check is looking for a LICENSE.md
          (github) or LICENSE.txt file and confirming it is on the OSI
          approved list. I hope a grep can identify any files with out
          headers and a void a time sync.</div>
        <div>- geospatial: This is the tricky one to confirm - any
          suggestions?</div>
        <div><br>
        </div>
        <div>Implicit in this is a tension between being flexible (many
          projects can show they are open to contributions by citing
          their developers guide rather than including a CONTRIBUTING
          file) and prescriptive (tell projects exactly what to do). I
          would personally err on communication; we are doing open
          source advocacy here so it is more important that projects
          *are* participatory than that they have exactly the right
          files.</div>
        <div><br>
        </div>
        <div>There are a few more requirements from the discuss list
          focusing on borderline cases between open source and free
          software. I would like us to take care to be kind to each
          other discussing this balance and not lose sight of our strong
          core of geospatial/open/fair.</div>
        <div>
          <div class="gmail_extra">
            <div>
              <div class="gmail_signature"
                data-smartmail="gmail_signature">
                <div dir="ltr">
                  <div>
                    <div dir="ltr">
                      <div>--</div>
                      <div>Jody Garnett</div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
            <br>
            <div class="gmail_quote">On 12 September 2017 at 02:32,
              Cameron Shorter <span dir="ltr"><<a
                  href="mailto:cameron.shorter@gmail.com"
                  target="_blank" moz-do-not-send="true">cameron.shorter@gmail.com</a>></span>
              wrote:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div text="#000000" bgcolor="#FFFFFF">
                  <p><span
style="color:rgb(0,0,0);font-family:-webkit-standard;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline!important;float:none">Hi
                      incubation committee,</span></p>
                  <p><span
style="color:rgb(0,0,0);font-family:-webkit-standard;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline!important;float:none">One
                      thing the OSGeo-Live community have picked up is
                      that OSGeo Community projects are being asked for
                      CONTRIBUTING.md and LICENSE.md files [1], however
                      there isn't an obvious corresponding requirement
                      for this in the OSGeo Incubation Graduation
                      Checklist [2].</span></p>
                  <p><span
style="color:rgb(0,0,0);font-family:-webkit-standard;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline!important;float:none">I'd
                      suggest that the Graduation Checklist probably
                      needs updating.</span></p>
                  <p><span
style="color:rgb(0,0,0);font-family:-webkit-standard;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline!important;float:none">I
                      also notice the requirement for Community projects
                      to check headers for Open Source compliance,
                      although there isn't  specific guidance on how
                      such checks should be applied. It sounds very
                      similar to a "Provenance Review". Our experience
                      with OSGeo incubation is that the "Provenance
                      Review" is usually the biggest time sink and
                      stumbling block for projects going through
                      incubation. I'd be interested to hear Jody's
                      thoughts on this.</span></p>
                  <p><span
style="color:rgb(0,0,0);font-family:-webkit-standard;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline!important;float:none">Warm
                      regards, Cameron<br>
                    </span></p>
                  <p><span
style="color:rgb(0,0,0);font-family:-webkit-standard;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline!important;float:none">[1]
                      <a
                        class="m_-1079179738151442342moz-txt-link-freetext"
href="https://wiki.osgeo.org/wiki/OSGeo_Community_Projects"
                        target="_blank" moz-do-not-send="true">https://wiki.osgeo.org/wiki/<wbr>OSGeo_Community_Projects</a></span></p>
                  <p><span
style="color:rgb(0,0,0);font-family:-webkit-standard;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline!important;float:none">[2]
                      <a
                        class="m_-1079179738151442342moz-txt-link-freetext"
href="http://www.osgeo.org/incubator/process/project_graduation_checklist.html"
                        target="_blank" moz-do-not-send="true">http://www.osgeo.org/<wbr>incubator/process/project_<wbr>graduation_checklist.html</a><span
                        class="HOEnZb"><font color="#888888"><br>
                        </font></span></span></p>
                  <span class="HOEnZb"><font color="#888888">
                      <p><span
style="color:rgb(0,0,0);font-family:-webkit-standard;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline!important;float:none"><br>
                        </span></p>
                      <pre class="m_-1079179738151442342moz-signature" cols="72">-- 
Cameron Shorter
Open Technologies Consultant
Geospatial & Software Architect
Open Source Developer

M <a href="tel:+61%20419%20142%20254" value="+61419142254" target="_blank" moz-do-not-send="true">+61 (0) 419 142 254</a>
<a class="m_-1079179738151442342moz-txt-link-freetext" href="http://shorter.net" target="_blank" moz-do-not-send="true">http://shorter.net</a></pre>
                    </font></span></div>
                <br>
                ______________________________<wbr>_________________<br>
                Incubator mailing list<br>
                <a href="mailto:Incubator@lists.osgeo.org"
                  moz-do-not-send="true">Incubator@lists.osgeo.org</a><br>
                <a
                  href="https://lists.osgeo.org/mailman/listinfo/incubator"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://lists.osgeo.org/<wbr>mailman/listinfo/incubator</a><br>
              </blockquote>
            </div>
            <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Cameron Shorter
Open Technologies Consultant
Geospatial & Software Architect
Open Source Developer

M +61 (0) 419 142 254
<a class="moz-txt-link-freetext" href="http://shorter.net">http://shorter.net</a></pre>
  </body>
</html>