鱼油功效和作用是什么| 冲动是什么意思| 长期便秘吃什么药效果最好| 胃不消化吃什么药| 维生素b6有什么作用| 摩羯座哭了代表什么| 桃花像什么| 大林木命适合做什么行业| 什么是口播| 拉屎是绿色的是什么原因| gigi是什么意思| 蜜獾为什么什么都不怕| 中指麻木是什么原因引起的| 美人是什么生肖| 狂犬疫苗什么时候打有效| 沙棘有什么作用| 朗姆是什么| 2018属什么生肖| 11月出生是什么星座| 85年属牛是什么命| 右耳朵发烫是什么征兆| 儿童感冒挂什么科| 棱是什么| 腰椎间盘突出吃什么好| 黄墙绿地的作用是什么| 78年的马是什么命| 卧蚕和眼袋有什么区别| mews评分是什么意思| 被强奸是什么感觉| 总是心慌是什么原因| 小孩晚上睡不着是什么原因| 新疆是什么地貌| 1223是什么星座| 小孩咳嗽吃什么药好| 什么书比较好| 双侧乳腺小叶增生是什么意思| 特需门诊和专家门诊有什么区别| 直肠炎吃什么药| 清华大学是什么级别| 梗塞是什么意思| atp是什么| 耳火念什么| 男女接吻有什么好处| 骨关节疼痛什么原因| 际遇是什么意思| 十月七号什么星座| 疤痕痒是什么原因| 不来事是什么原因| 膜性肾病什么意思| 和可以组什么词| 急性肠胃炎吃什么消炎药| 阳春白雪是什么意思| 处女男喜欢什么样的女生| 梦见吃排骨是什么意思| 六味地黄丸什么牌子好| 控是什么意思| 晚上吃什么减肥效果最好| 循序渐进什么意思| 尿床去医院挂什么科| 大豆是指什么豆| 肠系膜多发淋巴结是什么意思| 什么力竭| 思密达什么意思| 木字五行属什么| 高压氧治疗有什么作用| 牙龈肿痛吃什么药最好| 出现的反义词是什么| 用什么方法治牙疼| 西安有什么| 调经止带是什么意思| lyocell是什么面料| 魏丑夫和芈月什么关系| 产厄是什么意思| 上市公司是什么意思| 消化酶缺乏是什么症状| 夸父为什么要追赶太阳| 什么节日吃汤圆| 吃什么减肥最快| 甲状腺功能亢进症是什么病| 高贵的什么| 西布曲明是什么| 嘴巴周围长痘痘是什么原因| elsa是什么意思| 花是植物的什么器官| 11.11什么星座| 丝瓜络是什么| 发热吃什么药| 麻小是什么意思| 知世故而不世故是什么意思| 心动过速是什么原因| 排卵期什么症状和反应| 大便拉不出来是什么原因| 低血压适合吃什么食物| 磕碜是什么意思| apc是什么牌子| 锁阳是什么| 角加斗念什么| 为什么叫印度阿三| 双侧附睾头囊肿是什么意思| 犹太是什么意思| minute是什么意思| 属猪的本命佛是什么佛| 日行一善是什么意思| 东方明珠什么时候亮灯| yuki是什么意思| 什么是鸡冠油| 牛肉馅配什么菜包饺子好吃| 牛瓦沟是什么部位| spank是什么意思| 滑丝是什么意思| 强硬是什么意思| 大便发绿色是什么原因| 来月经拉肚子是什么原因| 背上长痘是什么原因| 什么动物是爸爸生的| 什么是春天的什么| 585是什么金| 大学休学1年有什么影响| 腰疼做什么检查| 鸟屎掉身上有什么预兆| 什么的雪花| 鳞状上皮细胞是什么意思| 十月23日是什么星座| 手脚冰凉是什么原因| 胆结石吃什么药可以化掉结石| 女人肾虚吃什么好得快| 肛门瘙痒看什么科| 洛索洛芬钠片和布洛芬有什么区别| 捡漏什么意思| 精神伴侣是什么意思| 打嗝多是什么原因| 圣诞节是什么时候| 六月十七是什么星座| 鑫字属于五行属什么| 什么牌子的充电宝好| 什么是情商| 为非作歹是什么意思| 蹲不下去是什么原因| 减肥能吃什么零食| 75年属什么生肖| 梦见打老婆是什么预兆| 海参是什么动物| 心识是什么意思| mm表示什么| 月经一个月来两次是什么原因| 哈喇子是什么意思| 什么一梦| 低密度是什么意思| 金戈铁马是什么生肖| 异地结婚登记需要什么证件| 你是谁为了谁是什么歌| 五福是什么| 并驾齐驱什么意思| 缩阳是什么意思| 宜余事勿取是什么意思| 西方属于五行属什么| 8月份是什么星座| 福德是什么意思| 什么是易经| 胎动在肚脐周围是什么胎位| 你在说什么用英语怎么说| 滑精是什么原因| 短杆菌是什么意思| 破屋坏垣适合干什么| 附件炎吃什么药好| 脾肾阳虚吃什么中成药最好| 什么都不放的冬瓜清汤| 证过二是什么意思| 中国黄金为什么便宜| 梦见吃豆腐是什么意思| hazzys是什么牌子价格| 挺舌反应是什么| 脂膜炎是什么病| 天下乌鸦一般黑是什么意思| 营养性贫血是什么意思| 拉肚子应该挂什么科| pagani是什么车| 释然什么意思| 骶1隐裂是什么意思| 修造是什么意思| 体检什么时候出结果| 便秘吃什么药见效快| 06年属什么| 八大碗都有什么菜| 今天生肖冲什么| 喝黄瓜汁有什么好处| 最亮的星星是什么星| 和女生聊天聊什么| 晚上8点是什么时辰| 北京属于什么气候| 邮箱地址填什么| 小便痒痒是什么原因女| 尿床去医院挂什么科| 电瓶车什么牌子好| 看胆囊挂什么科| aa什么意思| 双脚发热是什么原因| aigner是什么牌子| 什么是强直性脊柱炎| 幼儿急疹是什么原因引起的| 芹菜煮水喝有什么功效| 伤口增生是什么原因造成的| 碱性磷酸酶是什么意思| 12月份是什么星座| 血管炎是什么病| 双侧骶髂关节致密性骨炎是什么病| 蹭饭是什么意思| 肛门是什么意思| 过敏了吃什么药好| 是什么日子| 肠胃不好吃什么药效果好| 胃造影和胃镜有什么区别| 乳头出血是什么原因| 为什么兔子的眼睛是红色的| 保肝护肝吃什么| 什么病人要补氯化钾呢| 虎的本命佛是什么佛| 日加个成念什么| 转音是什么意思| 平板是什么| 水瓶女和什么星座最配| 慢性肾炎是什么原因引起的| 什么是甲醛| 转氨酶高说明什么| 吃完龙虾不能吃什么| 补铁吃什么| 女方什么人不能送亲| 做亲子鉴定需要什么| 白内障什么症状| 什么什么为什么| 脸上长红色的痘痘是什么原因| ear是什么意思| 当所有的人离开我的时候是什么歌| 佛法无边是什么意思| 什么是嘌呤食物| 坐骨神经有什么症状| 奢望是什么意思| 男人阴虱用什么药| 白细胞是什么| 气胸吃什么药好得快| 甲鱼和什么食物相克| 白果有什么功效与作用| jb什么意思| 学子是什么意思| 万事如意是什么生肖| 净身是什么意思| 验孕棒两条杠什么意思| 左侧附件区囊性占位是什么意思| 脚底疼痛是什么原因| 未时属什么生肖| 羡慕不来是什么意思| 一切唯心造是什么意思| 红色爱心是什么牌子| 趣味是什么意思| zoom 是什么意思| facebook什么意思| hm平方是什么单位| 白带什么颜色| 容易紧张是什么原因| 硫磺有什么作用| 不寐病是什么意思| jomalone是什么牌子| 突然晕倒是什么原因造成的| 龋齿挂什么科| 百度Jump to content

