Skip to content
This repository has been archived by the owner on Mar 27, 2024. It is now read-only.

Code of Conduct #47

Open
amtwo opened this issue Dec 21, 2020 · 5 comments
Open

Code of Conduct #47

amtwo opened this issue Dec 21, 2020 · 5 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@amtwo
Copy link
Contributor

amtwo commented Dec 21, 2020

We need a Code of Conduct (or Codes of Conduct) to support:

  • Contributing to this repo
  • Participants at events (Speakers, sponsors, organizers, etc)
    • Encompassing both in-person & virtual events

GitHub contributing Code of Conduct

This seems pretty straightforward in using the same Code of Conduct as other sqlcollaborative projects.

Event Code of Conduct

In #27 @andrekamman mentions the CodeOfConduct.com code as a base, which helps tackle internationalization/translation.

Events should have a "base" code of conduct (like above), plus a "supplement" which has event-specific details.

Requirements:

  • The event-specific supplement should include who to report violations to, and how/where to contact them.
    • Reporting/assistance should be a direct, unambiguous path from the Code of Conduct. (ie, a monitored email address, a front desk person at an in-person event, etc)
    • Provide guidance to event organizers on eliminating single points of failure for individuals seeking help in reporting problems. Event organizers are often busy & not able to provide a fast initial response
  • The event Code of which is featured prominently & is easy to find. When an attendee is "in crisis" as the victim of harassment, it should not be difficult to find the Code of Conduct (and hence the path to reporting/assistance)

We should additionally provide resources for event organizers so that they feel equipped to provide assistance & response.

@way0utwest
Copy link
Contributor

I agree with the above, and I think a CoC/AHP ought to be one of the few rules we implement.

@github-actions
Copy link

Accessibility Links:
Audio Link:https://gofile.io/d/0GtAZu
Image Link:https://gofile.io/d/vE3OSn

@SQLDBAWithABeard SQLDBAWithABeard added enhancement New feature or request help wanted Extra attention is needed labels Mar 19, 2021
@tameraclark
Copy link

Microsoft is requiring a CoC to be part of the Data Community they are setting up for user groups. It was just a requirement to be available on the MeetUp group. I resued the one we created for our last #SQLSatNash and posted it on our site. As long as you make the requirement verifiable this should be easy. https://nashbi.sqlugs.com/code-of-conduct/

One requirement that I would like to see and maybe it's just a recommendation. 1) HOW to report something and 2) that organizers plan for having a male & female available to talk to an attendee should there be an issue. I am not 100% certain I would feel like expressing my concerns to a guy.

@way0utwest
Copy link
Contributor

Thanks, I appreciate seeing this link. Getting a few CoCs is important.

@tameraclark
Copy link

Thanks, I appreciate seeing this link. Getting a few CoCs is important.

I reviewed several before working on this. I also added based on the feedback of doing my session "The community speaks". Getting real feedback from people who were actually attending events was very helpful!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants