Code Universel de Conduite/Consultations aux affiliés/Rapport

This page is a translated version of the page Universal Code of Conduct/Affiliates consultation/Report and the translation is 38% complete.
Code de conduite universel

En février 2021, le Le conseil d'administration de la Fondation Wikimedia a approuvé un Code de Conduite Universel (CCU) qui couvre tous les espaces du mouvement, y compris les projets wiki, le personnel de la Fondation et les membres affiliés, en ligne et hors ligne. Il définit un ensemble minimum de comportements attendus et inacceptables sur lesquels les parties prenantes du mouvement peuvent s'appuyer pour définir leurs propres politiques et directives, sans toutefois les dépasser. Le processus d'application et de mise en œuvre du Code de conduite universel est un facteur important dans la création d'un environnement sûr et inclusif dans nos Affiliés et sur les lieux de travail wiki.

Dans cette phase du projet, qui vise à créer des définitions claires des voies d'application et des processus de signalement, les communautés Wikimedia et les affiliés de toutes tailles, de tous types et de toutes expériences ont été invités à participer à des discussions pour partager leurs idées, leurs réflexions et leurs préoccupations concernant la mise en œuvre, le signalement et les voies d'application du code.

Dans l'ensemble, les affiliés pensent que la Fondation Wikimedia devrait coopérer activement avec les sections locales et les groupes d'utilisateurs, en les aidant à résoudre les problèmes de comportement au niveau local lorsque cela est possible ; cette coopération pourrait être améliorée efficacement par le développement et la mise en œuvre d'un code de conduite universel (CCU), et l'existence de règles de conduite et de résolution des conflits entre les participants dans les règlements internes des groupes locaux. Les affiliés reconnaissent également qu'il est impossible d'exclure l'émergence de différents types de problèmes lors d'activités impliquant de nombreux participants, ce qui pose un défi au processus d'application.Beaucoup de bonnes idées ont été suggérées au cours des discussions, et de nombreuses propositions ont été reçues de différents affiliés après avoir discuté en interne des principaux objectifs du processus de consultation.

En remerciant les hôtes, il convient de noter que l'équipe du projet CCU a eu l'occasion de présenter le processus de consultation et d'autres activités connexes lors de certains événements mondiaux des affiliés, notamment les réunions régulières de l'ESEAP et les réunions mensuelles du SWAN.

Processus

Invitations were sent to all Affiliates during March and April 2021, starting with the Affiliates that showed interest in the “Safety and Inclusion Requirement” of the Movement Strategy, and ending with the newly recognized Affiliates. Many Affiliates, focusing on well-structured and experienced ones, were invited to direct open discussions. Meetings were conducted with 23 affiliates of different sizes; mostly the directors of these Affiliates attended the meetings, but some also invited different members to participate.

In addition, a survey was sent out to most of the Affiliates in 8 languages, either to the contact persons, directors, mailing lists, meta page, or through an official communication channel. The total respondents were 147 from 24 different Chapters/Thematic Organizations and 27 different User Groups. Both the discussions and the survey were useful tools to get feedback from participants; Affiliates shared their experience in implementing local procedures, policies and code. Learning about the Affiliates’ experiences and the extent to which their experience can be applied and replicated through the emerging UCoC enforcement outline is of great importance. Some Affiliates conducted internal discussions and included the UCoC text in the agendas of their regular official meetings and provided collective feedback.

Situation actuelle

Every Affiliate should have a conflict resolution policy. Most of the consulted Affiliates state they have local procedures, bylaws, and policies. However, some Affiliates know whether everyone is aware of them and knows exactly how to use them.

Internal processes

Well-established Chapters explained that they rarely receive complaints about unacceptable behavior, or at least incidents were happening but not being reported. So current procedures are often untested and Affiliates require more clarity on how to deal with issues. Issues include who incidents should be reported to internally, and what the requirements are in terms of wider escalation. On the other hand, three Affiliates explained that they developed and enforced local code of conduct after they faced internal interpersonal conflicts and problems. Some Affiliates reported that they are not very satisfied with the policies they have. They believe they need to enhance the rules. The processes need to be formalized in case they need to refer to these bylaws and policies in front of a court for example. Others need to provide appropriate translations because they usually face challenges in communication in other languages.

Role in online conflicts

Affiliates also believe that abuse or harassment is significantly less likely to happen during an event (whether in person or online) compared to asynchronous online communications or projects. Affiliates shouldn’t be involved, let alone be the “judge and jury” in on-wiki situations. Adjudicating such conflicts is the responsibility, and often burden, of the administrators’, who usually face more challenges governing behavior and implementing local policies. However, in some cases, participants refer to Affiliate leaders to report or seek advice about cases that happen online such as banning or blocking. Affiliates usually try to avoid interfering in content-related issues. Affiliates which focus on online content haven’t seen the need to create any type of code because it’s mostly online activity. On one occasion, the talk page of the Affiliate became the anti-harassment tool and space for reporting cases.

UCoC enforcement

Almost all participating Affiliates don’t think that UCoC enforcement will or may conflict with the implementation of local procedures or policies. Many participants said that once the enforcement pathways for the UCoC have been agreed and this has been codified into Wikimedia Foundation policy then they will review their own internal policies and procedures and make any changes necessary to ensure alignment.
Participants said that there needs to be an affirmative moment whereby a participant agrees to be bound by the Code of Conduct if they are to be held to it. So Affiliates follow different approaches to enforcing their local policies and informing members about them. For example, one user group adds a link to the policy in the talk page of any project they initiate or host, along with a section for signatures where participants have to sign in acknowledging that they have read that friendly space policy. Other groups provide access to the guidelines to each member in advance before joining a project. By doing so, it becomes the invitee’s responsibility to read the policy and know that the rules are effective and will apply.
An interesting mechanism one Chapter applies to enforce the Friendly Space Policy is using a system that mimics a traffic light. Members who violate the policy receive a warning (yellow), repeating the violation is another warning (orange). When it turns red on the third strike, the organization decides a penalty, which could be withdrawing membership – which will not limit people’s participation in events but will limit the person from benefiting from grants.
Some well-structured Chapters think that if the Chapter has a successful process, they may not replace it with the UCoC, and at the same time, they will not ignore the UCoC, but rather will educate their members on how to refer to it to assess any situations they may face.
It is worth mentioning that the consultations gave some groups an opportunity to look at the UCoC policy, educate their Affiliate members about it and translate the related pages on Meta. This is a useful side effect of the process.

Défis

The major challenge the enforcement outline drafting process will face is the difficulty of producing a policy that truly represents needs and values from around the world, due to the global nature of the UCoC. Following are the major challenges and concerns related to UCoC, gathered from the Affiliates consultations:

Relationship with the Wikimedia Foundation

There were some concerns that given the current relationship between the community and Wikimedia Foundation, some communities/groups and many members of the communities could simply refuse to acknowledge the legitimacy of the Foundation as an enforcer and in general some stakeholders won’t welcome whatever comes from them. Relations with WMF teams, specifically the Trust & Safety team (T&S) and the Legal Department, are often not well established.
  • For example, one of the attendees explained that when he faced legal threats, it was hard to explain to the legal team, due to language and cultural barriers. The legal team was not prepared to support them.
  • Another case was that volunteers couldn't obtain legal support against legal threats that they faced once, because they are not staff, but only volunteers.
  • A few participants mentioned that they are not happy with how complaints are handled, investigations about harassment cases are done in an unacceptable way, some volunteers claimed they were accused for problems that they already knew nothing about or were not involved in; investigations don’t fairly balance between trying to protect users against false allegations and trying to satisfy complainants; there are concerns that users are now encouraged to report false cases to T&S because there isn’t a balanced mechanism nor transparency in place in the view of participants.
  • In addition, sometimes, there are problems with hypothetical scenarios, including that people report directly to WMF because they cannot assess the situations locally. T&S should investigate these issues considering local perspectives, there is a gap in communication, and there has to be a known mechanism of investigations and communications with all parties.

The possibility of the code creating a structure where local conduct decisions by administrators and elected arbitrators could be overturned unilaterally by the Trust & Safety Operations team was opposed; desire for that team not to function as an effective “court of appeals” for local decisions

— an Affiliate member

Low trust among community members

People find it difficult to deal with the allies of users they have concerns about in communities, because communities tend to protect some people who break the rules.

UCoC implementation in social media conversation

How will the UCoC be implemented when it comes to communications in social media? This was a concern that some small-sized Affiliates raised because they depend on social media for communication. However, while many are strongly against the usage of WhatsApp and Telegram, they often recommend using Signal instead.

Integration of local policies with UCoC

For the benefit of the wiki community, local Wikimedia Chapters and user groups can also support conflict resolution in online Wiki projects. However, here, organizations can act as advisors or facilitators but not directly interfere in the internal discussions of online wiki projects. Still, some Chapters explained that the integration of their local policies will not contradict the UCoC and the implementation will be easy. When it comes to the online language communities, where most of the violations happen and where volunteers usually reach out to the Affiliate directors or members for support related to their on-wiki participation, such as banning/unbanning, etc., it will not be easy to integrate the local policies with the UCoC. This challenge is especially important when Wikipedia and its sister projects are not limited to a single-country but cover languages spoken in several countries; such as Portuguese and Spanish projects.

Concerns of discrimination

In the multilingual Chapters, the problems of discrimination are very probable, but they find it difficult to apply the policies specially that there is some type of integration with other Chapters. For example, Chapters that have members of different languages, and on the other hand, some languages are handled by different Affiliates, such as Arabic Wikipedia and Spanish Wikipedia. The problems arise when the conflicts happen on-wiki and Affiliates are requested to engage in managing such conflicts.

Legal dispute concerns

Under the UCoC, how will staff of Affiliates be managed in case they are involved in legal issues that relate to their work or to other members? For example, if an Affiliate staff member is being sued in front of the court for a decision that he took against a member or as a witness. There is a need for more conversation about this.

Maintaining confidentiality

Sometimes individuals or certain groups perceive local Wikimedia organizations as the owner of Wikipedia and send a request for information about editors. It is important that the local Wikimedia organizations maintain the principle of confidentiality, thus protecting editors from possible harassment. Of course, in smaller countries the staff of the organization often knows most of the online editors, because they entered the Wikimedia movement through the organization's projects and programs. From this point of view, the reputation of Wikimedia in that country and the professionalism of the Affiliate staff are important in order to be able to protect the right of editors to privacy.

Handling of criminal cases

In the event of serious criminal elements (physical threats, sexual harassment, blackmail, slander, etc.) in conflicts arising in online wiki projects, some Affiliates advise victims to report to law enforcement agencies. This work can be done by both the victim and other editors familiar with the issue. Yet it’s not clear how the victim can collect evidence, present the case to the intended agency, or even how local laws may apply to wiki-related issues, neither the support the Affiliate provides is clear.

Content creators versus community organizers

Currently there is a big divide between community-centric Wikimedians and content-only, online -only Wikipedians. Help bridging that gap is needed; restarting conversations about dispute resolution, Women contributors – micro-aggressions, cliques, “tribalism” how can these issues be addressed?

Lost in translation

Wikimedia behavioral regulations are mostly written in complex English that is not understood by many non-English-speaking contributors. On the other side, the Wikimedia Foundation has a limited number of non-English speaking staffers (for example Chinese) that could understand reports and reply emails from non-English speakers.

IP contributions

Contributions by IP address editors have been one of the major contention points---a lot of projects saw confrontation and harassment from IP address editors, which can be nearly impossible to trace if using proxy services.

Cas particuliers

  • Affiliates in Europe need to comply with the regulations of General Data Protection Regulation (GDPR), especially when it relates to revealing personal information. However an Affiliate clarified that GDPR is only for databases. There is a need to consider if this will contradict the UCoC.
  • Members of the WikiWomen's User Group did not want to attend the meeting the project team offered because they were expecting some help from the Wikimedia Foundation regarding notability criteria on Wikipedia, a major barrier to some gender-centric initiatives. However, such help did not come as hoped-for and so they don't think their opinions on the UCoC will be listened to either. The UCoC community facilitators are mentioning this scenario to illustrate one of the reasons why Affiliates/communities may refuse to participate in the UCoC conversations.
  • Contentious political situations between Hong Kong, Taiwan, and Mainland China has led to several behavioral and safety issues, some of which have also implicated the Affiliates in that region.
  • One facilitator had several discussions with two leaders of the Wikimedia Russia and Russian-speaking user groups. The focal point was about the lack of participation by their community. The two leaders explained that many people appear to be upset and unwilling to fill in the survey, criticising it instead of filling it in. They themselves thought the survey looked like nonsense because it’s uncommon to them, questions seem to be hardly understandable and of little relevance. They hesitated to answer some questions because they felt that it was somehow dishonest if they did. According to them, most of their members tried to say the same thing and that is one of the reasons why their attitude to the Code is neutral to negative: ”much of useless side activity spreading community resources thinly”. However, they are planning to make their own Trust and Safety team of one person and want to propose the role to the group soon. They asked the facilitator if that’s a good solution. The main complaint has been that Russian community gets little attention from WMF, which has made many surveys and requests and many people were answering it for years, but almost nothing is getting done in response. There were many discussions at Meta about how to translate UCoC text properly into Russian. Many users provided feedback. Their feedback was ignored and WMF keeps proposing the erroneous versions.

Requests and thoughts for effective enforcement and reporting

Reporting behavioral issues that may occur in the wikimedia projects and user groups is one of the most important pillars of this Code of Conduct. The code must clearly identify all possible practical reporting pathways making use of the successful processes that some Affiliates currently apply, considering all challenges and requirements of the different communities and groups, such as safety and protection. Another important consideration is to recognize the different sizes and abilities of organized groups in the movement in terms of their capacity to receive reports and action them. In addition, enforcement outlines should consider the differing abilities of community members to communicate and interact in social groups.

Most of the Affiliates that participated in this consultation didn’t clarify specific reporting pathways, yet most of them agreed on that problems arise within the Affiliate’s activities must be addressed by the relevant structure of the Affiliate and severe cases must be addressed by the foundation and in case of conflicts with criminal elements, the victims can apply to the law enforcement bodies in their countries; however, more than one Affiliate requested that if a complaint is immediately addressed to the Wikimedia Foundation, then the local Wikimedia organization must be actively involved in the process of addressing the issue. Not only that, but Affiliates also need to know when they are obligated to report conduct issues to the Foundation under a new reporting environment.

Where we need support is to jointly clarify in which cases it will be the Chapter’s responsibility to respond to UCoC violations, and in which cases this responsibility lies with the Wikimedia Foundation

People need to know whom to return to, this means roles and responsibilities in the Affiliate have to be clarified in regards to the new code, specially that some communities are very diverse and it’s difficult to see who should be in charge. At least one Chapter expressed concerns that, if written into grant agreements with insufficient clarity, it would expose the Chapter to new avenues of litigation by people the Chapter has asked to leave events or the membership group.

In this context, the Affiliate’s chairman, a supervisory committee and the staff should be considered problem-solving platforms and hence they have to be able to identify conflicts and provide constructive solutions, considering public safety and solidarity. Smaller Affiliates think that there is a need for a committee of specialized people including a consultant from Wikimedia Foundation who would be responsible for enforcing the rules and remind people about the policy.

Enforcement requires some proportionate sanction – there has to be a meaningful downside to infractions, but the punishment has to be seen to fit the violation. But the goal should not only be to find and punish the culprits, to protect the victims, but also to reconcile them in that process, to bring them to a constructive field. However, sometimes it is not possible to deescalate the situation and to eliminate the mistakes without an administrative sanction. In that case, the administrators must be strictly guided by the regulations.

Arbcom has been mentioned as well as a successful model in some communities; but it didn’t work in others. Some claimed that it’s not easy to find volunteers who are willing to join Arbcom teams, and at the same time, it may fail due to the nature of the community.

In the case when a member faces a behavior problem, in an event, they report to the organizers of the event; there may be a need to identify the considerations to be taken when wikimedians participate in an event that is organized by external organizations.

One Affiliate mentioned that they think the majority is silent because they don’t know they can report or because the rules are not there; this is a big challenge that can be solved by education and awareness programs. There is a need to better define the types of harassment and how participants can be aware of these types including defining the types that can be or should be reported. What’s important is to define how harassment can be prevented before happening. One Affiliate is in favor of a global enforcement plan that could be adapted and contextualized within the interests of local communities, and supports the idea of a localized enforcement within appropriate local authorities.

The procedures of accepting complaints should maintain confidentiality, and each event and program has to have rules which are mandatory for all participants. Many Affiliates think training is needed for Affiliates to direct them on how to solve different types of situations; also training is required for volunteers to educate and guide them on how they should react if they face problems. Also, training was requested on topics that could help them prevent the non-accepted behavior before it occurs. A need to educate people, especially more experienced members who may have to commit to the implementation; not only that, but as some Chapters will use the UCoC as a reference, they need to educate their members about it and how to refer to it.

Currently, the most commonly used reporting tool is emails. It’s good that many groups designated an official email to report through, but the challenge is that people don’t report or detail the situation the same way and this needs to be enhanced, possibly using a unified template. Moreover, it’s been clarified that only staff can access this email, and staff are committed to protect the details of the members according to the contracts they sign.

Discussing safety of reporting, some participants envision a tool that provides three options (or levels) of reporting: report that can be published to the public, report that can be handled privately, but can still be shared with some people, and reports that should always be managed privately and securely. The tool should be accessible online in the Wikipedia pages, talk pages, village pumps and in the meta pages of the Affiliates. Contrary to that, others believe that reports should never be made publicly, but ideally, there must be as many channels as possible that are low-threshold and protected/private so that people can contact their Affiliate confidentially via their preferred channel.

We believe that the safety of the complainant is of great importance and of the highest priority, but not highest priority, Highest priority is to clarify and solve the case.

There is a need to enhance the communication ways in order to guarantee a successful implementation of the UCoC. There is a need to educate the directors how to be responsible for implementation then they will be responsible for teaching other members and newcomers regularly. For non-responsible members, there is a need to produce visual teaching materials like animation and videos.