告别家里电线乱插乱放 全屋开关插座布置攻略

From Wikimedia Foundation Governance Wiki
Wikimedia Foundation Universal Code of Conduct

1. UCoC Enforcement Guidelines

These Enforcement Guidelines describe how the community and Wikimedia Foundation achieve the goals of the Universal Code of Conduct (UCoC). This includes, among other topics: promoting understanding of the UCoC, engaging in proactive work to prevent violations, developing principles for responsive work to UCoC violations, and supporting local enforcement structures.

The UCoC applies to all online and offline Wikimedia spaces. Therefore, enforcing the UCoC is a shared responsibility. In line with the movement principle of decentralisation, the UCoC should be enforced at the most relevant local level possible.

The Enforcement Guidelines provide a framework for the interaction of current and future enforcement structures, seeking to create the groundwork for an equitable and consistent implementation of the UCoC.

1.1 Translations of the UCoC Enforcement Guidelines

The original version of the UCoC Enforcement Guidelines is in English. It is translated into various languages used on Wikimedia projects. The Wikimedia Foundation makes its best efforts to have accurate translations. If any difference arises in the meaning between the English version and a translation, decisions by the U4C must be based on the English version.

1.2 Review of the UCoC Enforcement Guidelines

The Universal Code of Conduct Coordinating Committee leads annual reviews of the UCoC Enforcement Guidelines.

