Organizzare eventi in sicurezza

This page is a translated version of the page Keeping events safe and the translation is 12% complete.

Outdated translations are marked like this.

Directory: Tenere gli eventi al sicuro / Materiali visuali

Questo kit di risorse offre un riepilogo conciso e di facile consultazione delle migliori pratiche utili per l'organizzazione di un evento. Non pretende di essere una guida definitiva, ma fornisce consigli e indicazioni per affrontare le questioni relative alla sicurezza durante gli eventi.

Codice universale di condotta

Il Codice di Condotta Universale governa tutti gli spazi Wikimedia. Esso specifica un insieme di comportamenti attesi dei partecipanti, nonché un elenco vietato di comportamenti. Attualmente, la tutela delle violazioni è gestita dagli organizzatori locali o dal Trust and Safety team della Wikimedia Foundation.

La Wikimedia Community e la Wikimedia Foundation Board of Trustees ha ratificato il Codice di Condotta Universale (UCoC) nel 2021. Il UCoC si applica a "tutti i progetti Wikimedia, agli spazi tecnici, agli eventi in-persona o virtuali" ed ad altri tipi di interazioni. Di conseguenza, il Codice di Condotta Universale è rilevante per gestire e per programmare questi eventi.

L'UCoC spiega quale comportamento minimo si aspetta dai partecipanti a Wikimedia, nonché quale comportamento è inaccettabile. Il comportamento minimo previsto prevede:

Rispetto reciproco;
Civiltà, collegialità, sostegno reciproco e buona partecipazione.

Invece un comportamento inaccettabile significa:

molestie di ogni tipo, alcuni esempi includono ma non sono limitati a insulti, molestie sessuali, minacce, incoraggiamenti a danneggiare altri, pubblicazione di informazioni personali, attacchi personali e provocazioni.
Abuso di potere, privilegi o influenza;
Vandalismi sui contenuti e abuso dei progetti

Nel 2023, la comunità e il Consiglio di Amministrazione hanno ratificato le Linee Guida per l'Applicazione per l'UCoC. Queste linee guida stabiliscono cosa dovrebbe accadere quando si verificano violazioni dell'UCoC e come tali situazioni dovrebbero essere gestite dalla comunità e dal Comitato di Coordinamento del Codice Universale di Condotta (U4C). Questo comitato è stato insediato nel giugno 2024, ma non sta ancora esaminando casi, il che significa che fino a quando l'U4C non inizierà a esaminare i casi, il potere di far rispettare le violazioni dell'UCoC è detenuto dalla comunità locale/organizzatori e, nei casi estremi, dal team di Fiducia e Sicurezza della Wikimedia Foundation.

Normativa degli spazi amichevoli

Una normativa di spazio amichevole è una politica messa in atto durante gli eventi e applicata dagli organizzatori. Essa specifica una serie di linee guida che i partecipanti devono seguire per promuovere esperienze libere da molestie.

In generale, la normativa proibisce l'aggressione dei partecipanti, così come altri comportamenti inadeguati in eventi di Wikimedia. La definizione d'aggressione è descritta nella normativa, come quali sono i passi da seguire nel caso in cui qualcuno viola la normativa in un evento di Wikimedia. Per spazi o eventi tecnici, si applica anche il Codice Tecnico di Condotta.

A Friendly Space Policy for Wikimedia events is available on Meta-Wiki. Groups can use it as it is, or adapt it. The final version should be shared with attendees.

Why is a Friendly Space Policy necessary?

One of the Wikimedia movement's core principles is openness and inclusion. This can only be achieved if those taking part in movement activities feel safe. The Friendly Space Policy is designed to explicitly define what constitutes inappropriate behavior, and in turn to allow event organizers to take action to prevent or stop behavior that makes others feel unsafe or unwelcome.

The Friendly Space policy also provides specific provisions for youth safety and keeping events inclusive during times of war.

What does the UCoC define as harassment?

Harassment includes but is not limited to:

Insults: This includes name calling, using slurs or stereotypes, and any attacks based on personal characteristics. Insults may refer to perceived characteristics like intelligence, appearance, ethnicity, race, religion (or lack thereof), culture, caste, sexual orientation, gender, sex, disability, age, nationality, political affiliation, or other characteristics. In some cases, repeated mockery, sarcasm, or aggression constitute insults collectively, even if individual statements would not.
Sexual harassment: Sexual attention or advances of any kind towards others where the person knows or reasonably should know that the attention is unwelcome or in situations where consent cannot be communicated.
Threats: Explicitly or implicitly suggesting the possibility of physical violence, unfair embarrassment, unfair and unjustified reputational harm, or intimidation by suggesting gratuitous legal action to win an argument or force someone to behave the way you want.
Encouraging harm to others: This includes encouraging someone else to commit self-harm or suicide as well as encouraging someone to conduct violent attacks on a third party.
Disclosure of personal data (Doxing): sharing other contributors' private information, such as name, place of employment, physical or email address without their explicit consent either on the Wikimedia projects or elsewhere, or sharing information concerning their Wikimedia activity outside the projects.
Hounding: following someone across the project(s) and repeatedly critiquing their work mainly with the intent to upset or discourage them. If problems are continuing after efforts to communicate and educate, communities may need to address them through established community processes.
Trolling: Deliberately disrupting conversations or posting in bad-faith to intentionally provoke.