Demande de soutien de la WMF

Almost all user groups will require support to build a system for implementation. The support needed is categorized as follows:

Guidance and awareness

To enforce the UCoC, many groups will need support from Wikimedia Foundation to define the easiest ways of implementation, especially in the political and legal influenced issued; and helping the on-wiki victims to provide evidence on the cases they faced more easily, because they hold the entire burden of the problems.

Empowerment

Chapters and user groups which feel responsible for smaller local language communities usually require support to support these isolated communities to boost their participation, which is vulnerable to stop and withdraw because they don’t feel welcomed and may face bullying; Wikimedia South Africa, for example, raised this concern.

Supporting harassment victims

Locally, this can be limited to a certain level, but groups need to learn how to provide this support. Of the good practices some Chapters do, that can be taken as lessons: in Wikimedia South Africa, they do campaigns sometimes on social media, but that's not sufficient according to them. Wikimedia CH (Switzerland) apply a program for mediation, where they are willing to pay for mediation for any member who may need it when facing problems, especially threats or harassment; and even for members who violate rules, if that would help reduce conflicts. This is similar somehow to the psychological help program that Wikimédia France applies.

Legal support

Some User Groups and Chapters mentioned the need for legal support. This includes supporting members who face external threats or course suits; such members usually need guidance and counselling; a designated legal expert can be appointed to guide people on what they can do considering the social aspects. Wikimedia CH is willing to pay for these members and for lawyers in case they need that support. In addition, this type of support is required for the entire group/chapter, especially if they lack sufficient experience (take the case of banning the Turkish Wikipedia and the support that Wikimedia Community User Group Turkey needed as an example). This support could be from local entities or from the WMF’s legal team. Hiring lawyers by the foundation for the benefit of the Affiliates is also a request; however, these hires may not be safe doing their job under certain political tension (for example, the Chinese-speaking community).

Building relations

WMF should support in building better relations with governmental entities; for example, participants may face problems when initiating projects like photo contests, which cause frustration. Such support will help create a healthier environment.

Wikimedia Foundation has resources, and relationships; they can form diplomatic channels with entities that can provide protection (i.e. safety net) and formal allies like Human Rights Watch

— an Affiliate member

Financial support

Financial support may be needed to hire consultants, and to build the required tools (e.g. for reporting). User groups would be open to receive additional funding to invest in T&S, maybe by hiring specialists or lawyers. Currently, the financial support Affiliates receive from Wikimedia Foundation to invest in community health is insufficient.

A user group like Wikimedia Indonesia technically handles a country the size of Europe with a shoe-string budget!

Technical support

To build the required tools, visual aids and educational material.

In May 2020, the WMF Board of Trustees posted a Statement on Healthy Community Culture, Inclusivity, and Safe Spaces, in which the Board, among others, instruct the Foundation to “significantly increase support for and collaboration with community functionaries primarily enforcing such compliance in a way that prioritizes the personal safety of these functionaries”. In addition, the Board explicitly directed the Foundation to “make additional investments in Trust & Safety capacity” and undertake it “in coordination and collaboration with appropriate partners from across the movement”. The Affiliates could be one of the targets of this mandate, owing to its strategic position within the Movement; perhaps through more target-specific funding as part of the Grants.

Sondage

The survey was sent in 8 languages to many of the Affiliates to share with their members; it was also sent directly to many other affiliate members directly using mass messages, on talk pages, and using Affiliates’ official communication channels including mailing lists. The total respondents were 147 from 24 different Chapters/Thematic Organizations and 27 different User Groups.

The questions of the survey aimed at measuring the members’ knowledge of the local procedures and policies of their Affiliates using suggested pre-defined statements that guide the participant; in addition, other questions encouraged the participants to provide thought on the best enforcement and reporting practices based on their experience.

Who did respond?
Quel est votre rôle au sein de l’entité affiliée ?
Depuis combien de temps êtes-vous impliqué dans cette entité affiliée ?

Local policies and reporting system

Status of local policies
Pensez-vous que votre entité affiliée a et suit un code de conduite local, des règles ou des politiques suffisantes permettant de prévenir et/ou de gérer les conflits ou les mauvais comportements entre les membres ?
2. At what degree do you feel your affiliate’s policies/bylaws are sufficiently comprehensive to effectively prevent bad behavior against contributors/participants/organizers or other staff members, in any event the affiliate organizes, such as conferences, gatherings, meetings, workshops, etc: (1=Not at all adequate, 5=Fully adequate)

When asked about the degree of effectiveness of the local policies in preventing bad behaviour, the average value is 3.65 and it does not vary depending from the length of the involvement in the affiliate but looking at the values for the different roles the average of confidence in the local policies is slightly lower for board members (avg=3.49).

