Universal Code of Conduct/Affiliates consultation/Report/nl

From Meta, a Wikimedia project coordination wiki
This page is a translated version of the page Universal Code of Conduct/Affiliates consultation/Report and the translation is 44% complete.
Universal Code of Conduct

In februari 2021 werd na goedkeuring door het bestuur van de Wikimedia Foundation een Universele Gedragscode (UCoC) aangenomen die betrekking heeft op alle bewegingsruimten, inclusief wiki-projecten, medewerkers van de Foundation en aangesloten leden; zowel online als offline. Het stelt een minimale set van verwacht en onaanvaardbaar gedrag vast waarop belanghebbenden van de beweging kunnen voortbouwen bij het vaststellen van hun eigen beleid en richtlijnen, maar waar ze niet onder vallen. Het proces van handhaving en implementatie van de Universele Gedragscode is een belangrijke factor bij het creëren van een veilige, inclusieve omgeving in onze affiliaties en wiki-werkplekken.

In deze fase van het project, dat tot doel heeft duidelijke definities van handhavingstrajecten en rapportageprocessen te creëren, zullen Wikimedia-gemeenschappen en affiliaties van alle groottes, typen en ervaringsachtergronden werden uitgenodigd om deel te nemen aan discussies om hun ideeën, gedachten en zorgen te delen met betrekking tot de implementatie-, rapportage- en handhavingstrajecten van de UCoC.

Over het algemeen zijn de leden van mening dat de Wikimedia Foundation actief moet samenwerken met lokale verenigingen en gebruikersgroepen, en hen moet helpen bij pogingen om gedragsproblemen waar mogelijk lokaal op te lossen; deze samenwerking zou effectief kunnen worden verbeterd door de ontwikkeling en implementatie van een universele gedragscode (UCoC) en het bestaan van regels voor het gedrag en de oplossing van conflicten tussen deelnemers aan de interne reglementen van lokale groepen. Affiliaties erkennen ook dat het onmogelijk is om uit te sluiten dat er verschillende soorten problemen ontstaan tijdens activiteiten waarbij veel deelnemers betrokken zijn, wat een uitdaging vormt voor het handhavingsproces. Tijdens de besprekingen werden veel goede ideeën geopperd en er werden veel voorstellen ontvangen van verschillende affiliaties na interne bespreking van de belangrijkste doelstellingen van het raadplegingsproces.

Met waardering voor de gastheren is het vermeldenswaard dat het UCoC-projectteam de kans kreeg om het raadplegingsproces en andere gerelateerde activiteiten te presenteren tijdens enkele wereldwijde Affiliatie-evenementen, waaronder reguliere ESAP-bijeenkomsten en maandelijkse SWAN-bijeenkomsten.

Proces

In maart en april 2021 werden uitnodigingen verstuurd naar alle affiliaties, te beginnen met de affiliaties die interesse toonden in de "Veiligheids- en inclusievereiste" van de Movement Strategie, en eindigend met de nieuw erkende affiliaties. Veel affiliaties, gericht op goed gestructureerde en ervaren affiliaties, werden uitgenodigd om open discussies te leiden. Er werden vergaderingen gehouden met 23 affiliaties van verschillende grootte; meestal woonden de directeuren ervan de vergaderingen bij, maar sommigen nodigden ook verschillende leden uit om deel te nemen.

Daarnaast werd een enquête verstuurd naar de meeste affiliaties in 8 talen, hetzij naar de contactpersonen, directeuren, mailinglijsten, metapagina, of via een officieel communicatiekanaal. Het totale aantal respondenten was 147 uit 24 verschillende verenigingen/thematische organisaties en 27 verschillende gebruikersgroepen. Zowel de discussies als de enquête waren nuttige hulpmiddelen om feedback van deelnemers te krijgen; Affiliaties deelden hun ervaring met het implementeren van lokale procedures, beleid en code. Het is van groot belang om meer te weten te komen over de ervaringen van de affiliaties en de mate waarin hun ervaring kan worden toegepast en gerepliceerd door middel van het opkomende UCoC-handhavingsoverzicht. Sommige affiliaties voerden interne discussies en namen de UCoC-tekst op in de agenda's van hun reguliere officiële vergaderingen en gaven collectieve feedback.

Huidige situatie

