-
Notifications
You must be signed in to change notification settings - Fork 65
Code of Conduct #47
Comments
I agree with the above, and I think a CoC/AHP ought to be one of the few rules we implement. |
Accessibility Links: |
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. |
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! |
We need a Code of Conduct (or Codes of Conduct) to support:
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:
We should additionally provide resources for event organizers so that they feel equipped to provide assistance & response.
The text was updated successfully, but these errors were encountered: