[Board] Fwd: OSGeo CoC committee proposal
Jeff McKenna
jmckenna at gatewaygeomatics.com
Fri Jul 24 04:58:43 PDT 2015
Hi Kristin, Camille,
The Board met face-to-face after FOSS4G-Como, for about an hour
(actually almost 2 hours), and one of the main topics was this
committee. (about 7 of the Board members attended the meeting, I will
share the minutes of the meeting in another message).
It was discussed thoroughly, and as a Board we came up with the
following feedback (luckily I tried to record notes as the discussion
was happening) :
****
- Board appreciates proposed CoC committee
- 2 points must be clarified:
1) changes needed to structure:
- there should be no limitation on # of members (as other
committees)
- need to name chair of committee
- should propose/vote in new members
2) changes needed to scope:
- committee reports about CoC incidents to privately
(board-priv mailing list)
- actions are only taken by the OSGeo Board
****
My own opinion, is that I really appreciate having you both step up to
volunteer tackling this, and, as I tried to explain to the Board, this
is a very important issue. The reality is that having a committee help
make sure that community members are always respected and that OSGeo
always encourages diversity, helps everyone grow. And to be honest, in
this busy world today, having leaders such as yourselves and Kate and
others willing to dedicate your time to helping, means a lot to me and I
would never, ever shut a door on that passion.
I hope that OSGeo Board members now speak up with their own opinions,
direct to Kristen and Camille here, so we can work through this all
together.
-jeff
http://wiki.osgeo.org/wiki/CodeOfConduct_Committee
On 2015-07-23 8:04 PM, Kristin Bott wrote:
> Hi all,
>
> 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?
>
> Looking forward to more discussion, and getting this work formally started.
>
> cheers -
> -kristin
>
> On Thu, Jul 9, 2015 at 2:53 PM, Cameron Shorter
> <cameron.shorter at gmail.com <mailto:cameron.shorter at gmail.com>> wrote:
>
> Hi David,
> You point re keeping the committee tight is valid.
> 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.
>
> 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).
>
> Cheers, Cameron
>
>
> On 10/07/2015 7:45 am, David William Bitner wrote:
>> Adding Camille's updated email address to the CC as I'm not sure
>> if she's on the board list...
>>
>> On Thu, Jul 9, 2015 at 4:43 PM, David William Bitner
>> <bitner at dbspatial.com <mailto:bitner at dbspatial.com>> wrote:
>>
>> Cameron,
>>
>> I think this committee is a bit different and there are really
>> two parts to what this committee can do.
>>
>> 1) Discuss and help guide policy around the CoC as well as
>> other initiatives that can help increase diversity in our
>> community
>>
>> 2) Respond and enforce to any reports of violations to the CoC
>>
>> 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.
>>
>> David
>>
>> On Thu, Jul 9, 2015 at 4:37 PM, Cameron Shorter
>> <cameron.shorter at gmail.com <mailto:cameron.shorter at gmail.com>>
>> wrote:
>>
>> Hi Camille and Kristin,
>> It is great to see you both initiate a CoC committee, and
>> I'm delighted to see you both involved in it.
>> I'm +1 for your proposal (although I'm not on the board
>> any more).
>>
>> I have a minor suggestion re membership, based on
>> conventions from other OSGeo committees.
>>
>> Committees have volunteers come and go, sometimes with
>> many people volunteering to be members, sometimes with few.
>>
>> 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).
>>
>> 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).
>>
>> 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.
>>
>> Thanks and warm regards,
>> Cameron
>>
>>
>> On 10/07/2015 1:59 am, Jeff McKenna wrote:
>>
>>
>> Hey Everyone,
>>
>>
>> As many of you know, a number of us met for a BoF
>> session during State
>> of the Map (NYC, early June) to discuss next
>> steps/implementation for
>> the Code of Conduct (CoC) that was recently adopted by
>> the OSGeo Board.
>>
>>
>> By adopting the CoC, the OSGeo Board has taken a step
>> in the right
>> direction, but a policy without an implementation plan
>> is insufficient.
>> In order to make the CoC actionable, OSGeo needs to
>> have process in
>> place to deal with any CoC issues occurring in OSGeo
>> forums, projects,
>> or in person at OSGeo gatherings.
>>
>>
>> We propose the creation of a standing Code of Conduct
>> committee. This
>> committee will be tasked not only with designing and
>> implementing a
>> process for incident reporting and follow-up but also
>> supporting
>> knowledge transfer between conference/event organizers
>> (e.g. as part of
>> the “passing of the torch” to the next FOSS4G LOC) and
>> supporting best
>> practices for accessibility for events and activities.
>>
>>
>> We ask you to review our proposed committee structure
>> on the OSGeo Wiki
>> (wiki page
>> <http://wiki.osgeo.org/wiki/CodeOfConduct_Committee>[1])
>> and
>> vote in favor of the establishment of this new
>> committee. We welcome
>> feedback about the best way to structure such a
>> committee, and we would
>> also appreciate guidance on how the committee can best
>> engage the board
>> and the rest of the organization.
>>
>>
>> If the Code of Conduct committee is approved by the
>> board we are willing
>> to serve as co-chairs to get the committee up and running.
>>
>>
>> We look forward to hearing from you and moving forward
>> in this important
>> work.
>>
>>
>> Cheers,
>>
>> Camille Acey
>>
>> Kristin Bott
>>
>>
>> [1] http://wiki.osgeo.org/wiki/CodeOfConduct_Committee
>>
>>
>>
>>
>> _______________________________________________
>> Board mailing list
>> Board at lists.osgeo.org <mailto:Board at lists.osgeo.org>
>> http://lists.osgeo.org/mailman/listinfo/board
>>
>>
>> --
>> Cameron Shorter,
>> Software and Data Solutions Manager
>> LISAsoft
>> Suite 112, Jones Bay Wharf,
>> 26 - 32 Pirrama Rd, Pyrmont NSW 2009
>>
>> P +61 2 9009 5000 <tel:%2B61%202%209009%205000>, W
>> www.lisasoft.com <http://www.lisasoft.com>, F +61 2 9009
>> 5099 <tel:%2B61%202%209009%205099>
>>
>>
>> _______________________________________________
>> Board mailing list
>> Board at lists.osgeo.org <mailto:Board at lists.osgeo.org>
>> http://lists.osgeo.org/mailman/listinfo/board
>>
>>
>>
>>
>> --
>> ************************************
>> David William Bitner
>> dbSpatial LLC
>> 612-424-9932 <tel:612-424-9932>
>>
>>
>>
>>
>> --
>> ************************************
>> David William Bitner
>> dbSpatial LLC
>> 612-424-9932 <tel:612-424-9932>
>
> --
> Cameron Shorter,
> Software and Data Solutions Manager
> LISAsoft
> Suite 112, Jones Bay Wharf,
> 26 - 32 Pirrama Rd, Pyrmont NSW 2009
>
> P+61 2 9009 5000 <tel:%2B61%202%209009%205000>, Wwww.lisasoft.com <http://www.lisasoft.com>, F+61 2 9009 5099 <tel:%2B61%202%209009%205099>
>
>
>
More information about the Board
mailing list