Status of local reporting system

Votre entité affiliée dispose-t-elle d’un système de signalement clair que tous les membres peuvent utiliser facilement?

As concerns the existence of a reporting system there are sometimes contradictory answers within the same affiliate meaning that probably even if reporting pathways are existing not everybody among members, staff and sometimes also board members is aware of their existence.

There were different comments about reporting systems. Some respondents share the opinion that no formal system is needed within small communities where everybody knows each other and informal methods are supposed to work, on the other hand it appears that some bigger Affiliates with staff have a formal reporting pathway for participants and members but sometimes forget about their employees who do not have or are not aware of a structured and clear reporting system. There are different suggestions, like the appointment of an experienced single person qualified in conflict resolution and arbitrage or the creation of a dedicated channel for these reports.

Comment avez-vous appris l’existence du système de signalement de votre entité affiliée?

Comment avez-vous appris l’existence du système de signalement de votre entité affiliée?
Moyen de paiement Respondents
Par moi-même en consultant la documentation sur wiki 41
Indiqué par un dirigeant ou un membre du personnel de l’entité affiliée 37
Indiqué par un membre de la communauté 21
Other reported tools were emails sent by the affiliate in some cases during joining procedure, conferences or off-wiki events.

Besides telling that "if you have any issues, turn to person X", we have none.

— Survey response

I am really not sure there is a proper reporting system within the association. In our CoC page there is only one sentence saying "in case of violations refer to this CoC by sending a public or private message", but it doesn't indicate where to send the message.

— Survey response

The main tools where respondents expect to make a report are via Email (121), in-person (64) and 54 would make them via social media, meaning some communication app like Whatsapp or Telegram. Only a few respondents referred to IRC (12) or other ways like noticeboards or affiliate specific tools like internal mailing lists or private wikis.

As privacy of the reports and their outcomes concerns the two main questions were about:

À votre avis, qui devrait pouvoir consulter le contenu et les résultats d’un rapport de signalement?

  • Parties directement impliquées: 93
  • Directeurs, conseil d’administration et personnel de l’entité affiliée: 89
  • Fondation Wikimédia: 70
  • Grand public, via les portails officiels des entités affiliées: 37

Many respondents answered that this depends on the sensitivity of the issue and on the details, transparency and accountability are considered important but not if it compromises the safety of the involved parties.

There is a thin line between the right to privacy and the need for transparency.

— Survey response

Dans quelles circonstances pensez-vous qu’un rapport de signalement devrait être privé ?

  • Rapports impliquant des informations potentiellement identifiables: 64
  • Tous les rapports: 51
  • Rapports impliquant des atteintes personnelles: 55
  • Rapports impliquant des auteurs d’atteintes de longue date: 20
  • Aucun (tous les rapports devraient être publics): 15

Anything that is not resolved should remain private. Only summary information should be made public for evaluation purposes after resolution.

— Survey response
Status of reporting system

Dans quelle mesure êtes-vous satisfait du système et processus de signalement défini et suivi dans votre entité affiliée ?

Légende

  1. Mon entité affiliée dispose de suffisamment de ressources pour enquêter sur les plaintes et assurer un suivi
  2. Les membres du personnel chargés de traiter les plaintes sont bien formés et chevronnés.
  3. Un nombre suffisant de directives et d’instructions permet de guider les membres quant à la manière d’envoyer un rapport de signalement.
  4. Le processus d’enquête est transparent.
  5. Une bonne communication est établie avec le(s) plaignant(s) et le(s) défendeur(s) au cours du processus
  6. Pendant le processus d’enquête, toutes les parties (c.-à-d. les plaignants et les défendeurs) sont traitées avec dignité et respect
  7. Les problèmes sont généralement traités en temps opportun.
  8. Les plaignants se sentent généralement en sécurité et protégés.
  9. Les plaignants peuvent suivre le traitement des plaintes pour s’assurer qu’une enquête est menée.

Quelles sont les raisons pour lesquelles les membres ne signaleraient pas un comportement inapproprié ou contraire à l’éthique dans votre entité affiliée ? Veuillez sélectionner toutes les réponses pertinentes.

  • Il n’existe aucun protocole ou processus clair. Ils ne sauraient pas comment procéder: 62
  • Manque de soutien de la part de la direction et/ou d’autres membres de l’entité affiliée: 22
  • Manque de confiance quant au traitement juste des problèmes signalés et crainte de représailles: 48
  • Crainte de représailles: 50
  • Préoccupations concernant leur réputation ; ils ne voudraient pas être considérés comme des personnes impliquées dans des problèmes: 61
  • Préoccupations concernant la réputation de l’entité affiliée: 27
  • Le processus de signalement n’est pas transparent, et il n’est donc pas fiable: 22
  • Ils sauraient comment réagir de manière appropriée en cas d’événement indésirable les concernant ou concernant un collègue, sans se référer à la direction de l’entité affiliée: 27

