You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 27, 2024. It is now read-only.
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.
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.