[HOT] Draft - HOT Resolution Process

[Heather Leson]

Dear Hotties,


Building a healthy, productive community is exciting. Our work is
internationally recognized. Last year we wrote the membership code of
conduct. As we grow, we aim to improve our common understandings with each
other. To help with this, the Board and Membership Chair have been writing
about how to resolve issues that may arise turning to health and
collaboration as our guiding focus. The very nature of our work is often
tense and fast-paced. We know that sometimes we disagree or misunderstand
each other.

Some of the key messages that we hope all of us can agree upon:

Step Back, Contemplate, Take an email/conversation time out (1 hour, 1 day)

Pausing, Breathing time

Ask clarifying questions, recognize differences in opinion, language, and
culture

Name and identify "escalation" or provocative" statements

Board members are expected to be leaders supporting good conduct

Review cnvc.org Communications basics: an overview of non-violent
communications

"Encourage respect, professionalism, and "fun".

Here are some supporting documents:

HOT Membership Code of Conduct:
http://wiki.openstreetmap.org/w/images/2/2f/HOT_Membership_Code--proposal_for_annual_meeting_2014.pdf

OSM Etiquette Guide: http://wiki.openstreetmap.org/wiki/Etiquette

OSM Community Code of Conduct:
https://wiki.openstreetmap.org/wiki/Community_Code_of_Conduct_(Draft)

In an effort to keep evolving, the Community Working group will be
reviewing this process during our upcoming meeting. We welcome your input
to help us infuse HOT with positive ways to better communicate.

Your input is most welcome:

https://docs.google.com/a/hotosm.org/document/d/1IB1e039JhSQ5xIwi1f6-8wkSDZitKOGUE6GpOUN78QM/edit#


(Special thanks to Gunner from Aspiration for his guidance.)



Thanks,

Russell and Heather

Heather Leson
heatherleson at gmail.com
Twitter: HeatherLeson
Blog: textontechs.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/hot/attachments/20140920/f0c4f9a1/attachment.html>