(Veuillez répondre à cette question si vous êtes membre du Conseil d’administration ou membre du personnel. Si vous n’êtes pas membre du Conseil d’administration ou membre du personnel, veuillez IGNORER la question.) Parmi les énoncés suivants, avec lequel ou lesquels ÊTES-VOUS D’ACCORD concernant les processus de conduite de votre entité affiliée ?

  • Notre code de conduite (CdC) local est accessible à tous les membres: 44
  • Notre code de conduite et nos règlements locaux sont toujours consultés (à titre de référence principale) pour enquêter de manière impartiale et objective sur une plainte liée à un comportement: 31
  • Les plaignants peuvent suivre le traitement des plaintes qu’ils signalent et peuvent demander des mises à jour: 34
  • Le code de conduite et les règlements locaux sont examinés régulièrement et mis à jour si nécessaire: 23
  • Nos lois internes sont souples pour permettre des modifications et amendements, ainsi que pour traiter d’éventuelles lacunes: 28
  • Le Code de conduite universel n’entrera pas en conflit avec notre code de conduite local, mais le complétera et l’enrichira: 42
  • En tant que dirigeants/membres du personnel d’entités affiliées, généralement, nous définissons les attentes et apportons des clarifications concernant la confidentialité, et ce à quoi le plaignant peut s’attendre au cours du processus d’enquête: 22
  • En tant que dirigeants/membres du personnel d’entités affiliées, nous sommes désireux d’écouter davantage si les plaignants ne sont pas satisfaits des résultats: 31
  • En tant que dirigeants/membres du personnel d’entités affiliées, nous conservons des registres sur le contenu et les résolutions relatifs à chaque cas ou plainte: 26
  • Les leçons tirées des enquêtes sont communiquées au personnel et aux membres: 20
  • En tant que dirigeants/membres du personnel d’entités affiliées, nous estimons que la sécurité du plaignant est d’une importance capitale et d’une priorité absolue: 39
  • En tant que dirigeants/membres du personnel d’entités affiliées, nous évaluons généralement nos systèmes de signalement et encourageons leur utilisation afin de garantir que les plaignants signalent en toute sécurité les incidents et les mauvais comportements: 18
  • En tant que dirigeants/membres du personnel d’entités affiliées, nous sommes satisfaits de notre processus de signalement. Nous continuerons d’utiliser le même système pour le moment: 16

(Veuillez répondre à cette question UNIQUEMENT si vous êtes impliqué dans la gestion des incidents signalés.) À quelle fréquence informez-vous les plaignants des résultats des rapports de signalement qu’ils ont établis, ou dans lesquels ils sont impliqués ?

(32 répondants)

  • Toujours: 14
  • Fréquemment: 7
  • Parfois: 6
  • Rarement: 3
  • Jamais: 2

Some Affiliates do not have a local code of conduct. When asked about the references upon which reported conflicts and inappropriate behavior are investigated and solved the answers vary depending on the dimension of the affiliate. Some of these have a local code of conduct or have adopted already existing ones like the mediawiki CoC, some have bylaws, some have policies about events and would refer to Wikipedia behavioural policies if needed, smaller groups would refer to “common” sense or report to their leaders or coordinators.

Impact de l'CdCU

Status of local policies
1. Dans quelle mesure pensez-vous que l'application du nouveau CdCU risque d’entrer en conflit avec les règlements existants ou le CdC local de votre entité affiliée? (1=faible, 5=élevé) ,
2. Dans quelle mesure pensez-vous que votre entité affiliée aurait besoin d’aide pour mettre en œuvre le nouveau CdCU, en particulier en l’absence de règlements locaux et de codes internes? (1=Pas d'aide, 5=beaucoup d'aide)

Si vous avez indiqué que votre entité affiliée aurait besoin d'aide pour mettre en œuvre le CdCU, quel type d'aide serait nécessaire ?

  • Reporting system and training to explain how the reporting system can be used.
  • Casebook and best practices, training, workshops in local language.
  • If we need to draft bylaws and such, we would need help with that.
  • We currently just refer to the Friendly Space Policy.
  • Knowing the policies and what other Chapters do would be helpful.