Elke affiliatie zou een beleid voor conflictoplossing moeten hebben. De meeste van de geraadpleegden geven aan dat ze lokale procedures, statuten en beleid hebben. Sommige weten echter niet of iedereen ervan op de hoogte is en precies weet hoe ze ze moeten gebruiken.

Interne processen

Gevestigde verenigingen legden uit dat ze zelden klachten ontvangen over onaanvaardbaar gedrag, of dat er in ieder geval incidenten plaatsvonden maar niet werden gemeld. De huidige procedures zijn dus vaak niet getest en affiliaties hebben meer duidelijkheid nodig over hoe om te gaan met problemen. Kwesties zijn onder meer aan wie incidenten intern moeten worden gemeld en wat de vereisten zijn in termen van bredere escalatie. Aan de andere kant legden drie affiliaties uit dat ze een lokale gedragscode hadden ontwikkeld en gehandhaafd nadat ze te maken hadden gehad met interne interpersoonlijke conflicten en problemen. Sommige affiliaties meldden dat ze niet erg tevreden zijn met het beleid dat ze hebben. Ze vinden dat ze de regels moeten aanscherpen. De processen moeten worden geformaliseerd voor het geval ze bijvoorbeeld voor een rechtbank naar deze statuten en beleidsregels moeten verwijzen. Anderen moeten voor passende vertalingen zorgen omdat ze meestal problemen ondervinden bij de communicatie in andere talen.

Rol in online conflicten

Affiliaties zijn ook van mening dat misbruik of intimidatie aanzienlijk minder waarschijnlijk is tijdens een evenement (persoonlijk of online) in vergelijking met asynchrone online communicatie of projecten. Affiliaties zouden er niet bij betrokken moeten zijn, laat staan dat ze de "rechter en jury" zouden moeten zijn in on-wiki situaties. Het beslechten van dergelijke conflicten is de verantwoordelijkheid, en vaak de last, van de bestuurders, die meestal meer uitdagingen ondervinden bij het beheersen van gedrag en het implementeren van lokaal beleid. In sommige gevallen verwijzen deelnemers echter naar aangesloten leiders om te rapporteren of advies in te winnen over gevallen die online plaatsvinden, zoals verbieden of blokkeren. Affiliaties proberen meestal te voorkomen dat ze zich bemoeien met inhoudelijke kwesties. Affiliaties die zich richten op online content hebben niet de noodzaak ingezien om enige vorm van code te maken, omdat het meestal online activiteiten zijn. Op een gegeven moment werd de overlegpagina van de Affiliatie het anti-intimidatiemiddel en de ruimte voor het melden van gevallen.

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.

Challenges

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.

Special cases

  • 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.

Requested support from 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.

Survey

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.

Wie reageerde er?
1. Wat is uw rol in de affiliatie? 2. Hoe lang ben je al betrokken bij deze Wikimedia-organisatie?

Lokaal beleid en rapportagesysteem

Status van het lokaal beleid
1. Denk je dat jouw Wikimedia-organisatie een lokale gedragscode, regels of voldoende beleidslijnen heeft en volgt om conflicten of ongepast gedrag tussen de leden te voorkomen en/of aan te pakken? 2. Geef aan in welke mate het beleid/de reglementen/de statuten van jouw Wikimedia-organisatie volgens jou afdoende zijn om slecht gedrag tegen bijdragers/deelnemers/organisatoren of personeelsleden te voorkomen bij alle evenementen die de organisatie organiseert, zoals conferenties, bijeenkomsten, vergaderingen, workshops (1=Helemaal niet toereikend, 5=Volledig toereikend)

Op de vraag naar de "mate van effectiviteit van het lokale beleid" bij het voorkomen van slecht gedrag, is de gemiddelde waarde 3,65 en varieert deze niet afhankelijk van de duur van de betrokkenheid bij de aangeslotene, maar kijkend naar de waarden voor de verschillende rollen is het gemiddelde vertrouwen in het lokale beleid iets lager voor bestuursleden (gem=3,49).

Status van het lokale rapportagesysteem

1. Beschikt jouw Wikimedia-organisatie over een duidelijk meldingssysteem dat alle leden probleemloos kunnen gebruiken?

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.

Hoe kwam je erachter dat je Wikimedia-organisatie een meldingssysteem heeft?

Hoe kwam je erachter dat je Wikimedia-organisatie een meldingssysteem heeft?
Methode Respondenten
Zelfstudie via documentatie op wiki’s 41
Getoond door een leider of medewerker van een aangesloten organisatie 37
Getoond door een lid van de gemeenschap 21
Andere gemelde hulpmiddelen waren e-mails die de affiliatie in sommige gevallen stuurde tijdens de toetredingsprocedure, conferenties of evenementen buiten de wiki.

Behalve dat we zeggen: "Als je problemen hebt, vraag het aan persoon X", hebben we geen problemen.

— Reactie op enquête

Ik ben er niet zeker van dat er binnen de vereniging een goed rapportagesysteem bestaat. Op onze pagina over de Gedragscode staat slechts één zin: "In geval van overtredingen, verwijzen wij naar deze Gedragscode door een openbaar of privé bericht te sturen", maar het geeft niet aan waar het bericht heen moet worden gestuurd.

— Reactie op de enquête

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:

Wie moet volgens jou de details en de afhandeling van een melding kunnen zien? Kies alles wat van toepassing is

  • Rechtstreeks betrokken partijen: 93
  • Directeuren, bestuursleden en medewerkers van aangesloten organisaties: 89
  • Wikimedia Foundation: 70
  • Algemeen publiek, via de officiële portals van de Wikimedia-organisatie: 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.

— Reactie op enquête

In welke omstandigheden vind je dat een melding vertrouwelijk moet zijn? Vink alles aan wat van toepassing is.

  • Meldingen met informatie die zou kunnen leiden tot de identificatie van betrokkenen: 64
  • Alle meldingen: 51
  • Meldingen met betrekking tot persoonlijke mishandeling: 55
  • Meldingen met betrekking tot langdurige overtreders: 20
  • Geen (alle meldingen moeten openbaar zijn): 15

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

— Reactie op enquête
Status of reporting system

Hoe tevreden l ben je met het meldingssysteem en -proces dat in jouw Wikimedia-organisatie is opgesteld en wordt gevolgd? Kies alle opties die van toepassing zijn.

Legend

  1. Er zijn voldoende middelen in mijn Wikimedia-organisatie om klachten te onderzoeken en op te volgen
  2. De medewerkers die verantwoordelijk zijn voor het afhandelen van klachten zijn goed opgeleid en ervaren
  3. Er zijn voldoende richtlijnen en aanwijzingen om leden te begeleiden bij het indienen van een melding.
  4. Het onderzoeksproces is transparant
  5. Tijdens het onderzoeksproces is er goede communicatie met de klager(s) en met de aangeklaagde(n).
  6. Tijdens het onderzoeksproces worden alle partijen (d.w.z. klagers en aangeklaagden) met waardigheid en respect behandeld.
  7. Zaken worden meestal tijdig afgehandeld.
  8. Klagers voelen zich meestal veilig en beschermd
  9. Klagers kunnen navraag doen naar de klachten om er zeker van te zijn dat er een onderzoek wordt ingesteld.

Om welke redenen zouden leden ongepast of onethisch gedrag in jouw Wikimedia-organisatie niet melden? Selecteer alles wat van toepassing is.

  • Er is geen duidelijk protocol of proces. Ze weten niet wat ze moeten doen.: 62
  • Gebrek aan ondersteuning door het management of bestuur van de aangesloten organisatie en/of andere leden: 22
  • Gebrek aan vertrouwen dat gemelde problemen eerlijk worden aangepakt Angst voor vergelding: 48
  • Angst voor vergelding: 50
  • Bezorgdheid over hun reputatie; ze willen niet worden beschouwd als iemand die met problemen: 61
  • Bezorgdheid over de reputatie van de Wikimedia-organisatie: 27
  • Het meldingsproces is niet transparant; daarom wordt het niet vertrouwd: 22
  • Ze weten zelf hoe ze op de juiste manier moeten reageren als zijzelf of een collega betrokken zijn bij een ongewenst voorval , zonder zich te hoeven wenden tot het management of het bestuur: 27

