Talk:Training modules/Keeping events safe/First draft

From Meta, a Wikimedia project coordination wiki

General comments[edit]

All in all a good draft. I appreciate the work that has gone into creating a thoughtful document.

One thought is that people in the middle of a situation don't necessarily think of themselves as filing a report. Rather they are pointing out issue or situation that is occurring and they need assistance. So, maybe we need to carefully consider language that makes it sound like a big deal to tell someone about a problem that they see happening. This is especially true when small problems that are addressed early can be prevented from escalating. Sydney Poore/FloNight (talk) 16:15, 6 January 2017 (UTC)[reply]

Comments on specific sections[edit]

Comments on E1: "Introduction"[edit]

Comments on E2: "Basics"[edit]

Comments on E3: "Situations you might encounter"[edit]

Comments on E4: "Before the event"[edit]

For large events: When selecting a venue:

  • Prior to booking the venue discuss security issues with the venue event coordinator to make sure that the space and policies match the needs of the event.
  • Consider whether the venue is able to provide adequate washrooms including gender inclusive or unisex. Can some of the existing ones be reallocated as unisex if they do not already exist?

Communication at the event:

  • Decide ahead of time a schedule of who will be responsible for being the first responder to various types of problems at the event. How does addressing a safe space violation fit in with other competing problems? Allocate an adequate number of EOT members to address a range of problems. Small problems caught early can prevent escalation to more serious problems.
  • Have a backup plan if the designated people are unreachable or unavailable.
  • Decide ahead of time about a rapid method for contacting more members of the event team and venue security.
    • Consider using mobile phones with headsets to allow for rapid contact and private secure communication.
    • Consider using a code word to alert EOT and event security about a serious problem.

Comments on E5: "During the event"[edit]

Comments on E6: "After the event"[edit]

Comments on E7: "Appendix"[edit]

First draft feedback summary[edit]

Thank you to everyone who has given feedback on the first draft of these modules! We have compiled a summary of the feedback we received here, and over the next month or so we will be working on revising and incorporating the feedback we received into the next draft of the modules. Kbrown (WMF) (talk) 21:24, 30 January 2017 (UTC)[reply]

After the event[edit]

Re: your section on "What would you do? #2: Board member behavior"...

The operational question here is "Some time after the end of an event, User A reports..."

What is the reporting mechanism? Do they post their accusations publicly on a Wikipedia criticism site along with personally identifying information and photographs, or perhaps in some other venue where the accused individual does not have an opportunity to respond? Or do they just have to stop going to events, and participating in the project, if they cannot do so in safety. For any given event, you are going to have problems arise, some that cannot be fixed and others that can be easily be remedied with quick explanations or diplomatic administrative actions behind the scenes, but you have no mechanism for reporting them internally. Your events need to include some kind of debriefing for participants, that includes the option that they can talk to someone in a position of influence after the event (as many distrust a paper trail), or even report something anonymously. Your policies are never going to be "finished" because the challenges and issues will keep changing, but you have no feedback mechanism to track this and stay on top of it from one event to the next. —Neotarf (talk) 16:21, 4 April 2017 (UTC) I see now this draft has been moved without leaving a redirect, so not sure who might have this on their watchlist or is still interested, pinging previous contributors JSutherland (WMF), PEarley (WMF), Jalexander-WMF, Kbrown (WMF), and FloNight. —Neotarf (talk) 16:40, 4 April 2017 (UTC)[reply]