Specific to events, especially in-person events, it should be noted that sexual images in public spaces also constitutes harassment, as does harassing photography or recording, inappropriate physical contact, and sustained disruption of events.

Who should violations be reported to?

If an attendee witnesses something they believe goes against the Friendly Space Policy or the UCoC, there are a few courses of action they might take. These are covered in detail in the “Taking action” section of this kit. This information should be clearly explained to attendees (for example, in the opening presentation and on posters around the venue).

If attendees feel safe doing so, telling a person to kindly but firmly to stop the behavior immediately can be the best action in non-violent situations.

Preparing for a safe event

This page supplies a checklist to prepare your event safety procedures. This list can't cover everything—it covers only the essentials.

Well before the event

Publish the event's Friendly Space Policy on the event webpage before the event begins. Link to it in all event communications, such as during the online registration process.
If you are having an in-person event, it is a good idea to print posters summarizing the policies and to display them around the venue.
If you are having a virtual event, you may wish to make attendees agree (via a checkbox or similar) to abide by UCoC and Friendly Space Policy before allowing them to join the event platform.

Create the documents and forms your event's safety team will use during the event, including:
- An incident report form
- An incident logging sheet
- A list of safety-related roles and responsibilities for event organizers
- An event safety plan (in all cases)
- A youth safety plan (for events targeted at ages 15-24)

Just before the event

Designate at least two people to respond to Friendly Space violations. It may be helpful to ask a range of genders and identities if possible. Sometimes people feel more comfortable reporting incidents to someone with whom they share identities. The points of contact must know how to contact local emergency services, Wikimedia Foundation officials, or other authorities as necessary. Brief them on the guidelines. For small events, this may need to be you.
Reach out to Wikimedia Foundation’s Trust and Safety team to receive the event ban list, to help you assess participants.
Make sure those designated to respond to incidents are easy to recognize, for example through special badges or shirts, so that they can be easily located.
For in-person events, collect important contact numbers such as local medical services, hotels, and taxi companies. Publicize them as needed at the event. It’s helpful to place these contact numbers on any welcome papers provided to attendees.
For in-person events, check in with the event venue so that you know their onsite team and security procedures and share your safety plans, including a way to contact your “safety team”.
For virtual events, make sure you are familiar with the event platform's safety and behavioral policies and how to contact the platform's Trust and Safety team in case of emergency.
Be prepared to explain to attendees why the UCoC and the Friendly Space Policy are important.
For virtual events, familiarize yourselves with the platform you are using, including its moderation features. You and other moderators should know how to mute, direct message, and ban on the platform before your event begins.
For virtual events, prepare, if possible, banners to be displayed on the platform about the UCoC and Friendly Space Policy.
For virtual events, consider pinning a message to the chat or using a banner that displays ways to contact your safety team in case of incidents.

During the event

During the opening of the event, remind participants of the Friendly Space Policy and the Universal Code of Conduct their obligation to adhere to these policies. Point out the event organizers who will respond to Friendly Space complaints, as well as any relevant posters or wiki pages.
For virtual events, consider posting regular reminders of the UCoC and Friendly Space Policy into the event's chat. Not everyone will have been present for the opening, and even those who were may forget what was said then.
For virtual events (or in-person events with a chat channel for attendees), the safety team should regularly monitor the chat for incidents or misbehavior.

Dealing with an incident

This is a checklist for steps to take if someone brings an incident to your attention. This is meant as a guide—feel free to adapt it to your needs.

First actions

If there is a threat to safety, call security or police first (in-person) or email Wikimedia Foundation Trust and Safety at emergency wikimedia.org (if virtual) if any additional supports are needed.
Help the person making the report feel safe. Find a comfortable, quiet, and at least semi-private place to speak with them. If your event is virtual, this may involve switching from public chat to direct/private message.
- If possible, ask the person if they would like a friend or trusted colleague present during your conversation.
Listen actively. Follow the advice in the “Taking the Report” section for best practices in speaking with those involved.

Take notes. This provides a record for future actions should they be taken. Important things to record include:
- Time and place of the incident(s)
- Names of people immediately affected
- Names of potential witnesses
- Details of what happened

Consult with the person making the report on actions they would like taken. Be cautious about making promises before you finish your review of the situation.

After the report is taken

Determine what action needs to be taken, and inform the reporter what you are doing. (See the “Taking Action” section for more information on how to do this.)
Follow up. See “Following up” for more details on what to do after you receive a Friendly Spaces report.

Taking the report

