Let's have a code of conduct. One of our charity recipients, The Ada Initiative, has a good primer on why it's good for a conference to have a code of conduct. To keep it simple, I suggest we adopt the draft DrupalCon Code of Conduct.
Done:
- Agree on a code of conduct and escalation procedure
Steps to complete
- Send a list of phone numbers to greg.knaddison gmail
- Agree on proposed text that will be read to people if none of the people pick up their phone (see below)
- Configure twilio per items #1 and #2
Proposed fallback text:
"Hello, you've reached the DrupalCamp Colorado Code of Conduct phone number but nobody was available to answer your call right now. You can hang up and try calling again, you can send an email to dcco@dogstar.org or you can stay on the line to leave a voicemail which will get emailed to that address."
Suggested code of conduct:
DrupalCamp Colorado Code of Conduct (DCCoCoC!)
DrupalCamp Colorado brings together people from around the world who use, develop, design, and support the Drupal platform. Many attendees at DrupalCamp Colorado are newcomers evaluating both our platform and our community.
The Drupal Code of Conduct (http://drupal.org/dcoc) outlines our shared ideals and values. This document expresses how we hope to make these ideals real at our events. Our goal is to ensure that all participants can freely and openly share ideas in a friendly, safe, and welcoming environment that encourages and inspires mutual respect and collaboration.
Come for the software, stay for the community.
Drupal would simply not exist without its community. We want all attendees at DrupalCamp Colorado to have an awesome experience, both in and out of formal conference sessions.
The purpose of this document is not to restrict the diversity of ideas and expression in the Drupal community; rather, it's to raise awareness of the potential for actions that could alienate valuable members — and potential members — of the community.
Be considerate.
DrupalCamp Colorado is an international event that attracts diverse people from a wide variety of ethnic, cultural, and religious backgrounds. We acknowledge that cross-cultural communication can often be complicated and encourage everyone to consider both the impact of their actions on those with different backgrounds and experiences and the honest intentions of those who may have unknowingly caused offense.
Be welcoming.
One of the greatest strengths of the Drupal community is our inclusiveness. Making all attendees feel welcome and included at DrupalCamp Colorado is everyone’s job, including exhibitors and sponsors. If you are sponsoring DrupalCamp Colorado and have questions or concerns about working with our community, please reach out to Sponsor Coordinator Jon Clark.
Be respectful.
Sponsors, volunteers, speakers, attendees, and other participants should strive to treat all people with dignity and respect, regardless of their culture, religion, physical appearance, disability, race, ethnicity, gender, or sexual orientation.
Be collaborative.
If and when misunderstandings occur, we encourage people to work things out between themselves whenever possible. People are encouraged to take responsibility for their words and actions and listen to constructively-presented criticism with an open mind, courtesy, and respect.
When we disagree, we consult others.
If people are unable to work out issues between themselves, they are encouraged to seek the advice of a mutually trusted third party or designated community volunteer Trent Hein to help mediate.
When we need it, we ask for help.
We do not tolerate harassment of conference participants in any form. If you feel threatened or violated as a result of intimidating, harassing, abusive, discriminatory, derogatory or demeaning conduct, please immediately notify a conference staff member. Likewise, please immediately notify a volunteer if you notice that someone else is being subjected to such behavior.
If the matter is especially urgent, please call/contact any of these individuals:
Trent Hein
Matthew Saunders
Kevin Bridges
The DrupalCamp Colorado team wants everyone to feel safe for the duration of the conference. If necessary, camp volunteers are empowered to take appropriate actions that may include, but are not limited to, warnings, expulsion from the camp without refund, and referrals to venue security or local law enforcement.
We’re all in this together
Thanks for making DrupalCamp Colorado awesome for everyone!
The DrupalCamp Colorado Code of Conduct is adapted from the draft DrupalCon Code of Conduct, licensed under a Creative Commons Attribution 3.0 Unported License (http://creativecommons.org/licenses/by-sa/3.0/) and is available for others to use and adapt for their own events.
Comments
Comment #1
gregglesYes, please. +1 to the Drupalcon Code of Conduct as long as we actually have a contact form and group of people who will respond to it.
Comment #2
sreynen commentedYeah, we'd need to fill in the [Drupal Association employee name here] placeholders with Drupal Colorado people who are willing and able to handle incidents. I'm not the best person to do that, having no prior experience, but I also try to avoid suggesting work for others I'm not willing to do myself, so I'm willing to handle incidents if we can't find a more capable volunteer.
Comment #3
trhein commentedThis is within my skillset. I would be happy to respond to incidents and/or be part of a group that responds to incidents.
Comment #4
matthews commented+1 (I can help as well - I'm the COC Board Liason for Austin) - but having trhein as point would be great.
Comment #5
sreynen commentedSounds like we're RTBC on the idea of having a code and just need to work out the exact language now. I updated the issue description with a draft code, with minimal modifications to the DrupalCon code to reference our camp and our volunteers rather than those of DrupalCamp. We need to add some way to conduct incident resolution volunteers. I'm not sure how that should work. I wouldn't want to put my own phone number on the site, but it seems important to be able to quickly contact a volunteer if we actually do have an incident. Maybe we should have just emails on the site and make phone numbers available only to 5-10 volunteers, who could then share them with attendees on an as-needed basis?
Comment #6
matthews commentedWe could set up a google voice account for this purpose and forward it to personal mobiles.
Comment #7
matthews commentedAnybody else have thoughts on the google voice idea?
Comment #8
greggmarshallI think this is a great solution to hiding individual phone numbers and allowing the calls to be directed to whomever is on duty to respond to those calls.
Comment #9
gregglesOne problem with google voice is that if people have it setup with their phone already they can't add a new number (and you can't set it up to forward to another google voice number.
Twilio is pretty cost effective (I'd guess less than ~$20 for the weekend) and in spite of being API-based there are solutions that allow forwarding via manual configuration or a simple twiml file can be setup to forward to multiple people for the weekend.
Comment #10
matthews commentedGreggles - would you be willing to lead the charge on Twilio?
Comment #11
gregglesIf that' solution is selected I'm happy to do it.
Comment #12
matthews commentedgreggles - you are on for this. I'm assigning to you.
Comment #13
matthews commentedComment #14
gregglesOkeydoke. Can someone make me a list of numbers it should forward to? There can be up to 5.
Also, there can be a backup message that is read to the person in case the call is not answered. Here's some proposed text.
"Hello, you've reached the DrupalCamp Colorado Code of Conduct phone number but nobody was available to answer your call. Please consider sending an email to XXX or try calling again soon."
Comment #15
gregglesUpdating status to reflect comment #14.
Updating the original issue post to reflect the remaining todos: sending me your phone numbers and agreeing on the proposed fallback text.
One other thing that can potentially be reviewed is the technical implementation. I just plan to pay for a twilio phone number for the weekend and admin it myself to keep it simple. I plan to use the simulring twimlet. I'm happy to have someone else (e.g. someone who is accepting these calls) set up the account, give me the credentials to set it up, and then change them so that privacy of callers is more protected.
Comment #16
matthews commentedgreggles - you can put my phone on it. I just SMSed it.
+1 on the text. I'll create an email account
I have created dcco@dogstar.org which can be useded at the email addy.
Comment #17
cyberswat commentedComment #18
cyberswat commentedThe tentative draft of the CoC has been moved over to the staging site as node/2
Comment #19
gregglesj_matthew_s I think you sms'd it to some number I no longer have. Current number is 720-310-KNAD :)
Comment #20
cyberswat commentedhttp://stage.2014.drupalcampcolorado.org/content/drupalcamp-colorado-cod... is on the staging site, but not prominently linked from anywhere. We are extremely close to launching the site and I feel like this is an important piece of content that should have higher visibility. To that end, I've added a menu item into the header.
Could use some help setting the rest of this up ... Our number will be (303) 731-4049. I'm emailing @greggles the account access information.
Comment #21
cyberswat commentedI set up the account and invited greggles to it via a gmail address I have for him.
Comment #22
gregglesCan we get agreement on the fallback text? That's the last blocker to me working on this.
Comment #23
cyberswat commentedI'm not 100% clear on how this works. I assume that the fallback text is given to the user when the three numbers have not answered. I'm also assuming that the person making the call will have left a message at some point. Assumptions are seldom correct, but I'll go with that for now.
Maybe something like:
"Your concerns are important and your request has taken top priority. We have three mediators available at this camp: Trent Hein (email), Matthew Saunders (email) or Kevin Bridges (email). A mediator will be getting in touch with you as soon as possible. If further, immediate escalation is desired, do not hesitate to contact an event volunteer that will assist with connecting you to a mediator. If you feel that you are in danger, do not hesitate to call 911 and request emergency services."
Comment #24
cyberswat commentedThis line of thought highlights a couple of items. It seems reasonable that we are going to want volunteers to be easily recognizable so that they can be approached. Volunteer t-shirts feel like the easiest way to accomplish this. It also highlights that we will need to make sure that all volunteers are briefed on how to respond if they are approached. I assume (there's that word again), that there was a similar strategy in place for Drupalcon Austin and that @MatthewS can speak to it.
Comment #25
gregglesI wasn't going to do a voicemail, just the simulring twimlet which forwards and then reads a message and stops. BUT...looks like I can also easily use a failURL to forward to a voicemail twiml.
So, we'll need to update the fallback text for that voicemail option. I'm proposing a change now.
Comment #26
gregglesThanks to Kevin in irc and matthew on the phone for help testing. This now seems to be working for at least the inbound call being sent to multiple messages part.
I set up the voicemail as a "fallback url" on the main number. Using that may require matthew and trent to NOT have voicemail on their phone numbers (kevin already has that set). We can also play with timing the phone call and setting the timeout time to 1 second less than the time it takes for the number to go to voicemail, but that requires using a hosted file instead of a twimlet - I can configure that in the twiml and would like to host that file in an obscured location on the camp website.
Comment #27
matthews commentedIs there anything else that needs to happen here or can we close this ticket?
Comment #28
gregglesI'd like to test this just a smidge more at some point. I think Saturday morning of the camp could be a good time to do that.
Comment #29
matthews commentedclosing