Add code of conduct

[sampl]

For slack group at least

Example via Steve Coffman: https://github.com/gobridge/about-us/blob/master/coc.md

Thoughts, comments?

[jshwlkr]

That seems pretty good. Are we thinking about having a support email and admin help channel? Just because of the nature of our community I might be hesitant to wholesale adopt these particular reporting and spam guidelines, but on a quick interpretation they seem fine. (Any opinions on that in particular?)

[sampl]

I’m inclined to just start with contact info and hold off on a full policy none of us really understands well, but maybe that’s naive and we should take time to structure things more. Open to opinions.

…

On Thu, Aug 22, 2019 at 7:49 AM Joshua Walker ***@***.***> wrote: That seems pretty good. Are we thinking about having a support email and admin help channel? Just because of the nature of our community I might be hesitant to wholesale adopt these particular reporting and spam guidelines, but on a quick interpretation they seem fine. (Any opinions on that in particular?) — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#111?email_source=notifications&email_token=AABYTK72ZNKS37WTWAAG55TQF2RQDA5CNFSM4IN2YUB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD45K3HQ#issuecomment-523939230>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABYTK7YXRNG3Y6BB2MRXCDQF2RQDANCNFSM4IN2YUBQ> .

[andrewsardone]

Sorry for the delay; just chiming into this thread.

I’m inclined to just start with contact info and hold off on a full policy none of us really understands well

That's my inclination, too, @sampl. The Slack community could use a clear documented channel of communication to raise issues & concerns with admins/moderators. Beyond that, a CoC should be deliberate and chosen carefully based on community needs. Perhaps that's an area @rondabergman or @theelfherself of tech[inclusive] might have advice and recommendations.

Proposed Next Steps

As I see them…

1. Determine moderators. Start with Slack admins?
2. Document in the #general channel the members who should be contacted if anyone has concerns. Note that this is a trusted group with an interest in maintaining a healthy community. Set up this notes as a recurring message in #general.
3. Leave this issue open as the running thread to document a broader CoC.

[sampl]

+1, any objections speak now or I'll get the ball rolling soon :)

…

On Sat, Aug 24, 2019 at 9:51 AM Andrew Sardone ***@***.***> wrote: Sorry for the delay; just chiming into this thread. I’m inclined to just start with contact info and hold off on a full policy none of us really understands well That's my inclination, too, @sampl <https://github.com/sampl>. The Slack community could use a clear documented channel of communication to raise issues & concerns with admins/moderators. Beyond that, a CoC should be deliberate and chosen carefully based on community needs. Perhaps that's an area @rondabergman <https://github.com/rondabergman> or @theelfherself <https://github.com/theelfherself> of tech[inclusive] <https://www.meetup.com/tech-inclusive/> might have advice and recommendations. Proposed Next Steps As I see them… 1. Determine moderators. Start with Slack admins? 2. Document in the #general channel the members who should be contacted if anyone has concerns. Note that this is a trusted group with an interest in maintaining a healthy community. Set up this notes as a recurring message in #general <https://www.quora.com/How-do-I-setup-a-recurring-message-in-Slack-either-from-me-or-from-Slackbot> . 3. Leave this issue open as the running thread to document a broader CoC. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#111?email_source=notifications&email_token=AABYTK3O5BNTDEMGLQNFXZDQGE4F3A5CNFSM4IN2YUB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5CANNA#issuecomment-524551860>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABYTKYNAGL4E25XZGRDNLTQGE4F3ANCNFSM4IN2YUBQ> .