In the case of a formal incident being reported, there are two possible resolution paths:
- Raising a concern to the admin to give them context, or,
- Filing a formal complaint that will result in administrative action.
In both cases, the reporter needs to provide the following information to the admin:
- What’s the nature of the incident or Code of Conduct violation?
- Who is involved in this incident?
- What material supports this situation?
- Any privacy concerns? (Reporter consent is required before sharing any information regarding the incident)
With this information in hand, the admin will:
- Work to determine whether this is a raised concern or a formal complaint with the reporter. In the case of a raised concern, the understanding is there may be no action other than administrative awareness.
- Ask clarifying questions of the reporter because every incident is different.
- Work with publicly available content to confirm the report.
- Talk with their fellow administrators to gather perspective.
The admin may deem it necessary to talk to the accused member(s) to gather additional perspective.
With this information in hand, the admin will determine a consequence. Consequences include but are not limited to:
- A Strike
- NashDev operates on a three strike system whereby non-suspending CoC violations can result in one or more strikes. Admins will use their judgement and historical precedent in determining what constitutes a strike.
- When a member receives three strikes, they will be suspended from NashDev for a period of time or permanently depending on the violation. Multiple strikes can be assessed depending on the violation.
- We do not have a definition of what does and does not constitute a strike. As of March 11, 2020 we are keeping a record of all administrative activity to help calibrate strikes.
- Do Not Contact
- A member may not contact (in any fashion, messages or emoji) either publicly or privately, designated members of the Slack for a predetermined period of time.
- Temporary suspension
- A member is suspended from NashDev Slack for a predetermined period of time.
- Permanent suspension
- A member is permanently banned from NashDev Slack
For any type of suspension, the admins will conduct a private vote based on the incident. Majority wins. With the defined incident and consequence in hand, the admin will present the following to the accused member:
- This is what occurred.
- This incident is confidential.
- This is how I confirmed what occurred.
- This is what I decided in terms of consequence. In the case of a non-ban action, explain the terms of Do Not Contact, Strikes, Etc.
For Strikes, members will be alerted to the strike policy and the number of current strikes they have.
For Do Not Contact, members will receive the time period when they can not contact other member(s)
For Temporary Suspension, members will receive the time period when they can not be a part of NashDev Slack.
For Permanent Suspension, members will receive the content above and then permanently removed from NashDev Slack.
The Administrators are committed to resolve incidents within five working days.