Git Product home page Git Product logo

Comments (8)

Alex-Yates avatar Alex-Yates commented on July 29, 2024 1

I would advocate for a standard conduct/anti-harrassment policy.

Any event that decides not to use it, or decides to use a different policy, should make their reasons for not following the standard policy very clear to all attendees.

from datasaturdays.

tameraclark avatar tameraclark commented on July 29, 2024 1

@Alex-Yates The current set up has a policy, the policy is vague and is likely written to protect the overseeing umbrella. We did have that option turned on. I think it is still currently optional. We wrote one that was based on several policies that were suggested.

During the SQLSat sessions, I did in 2019 it was discovered that a lot of folks would like to see to promotion of positive behaviors not a list of things that are not tolerated. Also, the current setup gives you no feedback on how to set up a policy, plan, and what to do if something happens. By nature, they can't tell you that because then they could be liable.

from datasaturdays.

tameraclark avatar tameraclark commented on July 29, 2024

How do we communicate the policies around harassment?
How can someone report harassment to organizers?
In the unlikely event that an issue comes up with an organizer how can someone escalate this for mediation?

This year at my event I issued a policy. That was sent as a separate email to all attendees, speakers, and sponsors. For sponsors, it was printed out and left at their tables. The policy included how to report an incident. A room was reserved to handle any complaints and a male and female representative were designated to handle any complaints. It was easy.

The current process is up to each and every event to handle on their own. I have done a few sessions collecting feedback and working with a few other SQLSaturday organizers so we could work together and feel supported.

from datasaturdays.

stephlocke avatar stephlocke commented on July 29, 2024

When I set up satRdays, we started with the policy from RLadies https://knowledgebase.satrdays.org/diversity/

from datasaturdays.

HugoKornelis avatar HugoKornelis commented on July 29, 2024

I prefer events to be mostly independent, but still held to a common standard. To implement that, my proposal would be a baseline policy / guidelines that event organizers are free to use. They can use their own but it has to include or exceed all elements of the baseline. And this baseline policy would not be anti-harrassment only, it would also be very explicit on inclusion.

Enforcement / dealing with complaints should be done locally, by the event organizer. If an event doesn't enforce their policy, then the ultimate penalty would be to lose eligibility to call themselves a DataSaturdays event, and lose access to whatever resources DataSaturdays makes available to events.

from datasaturdays.

rabryst avatar rabryst commented on July 29, 2024

My 2 cents is that the Calgary Data User Group uses a policy derived from confcodeofconduct.com.

from datasaturdays.

amtwo avatar amtwo commented on July 29, 2024

Gah. I missed this issue when I created #47.

In that issue, I list these requirements for an event Code of Conduct:

  • 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)

I think it's important & fair to have a baseline code of conduct that all events are held to. Each event will need to have a supplement to include reporting details for their event. That supplement could also be used for other additions to the baseline Code of Conduct. However, if an event organizer disagrees with the baseline Code of Conduct, they would be free to host their event elsewhere without a Code of Conduct, or with a different one. Allowing any event to have any code of conduct they wish (including one that may be contrary to the community's baseline standards), isn't a scalable approach if we want to ensure folks are able to bring their whole self to the community.

from datasaturdays.

github-actions avatar github-actions commented on July 29, 2024

Accessibility Links:
Audio Link:https://gofile.io/d/3uFPOg
Image Link:https://gofile.io/d/dFNybn

from datasaturdays.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.