While taking a report, your job is not to determine the validity of the incident being reported. Clearly document the situation as the person describes it. Be a non-judgmental listener—people with a strong empathetic listening presence are best suited for taking reports. Take notes while you listen, or write the details down as soon as possible.

Before taking the report, confirm that the person understands the reporting process.

Review the actions that will be taken if the person makes a report.

I want to make sure you know who will have access to a report if you make one.

You will be consulted before further actions are taken.

(Clarify that illegal activity will be reported to authorities.)

Set reasonable expectations about what kind of protection and support the person will receive after making the report.

Use mirroring and clarifying questions to make sure you are correctly understanding the story.

The incident happened as soon as you entered the room. Did I get that right?

Do you remember anything else that was said?

Avoid making interpretive comments like:

"This doesn't make sense to me"; "Are you sure they said that?"; "That seems out of character for that person"

Have the person review what you have written for accuracy before finalizing the report.

Acknowledge their emotions and offer support.

I know that this experience was upsetting and stressful.

It looks like you are having a hard time. Is there anyone that you would like to be present while you make this report?

Assure the participant that you have heard their complaint and will take action.

Give a timeframe for next steps. You do not need to commit to what action will be taken. See “Taking action” for examples of what you can do depending on the situation.

Thank you for reporting this. We will use it to take the appropriate actions as soon as we can.

Taking action

Having a Friendly Space Policy is a great first step towards keeping an event safe. To be fully effective, however, it requires organizers to know how to handle threats to event safety.

Exercise civility. Treat others with kindness and respect. Sensitive topics that are more prone to causing offense (i.e. religion, politics, nationality, etc.) should be treated with extra diplomacy and care.
Be considerate of physical boundaries. Boundaries vary from person to person and from culture to culture. Use extra sensitivity in relation to others’ physical spaces. Ask permission rather than assuming that others are comfortable with touch, including well-intentioned hugs, kisses on cheeks, etc.

Be an ally. If you experience or witness someone making a hurtful comment, remind the person about the Friendly Space policy and ask them, kindly but firmly, to stop. Keep in mind that in some cases people may not realize that their actions or words are hurtful. Consider ways to support the recipient of the comment, as appropriate.
Inform event organizers. Inform event staff as soon as possible after you witness an incident so they can take appropriate action promptly. Early intervention may prevent escalation of behavior.

Level of severity	Description	Examples	What should organizers do when an incident is reported?
Low	Comments made that do not directly target a specific person or persons but cause offense. Offense appears to be unintended or perhaps not even understood by the speaker.	An audience participant makes a series of disgruntled comments at a presentation. A participant enters others’ physical spaces, making them uncomfortable.	Remind those involved of the UCoC and the Friendly Space Policy. Explain why certain actions or words might make others uncomfortable. This interaction should be respectful, with an assumption that the offense was not intended.
Medium	Comments made that are intended to offend or attack fellow attendees. Behavior that is considered antisocial or unwarranted, or which has already been warned against in the past.	A participant aggressively confronts another attendee about their editing and continues after being told to stop. A participant continues to take photographs of people without consent after being asked to stop.	Individuals who violate the UCoC and Friendly Space Policy on multiple occasions may be politely yet explicitly told to leave. If the person refuses or becomes aggressive, contact venue security or the police while virtual organizers may forcibly remove the attendee from the platform ("kickban" them).
High	Behavior is targeted and has a high chance of resulting in physical or mental harm to the person targeted. Behavior violates applicable laws, or is an repeated pattern of Friendly Space/UCoC concerns that have resulted in prior warnings.	A participant repeatedly touches another participant inappropriately. A banned person attempts to enter the venue. A virtual participant posts sexual images of another participant in open event chat.	The participant must be asked firmly to leave the event. If they refuse, contact venue security or law enforcement (if in-person)—do not put yourself in danger—or remove and ban the participant (if virtual). You may also wish to contact the event platform's Trust and Safety team (if virtual). If a report is made, it must be escalated to Wikimedia Foundation staff and, if applicable, to local law enforcement.

Following up

If an incident occurs at your event, it is valuable after the event for everyone involved to do a short review of how it was handled. Here are some suggestions for how to follow up.

Evaluate how any incidents were handled.

Depending on the size of your user group or chapter, you should write up an incident report containing information like:

What happened
Who was involved
What action was taken
What the outcome was

Learn from the experience.

Set up a time for those who dealt with the incidents to discuss what happened, or just take notes for your own evaluation.

What went well?
What could have been done better?
Were there any tools or resources you think would have helped?
- Do these exist and can you arrange to have them next time?
- Do you need to suggest they be created?
If you are not feeling confident about organizing more events—what do you need to gain back that confidence?

Share the report.

If the incident resulted in a report, please pass it on to your Grants Program Officer or to your Wikimedia Foundation contact. If you don't have one, you can email the Support and Safety team at ca wikimedia.org. Providing this information to the Wikimedia Foundation will help them design better practices and resources for event organizers.

If the incident took place at a technical event, such as a hackathon, refer your report to the Technical Code of Conduct Committee.