<div dir="ltr">Hi all, <div><br></div><div>Wondering if there is any action on this front. Any questions from the board re: the committee, or any issues we should address before the committee is formed?</div><div><br></div><div>Looking forward to more discussion, and getting this work formally started.</div><div><br></div><div>cheers -</div><div>-kristin</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 9, 2015 at 2:53 PM, Cameron Shorter <span dir="ltr"><<a href="mailto:cameron.shorter@gmail.com" target="_blank">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 bgcolor="#FFFFFF" text="#000000">
    Hi David,<br>
    You point re keeping the committee tight is valid.<br>
    So I'll extend my suggestion to explain the reason for a relatively
    small number of voting members . This would typically be in the
    range of X and Y.<br>
    <br>
    This gives some flexibility to add a valuable voice to the voting
    committee as required. (Note: I'm still suggesting the committee is
    responsible for voting in new committee members, and as such are
    able to protect the committee from being hijacked).<br>
    <br>
    Cheers, Cameron<div><div class="h5"><br>
    <br>
    <div>On 10/07/2015 7:45 am, David William
      Bitner wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">Adding Camille's updated email address to the CC as
        I'm not sure if she's on the board list...</div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Jul 9, 2015 at 4:43 PM, David
          William Bitner <span dir="ltr"><<a href="mailto:bitner@dbspatial.com" target="_blank">bitner@dbspatial.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="ltr">Cameron,
              <div><br>
              </div>
              <div>I think this committee is a bit different and there
                are really two parts to what this committee can do.</div>
              <div><br>
              </div>
              <div>1) Discuss and help guide policy around the CoC as
                well as other initiatives that can help increase
                diversity in our community</div>
              <div><br>
              </div>
              <div>2) Respond and enforce to any reports of violations
                to the CoC</div>
              <div><br>
              </div>
              <div>While it is extremely important to have open
                discussion with a group that may grow and contract for
                #1, I think it's important to have an intentional limit
                on the group that is privy to #2 so as to limit the
                scope of people who are dealing with potentially very
                private information. I can see perhaps having more
                voting members, but only if we created some sort of
                executive committee of the committee that was much more
                limited.</div>
              <div><br>
              </div>
              <div>David</div>
            </div>
            <div class="gmail_extra">
              <div>
                <div><br>
                  <div class="gmail_quote">On Thu, Jul 9, 2015 at 4:37
                    PM, Cameron Shorter <span dir="ltr"><<a href="mailto:cameron.shorter@gmail.com" target="_blank">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">Hi
                      Camille and Kristin,<br>
                      It is great to see you both initiate a CoC
                      committee, and I'm delighted to see you both
                      involved in it.<br>
                      I'm +1 for your proposal (although I'm not on the
                      board any more).<br>
                      <br>
                      I have a minor suggestion re membership, based on
                      conventions from other OSGeo committees.<br>
                      <br>
                      Committees have volunteers come and go, sometimes
                      with many people volunteering to be members,
                      sometimes with few.<br>
                      <br>
                      I'd encourage you to have no fixed limit on the
                      number of members that you have at any one time.
                      Rather existing members can vote in a new member
                      at any time, and people can retire at any time
                      (and be thanked for their service).<br>
                      <br>
                      As I expect this committee might receive some
                      strong opinions from people who jump in, say their
                      point, then leave, you might want to expect people
                      have provided valuable contributions for a period
                      of time before they become a voting member. (Maybe
                      ~ 3 months as a guide, but that a timeframe need
                      not be a criteria).<br>
                      <br>
                      As such, you might want to make it clear that all
                      are welcome to contribute to public email
                      discussions, but votes are only counted from
                      committee members.<br>
                      <br>
                      Thanks and warm regards,<br>
                      Cameron
                      <div>
                        <div><br>
                          <br>
                          On 10/07/2015 1:59 am, Jeff McKenna wrote:<br>
                          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                            <br>
                            Hey Everyone,<br>
                            <br>
                            <br>
                            As many of you know, a number of us met for
                            a BoF session during State<br>
                            of the Map (NYC, early June) to discuss next
                            steps/implementation for<br>
                            the Code of Conduct (CoC) that was recently
                            adopted by the OSGeo Board.<br>
                            <br>
                            <br>
                            By adopting the CoC, the OSGeo Board has
                            taken a step in the right<br>
                            direction, but a policy without an
                            implementation plan is insufficient.<br>
                            In order to make the CoC actionable, OSGeo
                            needs to have process in<br>
                            place to deal with any CoC issues occurring
                            in OSGeo forums, projects,<br>
                            or in person at OSGeo gatherings.<br>
                            <br>
                            <br>
                            We propose the creation of a standing Code
                            of Conduct committee. This<br>
                            committee will be tasked not only with
                            designing and implementing a<br>
                            process for incident reporting and follow-up
                            but also supporting<br>
                            knowledge transfer between conference/event
                            organizers (e.g. as part of<br>
                            the “passing of the torch” to the next
                            FOSS4G LOC) and supporting best<br>
                            practices for accessibility for events and
                            activities.<br>
                            <br>
                            <br>
                            We ask you to review our proposed committee
                            structure on the OSGeo Wiki<br>
                            (wiki page <<a href="http://wiki.osgeo.org/wiki/CodeOfConduct_Committee" rel="noreferrer" target="_blank">http://wiki.osgeo.org/wiki/CodeOfConduct_Committee</a>>[1])
                            and<br>
                            vote in favor of the establishment of this
                            new committee. We welcome<br>
                            feedback about the best way to structure
                            such a committee, and we would<br>
                            also appreciate guidance on how the
                            committee can best engage the board<br>
                            and the rest of the organization.<br>
                            <br>
                            <br>
                            If the Code of Conduct committee is approved
                            by the board we are willing<br>
                            to serve as co-chairs to get the committee
                            up and running.<br>
                            <br>
                            <br>
                            We look forward to hearing from you and
                            moving forward in this important<br>
                            work.<br>
                            <br>
                            <br>
                            Cheers,<br>
                            <br>
                            Camille Acey<br>
                            <br>
                            Kristin Bott<br>
                            <br>
                            <br>
                            [1] <a href="http://wiki.osgeo.org/wiki/CodeOfConduct_Committee" rel="noreferrer" target="_blank">http://wiki.osgeo.org/wiki/CodeOfConduct_Committee</a><br>
                            <br>
                            <br>
                            <br>
                            <br>
_______________________________________________<br>
                            Board mailing list<br>
                            <a href="mailto:Board@lists.osgeo.org" target="_blank">Board@lists.osgeo.org</a><br>
                            <a href="http://lists.osgeo.org/mailman/listinfo/board" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/board</a><br>
                          </blockquote>
                          <br>
                        </div>
                      </div>
                      <span><font color="#888888">
                          -- <br>
                          Cameron Shorter,<br>
                          Software and Data Solutions Manager<br>
                          LISAsoft<br>
                          Suite 112, Jones Bay Wharf,<br>
                          26 - 32 Pirrama Rd, Pyrmont NSW 2009<br>
                          <br>
                          P <a href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank">+61 2
                            9009 5000</a>,  W <a href="http://www.lisasoft.com" rel="noreferrer" target="_blank">www.lisasoft.com</a>, 
                          F <a href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank">+61 2
                            9009 5099</a></font></span>
                      <div>
                        <div><br>
                          <br>
_______________________________________________<br>
                          Board mailing list<br>
                          <a href="mailto:Board@lists.osgeo.org" target="_blank">Board@lists.osgeo.org</a><br>
                          <a href="http://lists.osgeo.org/mailman/listinfo/board" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/board</a></div>
                      </div>
                    </blockquote>
                  </div>
                  <br>
                  <br clear="all">
                  <div><br>
                  </div>
                </div>
              </div>
              <span><font color="#888888">-- <br>
                  <div>************************************<br>
                    David William Bitner
                    <div>dbSpatial LLC</div>
                    <div><a href="tel:612-424-9932" value="+16124249932" target="_blank">612-424-9932</a></div>
                  </div>
                </font></span></div>
          </blockquote>
        </div>
        <br>
        <br clear="all">
        <div><br>
        </div>
        -- <br>
        <div>************************************<br>
          David William Bitner
          <div>dbSpatial LLC</div>
          <div><a href="tel:612-424-9932" value="+16124249932" target="_blank">612-424-9932</a></div>
        </div>
      </div>
    </blockquote>
    <br>
    <pre cols="72">-- 
Cameron Shorter,
Software and Data Solutions Manager
LISAsoft
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009

P <a href="tel:%2B61%202%209009%205000" value="+61290095000" target="_blank">+61 2 9009 5000</a>,  W <a href="http://www.lisasoft.com" target="_blank">www.lisasoft.com</a>,  F <a href="tel:%2B61%202%209009%205099" value="+61290095099" target="_blank">+61 2 9009 5099</a></pre>
  </div></div></div>

</blockquote></div><br></div>