2. Preventive work

This section aims to provide guidelines for Wikimedia communities and affiliated individuals to be aware of the UCoC, to fully understand and adhere to it. To that end, this section details recommendations for raising awareness of the UCoC, handling translations of the UCoC, and promoting voluntary adherence to the UCoC where appropriate or necessary.

2.1 Notification and confirmation of the UCoC

The UCoC applies to everyone who interacts and contributes to Wikimedia projects. It also applies to official in-person events, and related spaces hosted on third party platforms as a baseline of behavior for collaboration on Wikimedia projects worldwide.

The UCoC is part of the Wikimedia Terms of Use.

Additionally, the following individuals need to confirm their adherence to the UCoC:

  • All Wikimedia Foundation staff and contractors, Board of Trustees members, Wikimedia affiliate board members and staff;
  • Any representative of a Wikimedia affiliate or aspiring Wikimedia affiliate (such as, but not limited to: an individual, or group of individuals who is seeking to promote and/or collaborate a Wikimedia sponsored event, group, study, either on or off-wiki in a research setting); and
  • Any individual who wants to use the Wikimedia Foundation trademark in an event such as, but not limited to: events branded with Wikimedia trademarks (such as by including them in the event's title) and representation of the Wikimedia organization, community, or project at an event (such as, but not limited to, a presenter or a booth operator).

2.1.1 Promoting UCoC awareness

In order to improve awareness, a link to the UCoC will be accessible on or at:

  • User and event registration pages;
  • Footers on Wikimedia projects and edit confirmation pages for logged-out users (where appropriate and technically possible);
  • Footers on the websites of recognized affiliates and user groups;
  • Prominently communicated at in-person, remote, and hybrid events; and
  • Anywhere else deemed appropriate by local projects, affiliates, user groups, and event organizers

2.2 Recommendations for UCoC training

The U4C, with support from the Wikimedia Foundation, develops and implements training to provide a common understanding of the UCoC and skills for its implementation. Relevant stakeholders must be consulted in the development of training, including, but not limited to: Affiliates, the Affiliations Committee, Arbitration Committees, Stewards and other Advanced Rights Holders, T&S and legal, and others as it deems beneficial to providing a complete view of the UCoC.

These trainings are for people who want to be part of UCoC enforcement processes, or those who want to be informed about the UCoC.

The training will be set up in independent modules covering general information, identification of violations and support, and complex cases and appeals. The U4C is responsible for maintaining and updating the training modules as needed.

Training modules will be available in different formats and on different platforms for easy access. Local communities and Wikimedia Affiliates who want to provide training at their community level will get financial support from the Wikimedia Foundation to implement training. This includes support for translations.

Participants who complete a module must have the option of having their completion publicly acknowledged.

The following sets of trainings are proposed:

Module A - Orientation (UCoC - General)

  • Help to ensure a common understanding of the UCoC and its implementation
  • Explain concisely what the UCoC is and its expected enforcement, as well as what tools are available to help report violations

Module B - Identification and Reporting (UCoC - Violations)

  • Give people the ability to identify UCoC violations, understand reporting processes and learn how to use reporting tools
  • Detail the type of violation, how to identify reportable instances in their local context, how and where to make reports, and optimal handling of cases within UCoC processes
  • Training will also focus on specific parts of the UCoC, such as harassment and abuses of power (as required)

Modules C - Complex cases, Appeals (UCoC - Multiple Violations, Appeals)

  • These modules are a prerequisite to joining the U4C, and are recommended for prospective U4C applicants and advanced rights holders
  • This module should cover two specific topics:
    • C1 - Handling complex cases (UCoC - Multiple Violations): Cover cross-wiki cases, long term harassment, identifying credibility of threats, effective and sensitive communication, and protecting the safety of victims and other vulnerable people
    • C2 - Handling appeals, closing cases (UCoC - Appeals): Cover handling UCoC appeals
  • These modules will be instructor-led and tailored trainings, provided to U4C members and applicants, and community-elected functionaries who have signed the Access to Nonpublic Personal Data Policy
  • When possible the materials for these instructor-led trainings, such as individual modules, slides, questions, etc., will be publicly available

3. Responsive work

This section aims to provide guidelines and principles for processing reports of UCoC violations, and recommendations for local enforcement structures dealing with UCoC violations. To that end, this section will detail important principles for processing reports, recommendations for the creation of a reporting tool, suggested enforcement for different levels of violations, and recommendations for local enforcement structures.

3.1 Principles for filing and processing of UCoC violations

The following principles are standards for reporting systems across the Movement.

Reports:

  • Reporting of UCoC violations should be possible by the target of the violation, as well as by uninvolved third parties that observed the incident
  • Reports shall be capable of covering UCoC violations, whether they happen online, offline, in a space hosted by a third party, or a mix of spaces
  • It must be possible for reports to be made publicly or with varying degrees of privacy
  • Credibility and verifiability of accusations will be investigated thoroughly to properly assess risk and legitimacy
  • Users who continually send bad faith or unjustified reports risk facing loss of reporting privileges
  • Accused individuals shall have access to the particulars of the alleged violation made against them unless such access would risk danger or likely harm to the reporter or others' safety
  • Where possible and necessary, the Wikimedia Foundation will provide translation resources for reports

Processing violations:

  • Outcomes shall be proportional to the severity of the violation
  • Cases shall be judged in an informed way, which makes use of context, in alignment with the principles of the UCoC
  • Cases shall be resolved within a consistent time frame, with timely updates provided to participants if it is prolonged

Transparency:

  • Where possible, the group that processed the UCoC violation will provide a public archive of those cases, while preserving privacy and security in non-public cases
  • The Wikimedia Foundation will publish basic statistics about usage of the central reporting tool proposed in section 3.2, while honoring the principles of minimal data collection and respect for privacy.
    • Other groups that process UCoC violations are encouraged to provide basic statistics about UCoC violations and reporting as they are able, while honoring the principles of minimal data collection and respect for privacy.

3.1.1 Providing resources for processing cases

Enforcement of the UCoC by local governance structures is supported in multiple ways. Communities choose from different mechanisms or approaches based on several factors such as: the capacity of their enforcement structures, approach to governance, and community preferences. Some of these approaches can include:

  • An Arbitration Committee (ArbCom) for a specific Wikimedia project
  • An ArbCom shared amongst multiple Wikimedia projects
  • Advanced rights holders enforcing local policies consistent with the UCoC in a decentralized manner
  • Panels of local administrators enforcing policies
  • Local contributors enforcing local policies through community discussion and agreement

Communities handle enforcement through existing means where they do not conflict with the UCoC.

3.1.2 Enforcement by type of violations

This section details a non-complete list of the different types of violations, along with the potential enforcement mechanism pertaining to it.

  • Violations involving threats of any sort of physical violence
    • Handled by the Wikimedia Trust & Safety team
  • Violations involving litigation or legal threats
    • Sent to the Wikimedia Foundation Legal team, or, when appropriate, other professionals who can appropriately evaluate the merit of the threats
  • Violations involving the nonconsensual disclosure of personally identifiable information
    • Generally handled by users with oversight or edit suppression permissions
    • Occasionally handled by Trust & Safety
    • Sent to the Wikimedia Foundation Legal team or, when appropriate, other professionals who can appropriately evaluate the merits of the case if this kind of violation invokes a legal obligation
  • Violations related to affiliate governance
    • Handled by the Affiliations Committee or equivalent body
  • Violations in technical spaces
    • Handled by Technical Code of Conduct Committee
  • Systemic failure to follow the UCoC
    • Handled by U4C
    • Some examples of systemic failure include:
      • Lack of local capacity to enforce the UCoC
      • Consistent local decisions that conflict with the UCoC
      • Refusal to enforce the UCoC
      • Lack of resources or lack of will to address issues
  • On-wiki UCoC violations
    • UCoC violations that happen across multiple wikis: Handled by global sysops and stewards and the bodies that handle single-wiki UCoC violations or handled by the U4C where they do not conflict with these guidelines
    • UCoC violations that happen on a single wiki: Handled by existing enforcement structures according to their existing guidelines, where they do not conflict with these guidelines
      • Simple UCoC violations such as vandalism should be handled by existing enforcement structures through existing means, where they do not conflict with these guidelines
  • Off-wiki violations
    • Handled by the U4C where no local governance structure (e.g. ArbCom) exists, or if the case is referred to them by the enforcement structure that would otherwise be responsible
    • In some cases, it is helpful to report the off-wiki violations to enforcement structures of the relevant off-wiki space. This does not preclude existing local and global enforcement mechanisms from acting on the reports
  • Violations at in-person events and spaces
    • Existing enforcement structures often provide rules of behavior and enforcement in off-wiki spaces. These include friendly space policies and conference rules
    • Enforcement structures handling these cases can refer them to the U4C
    • In instances of events hosted by the Wikimedia Foundation, Trust & Safety provides event policy enforcement

3.2 Recommendations for a reporting tool

A centralized reporting and processing tool for UCoC violations will be developed and maintained by the Wikimedia Foundation. It will be possible to make reports through MediaWiki with this tool. The purpose is to lower the technical barrier for reporting and processing UCoC violations.

Reports should include relevant actionable information or provide a documentation record of the case at hand. The reporting interface should allow the reporter to provide details to whomever is responsible for processing that particular case. This includes information such as, but not limited to:

  • How the reported behavior violates the UCoC
  • Who or what has been harmed by this violation of the UCoC
  • The date and time at which the incident(s), occurred
  • The location(s) of the incident(s)
  • Other information to allow enforcement groups to best handle the matter

The tool should operate under the principles of ease-of-use, privacy and security, flexibility in processing, and transparency.

Individuals charged with enforcing the UCoC are not required to use this tool. They may continue to work with whatever tools they deem appropriate, as long as cases are handled according to the same principles of ease-of-use, privacy and security, flexibility in processing, and transparency.

3.3 Principles and recommendations for enforcement structures

Where possible, existing local enforcement structures have the responsibility of receiving reports of and dealing with UCoC violations, in accordance with the guidelines stated here. To ensure that enforcement of the UCoC remains consistent across the movement, the following baseline principles are applied when handling UCoC violations.

3.3.1 Fairness in process

Enforcement structures must develop and maintain supportive conflict-of-interest policies. These should help admins or others determine when to abstain or disengage from a report when they are closely involved in the issue.

All parties will usually have the opportunity to give their perspective on the issues and evidence, and feedback from others can also be invited to help provide more information, perspective, and context. This may be limited to protect privacy and safety.

3.3.2 Transparency of process

The U4C, in line with its purpose and scope as defined in 4.1, provides documentation on the effectiveness of UCoC enforcement actions and their relation to common violations throughout the movement, supported by the Wikimedia Foundation in conducting this research. The goal of this documentation is to aid enforcement structures in developing best practices for enforcing the UCoC.

Wikimedia projects and affiliates, when possible, shall maintain pages outlining policies and enforcement mechanisms in line with the UCoC policy text. Projects and affiliates with existing guidelines or policies in contradiction to the UCoC policy text should discuss changes to conform with global community standards. Updating or creating new local policies should be done in a way that does not conflict with the UCoC. Projects and affiliates may request advisory opinions from the U4C about potential new policies or guidelines.

For Wikimedia-specific conversations occurring on related space hosted on third party platforms (e.g. Discord, Telegram, etc.), Wikimedia's Terms of Use may not apply. They are covered by that specific website's Terms of Use and conduct policies. Nevertheless, the behavior of Wikimedians on related space hosted on third party platforms can be accepted as evidence in reports of UCoC violations. Wikimedia community members who moderate Wikimedia-related spaces on third party platforms are required to incorporate the UCoC into their policies. The Wikimedia Foundation encourages best practices for third-party platforms that discourage the continuation of on-wiki conflicts to their spaces.

3.3.3 Appeals

An action taken by an individual advanced rights holder will be appealable to a local or shared enforcement structure. Local communities may allow appeals to a different individual advanced rights holder. If no local enforcement structure exists, then an appeal to the U4C is permissible.

Enforcement structures set standards for accepting and considering appeals based on relevant contextual information and mitigating factors. These factors include, but are not limited to: verifiability of the accusations, the length and effect of the sanction, and whether there is a suspicion of abuse of power or other systemic issues, and the likelihood of further violations. The acceptance of an appeal is not guaranteed.

Appeals are not possible against certain decisions made by the Wikimedia Foundation Legal department. However, some Wikimedia Foundation office actions and decisions are reviewable by the Case Review Committee. The limitation, specifically on appeals from office actions and decisions, may not apply in some jurisdictions, if legal requirements differ.

Enforcement structures should seek informed perspectives on cases in order to establish a basis to grant or decline an appeal. Information should be handled sensitively, with care for the privacy of the people involved and the decision-making process.

To achieve this goal, enforcement structures are encouraged to consider different factors when reviewing appeals. These may include, but not be limited to:

  • The severity and harm caused by the violation
  • Prior histories of violations
  • Severity of sanctions being appealed
  • Length of time since the violation
  • Analysis of the violation in contact
  • Suspicions of a possible abuse of power or other systemic issue

4. UCoC Coordinating Committee (U4C)

The Universal Code of Conduct Coordinating Committee (U4C) is a co-equal body with other high-level decision-making bodies (e.g. ArbComs and AffCom). Its purpose is to serve as final recourse in the case of systemic failures by local groups to enforce the UCoC.

4.1 Purpose and scope

The U4C monitors reports of UCoC breaches, and may conduct additional investigations and take actions where appropriate. The U4C will regularly monitor and assess the state of UCoC enforcement. It may suggest suitable changes to UCoC, the UCoC Enforcement Guidelines, and U4C Charter for the Wikimedia Foundation and the community to consider, but may not change these documents on its own. When necessary, the U4C will assist the Wikimedia Foundation in handling cases.

The U4C:

  • Handles complaints and appeals in the circumstances outlined in the Enforcement Guidelines
  • Performs any investigations necessary to resolve said complaints and appeals
  • Provide resources for communities on UCoC best practices, such as mandatory training material and other resources as needed
  • Provides a final interpretation of the UCoC Enforcement Guidelines and the UCoC if the need arises, in collaboration with community members and enforcement structures
  • Monitors and assesses the effectiveness of UCoC enforcement, and provides recommendations for improvement

The U4C will not take cases that do not primarily involve violations of the UCoC, or its enforcement. The U4C's responsibilities are explained in the context of other enforcement structures in 3.1.2.

4.2 Selection, membership, and roles

Annual elections, organized by the global community, will select up to 16 voting members.

In exceptional circumstances, the U4C may call interim elections, if it determines that resignations or inactivity have created an immediate need for additional members. Elections will be in a format similar to that of the regular annual elections.

The Wikimedia Foundation may appoint up to two non-voting members to the U4C and will provide support staff as desired and appropriate.

4.3 Policy and precedent

The U4C does not create new policy and may not amend or change the UCoC. The U4C instead applies and enforces the UCoC as defined by its scope.

As community policies, guidelines and norms evolve over time, previous decisions will be taken into account only to the extent that they remain relevant in the current context.

5. Glossary

Administrator (sysop or admin)
See definition on Meta-Wiki.

Advanced rights holder
user who holds administrative rights above typical editing permissions, and is generally elected through community processes or appointed by Arbitration Committees. This includes, as a non-exhaustive list: local sysops / administrators, functionaries, global sysops, stewards.

Affiliations Committee or Affcom
See definition on Meta-Wiki.

Arbitration Committee or ArbCom
group of trusted users who serve as the final decision making group for some disputes. An ArbCom is considered a high-level decision making body only for the parts of the UCoC that are within its scope, as defined by its community. An ArbCom may serve more than one project (e.g. Wikinews and Wikivoyage) and/or more than one language. For the purposes of these guidelines, this includes the Code of Conduct Committee for Wikimedia Technical Spaces and administrative panels. See also the definition on Meta-Wiki.

Binding verbs
When drafting the Enforcement Guidelines, the drafting committee considered the words 'create', 'develop', 'enforce', 'must', 'produce', 'shall', and 'will' as binding. Compare this to recommendation verbs.

Case Review Committee
See definition on Meta-Wiki.

Community
Refers to a project's community. Decisions made by a project's community are generally determined by consensus. See also: Project.

Cross-wiki
Affecting or occurring on more than one project. See also: Global.

Event safety coordinator
a person designated by the organizers of an in-person Wikimedia-affiliated event as responsible for that event's safety and security.

Global
Referring to all Wikimedia projects. In the Wikimedia movement, "global" is a jargon term referring to Movement-wide governing bodies. It generally is used to contrast against "local".

Global sysops
See definition on Meta-Wiki.

High-level decision-making body
A group (i.e. U4C, ArbCom, AffCom, Stewards) beyond which there can be no appeal of UCoC enforcement. Different issues may have different high-level decision-making bodies. This term does not include a group of users participating in a discussion organized at a noticeboard and resulting in a decision, even if the results of that discussion cannot be appealed.

Local
Referring to a single Wikimedia project, affiliate, or organisation. This term usually refers to the smallest, most immediate governing body applicable to the situation.

Off-wiki
Generally refers to online spaces that are not hosted by the Wikimedia Foundation, even if Wikimedia community members are present and actively using the space. Examples of off-wiki spaces include Twitter, WhatsApp, IRC, Telegram, Discord, and others.

Personally identifiable information
is any data that could potentially identify a specific individual. Any information that can be used to distinguish one person from another and can be used to deanonymize previously anonymous data is considered PII.

Project (Wikimedia project)
A wiki operated by the Wikimedia Foundation.

Recommendation verbs
When drafting the Enforcement Guidelines, the drafting committee considered the words 'encourage', 'may', 'propose', 'recommend', and 'should' as recommendations. Compare this to binding verbs.

Related space hosted on third party platforms
Websites, including private wikis, not operated by the Wikimedia Foundation but where users discuss project matters relevant to Wikimedia. Often moderated by Wikimedia volunteers.

Staff
Employees of and/or staff members assigned to a Wikimedia movement organization or contractors of such a movement organization whose work requires interaction with Wikimedia community members or in Wikimedia movement spaces (including third-party spaces such as off-wiki platforms dedicated to Wikimedia movement activity).

Steward
See definition on Meta-Wiki.

Systemic issue or failure
An issue for which there is a pattern of failing to follow the Universal Code of Conduct with participation of several people, particularly those with advanced rights.

Wikimedia Foundation Office Action Policy
The policy or its equivalent successor policy.
5月13日什么星座 思量是什么意思 散光和近视有什么区别 晚饭后散步有什么好处 一什么眉毛填量词
五个手指头分别叫什么 吃什么可以丰胸 麸质是什么意思 整体认读音节有什么 乳腺增生看什么科室
五月十七号是什么星座 chop是什么意思 甘油三酯指的是什么 石榴石一般什么价位 扑救带电火灾应选用什么灭火器
摩羯前面是什么星座 什么小说最好看 矿物质是什么 蒲地蓝消炎片主治什么 看对眼是什么意思
7.28是什么星座hcv9jop7ns0r.cn 芡实有什么功效hcv9jop1ns1r.cn tb是什么意思hcv9jop0ns0r.cn 卦不走空是什么意思hcv9jop3ns4r.cn 省公安厅副厅长是什么级别hcv9jop7ns2r.cn
2009属什么生肖hcv8jop8ns8r.cn 痛风可以吃什么肉hebeidezhi.com 着床出血是什么样子的hcv8jop2ns6r.cn 流浓黄鼻涕是什么原因hcv8jop9ns1r.cn 国家副主席是什么级别hcv8jop6ns7r.cn
低密度脂蛋白偏低是什么意思hcv7jop7ns1r.cn 有肾病的人吃什么好hcv8jop6ns7r.cn 做鸡蛋饼用什么面粉好hcv7jop5ns1r.cn 宬字五行属什么bjhyzcsm.com 宝宝屁多是什么原因hcv9jop2ns3r.cn
屈曲是什么意思hcv8jop8ns8r.cn 戌怎么读音是什么hcv9jop1ns2r.cn 乳房疼痛吃什么消炎药hcv8jop3ns7r.cn 玉婷是什么hcv9jop6ns8r.cn 抵抗是什么意思aiwuzhiyu.com
百度