Giter VIP home page Giter VIP logo

coc-guidelines-taskforce's People

Contributors

kariljordan avatar tracykteal avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

kariljordan

coc-guidelines-taskforce's Issues

Guidelines for communicating with staff/EC about CoC incidents

The following Code of Conduct incident response procedure was developed collaboratively by The Carpentries Staff.

Procedure

From this procedure I will create a checklist for incidents that require an immediate response , i.e. the community member is removed from all Carpentries engagement.

We need to include language in the CoC that states staff/EC members pertinent to the operations of The Carpentries will be made aware of persons under review such that their privileges can be revoked.

Feedback Request: Please provide recommendations for how to phrase this type of statement by 17-February. I will then add the statement to the CoC Documentation in the appropriate spot(s).

Revise Enforcement Manual

Draft a revised enforcement manual in readable format. Be sure to track changes.

Points to include:

  • Ensure that staff pertinent staff are told about investigations
  • Ensure that instructors being investigated are not placed with new workshops or instructor training events
  • Discuss and decide to what extent the EC should have access, and how.
  • Issues with CoC implementation

Suggestion: add a tldr section to Coc

At an admin meeting it was brought up that the Code of Conduce can be a long or intimidating read, especially if someone is feeling upset. Suggestion is to have a 2-3 bullet point condensed version that people can easily refer to even in a stressful situation.

Request for Comments: Code of Conduct Incident Report Form

update: The original form was created under The Carpentries organisation Typeform account. This means that all staff would have access to the results of this form. Because of that, I created a new form using Google Forms. The Typeform form was deleted.

Here is the draft incident report form. You can scroll down to view the questions without adding information. Please provide your feedback in this issue.

Deadline: 17-February 2019

We should have a form that people and/or the CoC committee can fill out to gather necessary information regarding an incidence.

Note: at present this form is platform independent, how to gather info is a separate issue.

To be reviewed by policy when done.

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.