À votre avis‚ parmi ce qui est proposé ci-dessous, qu’est-ce que votre entité affiliée doit faire ou avoir pour mettre en œuvre efficacement le CdCU?

  • Directives écrites et accessibles: 99
  • Formation des membres affiliés quant à la manière de signaler les incidents: 95
  • Conseils aux membres du personnel sur la manière de mettre en œuvre le CdCU chaque fois qu’un nouveau Conseil d’administration est élu ou qu’un nouveau membre du personnel est embauché: 75
  • Rappels périodiques de l’existence et de l’importance du CdCU, ainsi que de la manière de l’utiliser: 79
  • Examen périodique de la manière dont le CdCU est utilisé pour régir les comportements dans l’ensemble de votre entité affiliée: 75

Quels sont les moyens que les dirigeants d’entités affiliées peuvent utiliser pour sensibiliser leurs membres au CdCU?

  • Communication before offline events, adding it to the invite to events, in the website, in ML
  • Through social media, small video or flyers and the different communication forms used by Affiliates.
  • Important to inform new members and to have clear and accessible guidelines.

(Veuillez répondre UNIQUEMENT si vous êtes un membre du Conseil d’administration ou un membre du personnel d’une entité affiliée) Quelles autres mesures les dirigeants des entités affiliées peuvent-ils prendre pour assurer une mise en œuvre plus fluide du CdCU?

  • Support the UCoC, training on UCoC matters for volunteers, create clear communication within the affiliate members about UCoC issues.
  • Organize training for staff and volunteers, dissemination, awareness, periodical reminders and surveys, update internal codes and guidelines.
  • Supporting victims.

Comment la conformité de votre entité affiliée au CdCU pourrait-elle être mesurée et surveillée?

  • Anonymous surveys (once per year) to our members and volunteers
  • Periodic reports about the related issues to the UCOC like complaints and their resolution.
  • Create a monitoring committee from the Trust and Safety staff in Wikimedia Foundation for all the Affiliates and ask for reports regularly
  • Members should also be able to submit complaints about the local Affiliates' handling of the situation to a global body overseeing the implementation of the UCoC.
  • There should be a community member responsible for UCoC.
  • Analysis of willingness to accept investigations, outcome of investigations, number of reports, etc.

[...] pay attention to its follow-up and educate the community that the goal is not to suppress freedom of expression, but to work within a framework of general global behavior, protect all people, support all ideas, and prevent bullying or mockery.

— Survey response

Dedicated staff who are tasked with this. Aided by external reviews every couple of years, like an audit.

— Survey response

As concerns the contribution of UCoC to the long term sustainability of the affiliate, despite some criticism about the process generally the respondents think that UCoC and the awareness about its goals will have a positive impact on activities, retention and the working environment. The effectiveness of this will depend on the implementation and enforcement and on how much the process is seen as "coming from above".

It should help in keeping a friendly environment (which is a good thing), but I do not expect it to greatly aid in the sustainability of the affiliate. Sustainability requires much more than a friendly environment.

— Survey response

Références

Following are some references that some Affiliates provided during the discussions:

Considerations for the future

  • In a discussion with a user group, a participant objected that the discussion took place in another language than the group’s official language: “I would just like to add something: if the topic of the meeting is really important for the Wikimedia Foundation, I think the first thing to do would be to allow this exchange to take place in the language of the participants of the group.”
  • Objections to using Google forms came from many groups and individuals; even Qualtrics was not a solution for them; data of people are usually imposed using these tools. At the same time, Wikimedia Foundation is not encouraged to use open source platforms because they host data externally and that's not the solution. Suggestions are that Wikimedia Foundation should have worked on tools and platforms since people had complained about it a long time ago, especially if they have money to do it. The change cannot be done on a day, but participants would accept it if the foundation shared a real plan with the groups that includes dates.
  • Many responses we received included complains about the timing of the consultation process as it conflicts with too many other open discussions; this processes intersected with the discussions about the outcomes of the Movement Strategy Recommendations, discussions about the board governance and elections; “we can consider throwing off some of the issues to trigger people on thinking about more focused items”; In addition, the process started with other annual projects such as WikiGap, Women’s International month, etc. in which many groups participate. Not only that, but our processes were confusing to some groups/individuals; for example, we sent the “Targets of Harassment” survey to Affiliates at the same time they were requested to take the Affiliates consultations survey.
  • Increase direct communication with the smaller groups. This increases engagement and encourages them to provide input and feedback. This has been raised previously in phase 1 and another time in phase two, and both comments came from African user groups, who expressed their excitement about someone from the foundation consulting with them and asking for their opinions.
  • AffCom: Should Affcom be more involved in facilitating some communications specifically with Affiliates that don’t respond?