(Beantwoord deze vraag als je een bestuurslid of een medewerker bent. Als je geen bestuurslid of medewerker bent, kun je de vraag OVERSLAAN.) Met welke van de volgende uitspraken ben je het EENS met betrekking tot de gedragsregels bij jouw Wikimedia-organisatie? Kies alles wat van toepassing is.

  • Onze lokale gedragscode kan door alle leden worden bekeken: 44
  • Onze lokale gedragscode en statuten worden altijd geraadpleegd (als belangrijkste referentie) bij het onpartijdig en objectief onderzoeken van klachten m.b.t gedrag: 31
  • Klagers kunnen navraag doen over de klachten die ze melden en om updates vragen: 34
  • De lokale gedragscode en statuten worden regelmatig herzien en waar nodig bijgewerkt: 23
  • Onze interne regels zijn flexibel, zodat we wijzigingen en aanpassingen kunnen aanbrengen en eventuele tekortkomingen kunnen aanpakken: 28
  • De universele gedragscode zal niet in strijd zijn met onze lokale gedragscode, maar zal deze aanvullen en versterken: 42
  • Als bestuurders/medewerkers van de Wikimedia-organisatie geven wij duidelijkheid over de eisen en verwachtingen omtrent vertrouwelijkheid, en wat de klager kan verwachten tijdens het onderzoeksproces: 22
  • Als bestuurders/medewerkers van de Wikimedia-organisatie blijven wij bereid om te luisteren als klagers niet tevreden zijn over de resultaten: 31
  • Als bestuurders/medewerkers van de Wikimedia-organisatie houden wij voor elke zaak of klacht een administratie bij van de details en oplossingen: 26
  • De uit de onderzoeken geleerde lessen worden gecommuniceerd aan medewerkers en leden: 20
  • Als bestuurders/medewerkers van de aangesloten organisatie zijn wij van mening dat de veiligheid van de klager van groot belang is en een topprioriteit: 39
  • Als bestuurders/medewerkers van de Wikimedia-organisatie evalueren we onze meldingssystemen meestal en geven bekendheid aan onze meldingssystemen om te garanderen dat klagers incidenten en slecht gedrag op een veilige manier melden: 18
  • Als bestuurders/medewerkers van de Wikimedia-organisatie zijn wij tevreden over ons huidige meldingsproces. We zullen voorlopig hetzelfde systeem blijven gebruiken: 16

Beantwoord deze vraag ALLEEN als je betrokken bent bij het afhandelen van gemelde incidenten. Hoe vaak informeer je de klagers over de uitkomst van de meldingen die ze hebben gedaan of waarbij ze betrokken zijn?

(32 respondents)

  • Altijd: 14
  • Vaak: 7
  • Soms: 6
  • Zelden: 3
  • Nooit: 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 of the UCoC

Status of local policies
1. In hoeverre denk je dat de handhaving van de nieuwe universele gedragscode in strijd zou kunnen zijn met de bestaande statuten of lokale gedragscode van jouw Wikimedia-organisatie? (1=Lage waarschijnlijkheid, 5=Zeer waarschijnlijk)

,

2. Hoeveel hulp denk je dat jouw Wikimedia-organisatie nodig zou hebben om de nieuwe universele gedragscode te implementeren, vooral als er geen lokale statuten en interne gedragscodes zijn? (1=Helemaal geen hulp, 5=Veel hulp)

Op welke manieren kunnen leiders van jouw organisatie helpen om het bewustzijn over de universele gedragscode onder de leden te vergroten?

  • 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.

Welke van de volgende zaken moet jouw Wikimedia-organisatie volgens jou doen of hebben om de universele gedragscode effectief te implementeren?

  • Schriftelijke, toegankelijke richtlijnen: 99
  • Training voor leden van de organisatie over het melden van incidenten: 95
  • Begeleiding voor medewerkers bij het implementeren van de universele gedragscode telkens wanneer er een nieuw bestuur wordt gekozen of wanneer nieuw personeel wordt aangenomen: 75
  • Periodieke herinneringen aan het bestaan en het belang van de universele gedragscode, evenals hoe deze te gebruiken: 79
  • Periodieke evaluatie hoe de universele gedragscode wordt gebruikt om het gedrag binnen de gehele organisatie te beheren: 75

Op welke manieren kunnen leiders van jouw organisatie helpen om het bewustzijn over de universele gedragscode onder de leden te vergroten?

  • 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.

(Geef ALLEEN antwoord als je lid bent van het bestuur of een medewerker bent van een aangesloten organisatie): Welke extra stappen kunnen leiders van de aangesloten organisatie nemen om een soepelere implementatie van de universele gedragscode te verzekeren?

  • 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.

Hoe kan de naleving van de universele gedragscode in jouw Wikimedia organisatie worden gemeten en gecontroleerd?

  • 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.

— Reactie op enquête

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

— Reactie op enquête

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.

— Reactie op enquête

References

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?

{{|Universal Code of Conduct/Navbox}}