通用行為準則/協調委員會/公告
擬議權限列表
U4C正緊急處理U4C用戶組的權限設置。為解決此問題，委員會擬議設置如下權限（另見于協調委員會章程中工具一節）：
全域權限：
- 查看滥用日志 (abusefilter-log)
- 查看详细滥用日志 (abusefilter-log-detail)
- 查看标记为非公开的滥用过滤器的过滤日志 (abusefilter-log-private)
- 查看滥用过滤器 (abusefilter-view)
- 查看被标记为非公开的滥用过滤器 (abusefilter-view-private)
- 搜索已被删除的页面 (browsearchive)
- 查看被删除的历史项目，不含相关文本 (deletedhistory)
- 查看已被删除的文本及已删除版本间的差异 (deletedtext)
- 启用双重身份验证 (oathauth-enable)
- 查看隐藏的滥用日志条目 (abusefilter-hidden-log)
Meta-wiki權限：
- 擁有部分管理員權限以管理Meta-wiki上與U4C相關的頁面
U4C欢迎社群用戶在我们對相關請求正式投票表决前提供意見。
謹代表U4C通告，
Barkeep49，2024年9月13日
- 相關話題請於此處討論
Proposed inactivity rule
The U4C has been working on creating an inactivity procedure in hopes of helping us meet our quorum requirements for some future matters of work ahead of us.
Section 3.2. of the charter (Conduct of U4C members) states that:
U4C members should:
- Actively engage in the U4C work, and inform the U4C at the start of any absence from U4C participation.
Communicate absences or inactivity periods
- Members may mark themselves as inactive for a period of expected absence on Universal Code of Conduct/Coordinating Committee/Membership. Members should also inform the other members of the committee where practical using the usual channels of communication.
- Any U4C member who has not participated in any official U4C discussion spaces (e.g. Meta, private wiki, Mailing List, Discord) for at least two weeks may be marked as absent on the U4C membership page by any U4C member. Where practical, the date of inactivity will be set at the date of the last known communication.
- Inactivity ends when the member next participates in a U4C discussion, unless the member has or does indicate they wish to remain inactive otherwise.
Inactivity and votes
- A member will be considered abstained on all matters that occur during their period of inactivity.
- Despite the above, no vote may pass with fewer supporting votes than would be needed to reach a majority with a quorum of members voting for or against (i.e. >50%).
On behalf of the U4C, Barkeep49 (talk) 18:23, 2 October 2024 (UTC)
- 相關話題請於此處討論
Inactivity rule
Following community consultation on the proposed inactivity rule, the U4C has decided by motion to:
- 1. Adopt the following rules relating to inactivity and voting:
Inactivity ruleSection 3.2. of the charter (Conduct of U4C members) states that:
U4C members should:
- Actively engage in the U4C work, and inform the U4C at the start of any absence from U4C participation.
Communicate absences or inactivity periods
- Members may mark themselves as inactive for a period of expected absence on Universal Code of Conduct/Coordinating Committee/Membership. Members should also inform the other members of the committee where practical using the usual channels of communication.
- Any U4C member who has not participated in any official U4C discussion spaces (e.g. Meta, private wiki, Mailing List, Discord) for at least two weeks may be marked as absent on the U4C membership page by any U4C member. Where practical, the date of inactivity will be set at the date of the last known communication.
- Inactivity ends when the member next participates in a U4C discussion, unless the member has or does indicate they wish to remain inactive otherwise.
Inactivity and votes
- A member will be considered abstained on all matters that occur during their period of inactivity.
- In cases where the number of abstentions brings the total number of voting members below the quorum (currently 8), votes can still be taken, but can only pass if they reach the simple majority required in a situation where a full quorum of members voted.
- 2. To publish and maintain a list of active and inactive members on Meta-Wiki.
This motion has been adopted with 7 supporting (0xdeadbeef, Ajraddatz, Barkeep49, Civvì, Ghilt, Ibrahim.ID, Luke081515), 0 opposed and 1 abstaining (Superpes15).
謹代表U4C,
Ajraddatz, 15 October 2024
- 相關話題請於此處討論
用户权限
Following community consultation on user rights for the U4C, the U4C has decided by motion to request the following permissions in accordance with section 3.7 of the U4C charter:
全域權限：
- 查看滥用日志 (abusefilter-log)
- 查看详细滥用日志 (abusefilter-log-detail)
- 查看标记为非公开的滥用过滤器的过滤日志 (abusefilter-log-private)
- 查看滥用过滤器 (abusefilter-view)
- 查看被标记为非公开的滥用过滤器 (abusefilter-view-private)
- 搜索已被删除的页面 (browsearchive)
- 查看被删除的历史项目，不含相关文本 (deletedhistory)
- 查看已被删除的文本及已删除版本间的差异 (deletedtext)
- 启用双重身份验证 (oathauth-enable)
- 查看隐藏的滥用日志条目 (abusefilter-hidden-log)
- 检索有关附加到修订版本或日志记录中的IP地址信息 (ipinfo)
- 查看临时账号使用的IP地址 (checkuser-temporary-account)
On Meta:
- Limited adminship on Meta to manage the U4C pages locally
This motion has been adopted with 7 supporting, 0 opposed and 1 abstaining.
On behalf of the U4C,
Ajraddatz, 15 October 2024
- 相關話題請於此處討論
de.wiktionary
The U4C decided to accept the request and the following motions were proposed to resolve the case:
- Action: the block of Mighty Wire gets lifted.
- Warning: we remind Mighty Wire of using a more civil tone in discussions. Lifting this block does not prevent future blocks.
- Recommendation: we recommend that dewikt administrators try to not perform administration actions when they have been previously involved in discussions or conflicts with a user, and if this cannot be avoided due to the low number of active administrators to be careful to avoid actions under a conflict of interest that can be seen as an act of silencing (potentially valid) criticism.
- Recommendation: we recommend an RfC (de:wikt:Wiktionary:Meinungsbild#Angabe_von_Glossen_in_Übersetzungstabellen) about the requirement of a glosse and the drafting of a clear guideline about how a glosse should be. Each local project, no matter how small, is not an island. If technical help is needed to automate operations help can be requested outside the project.
We also encourage Udo T. to continue to contribute to the RfC on de.wiktionary.
- Aktion: die Sperre von Mighty Wire wird aufgehoben.
- Warnung: wir erinnern Mighty Wire daran, einen höflicheren Ton in Diskussionen zu verwenden. Eine Entsperrung jetzt schützt nicht vor zukünftigen Sperren.
- Empfehlung: wir empfehlen, dass dewikt-Administratoren versuchen sollten, keine administrativen Aktionen durchzuführen, wenn sie zuvor in Diskussionen oder Konflikte mit einem Benutzer verwickelt waren, und wenn dies aufgrund der geringen Anzahl aktiver Administratoren nicht vermieden werden kann, darauf zu achten, dass Aktionen unter einem Interessenkonflikt vermieden werden, die als ein Akt des Unterdrückens von (potentiell berechtigter) Kritik angesehen werden können.
- Empfehlung: Wir empfehlen eine RfC (de:wikt:Wiktionary:Meinungsbild#Angabe_von_Glossen_in_Übersetzungstabellen) über das Erfordernis einer Glosse und die Erarbeitung einer klaren Richtlinie, wie eine Glosse aussehen sollte. Jedes lokale Projekt, und sei es noch so klein, ist keine Insel. Wenn technische Hilfe benötigt wird, um Abläufe zu automatisieren, kann Hilfe außerhalb des Projekts angefordert werden.
Wir ermutigen Udo T. auch, weiterhin zum RfC auf de.wiktionary beizutragen.
代表U4C, Barkeep49 (留言) 01:23, 10 December 2024 (UTC)
相關話題請於此處討論
クフィ
On 12 December 2024, the U4C received a request for a case to consider actions by クフィ on zhwiki and comments made off-wiki. On 20 December the U4C decided to accept the case as a private case and waive the two week voting period. The U4C then reached out to クフィ about the allegations on 23 December. クフィ replied on 24 December. The U4C and クフィ exchanged several further emails. The U4C is now ready to report on the case.
事實認定
- The conflict began as an on-wiki content dispute on zhwiki.
- クフィ posted comments about the content dispute off wiki.
- The U4C finds that those comments by クフィ violated the Universal Code of Conduct section 3.2 – Abuse of power, privilege, or influence.
- When asked by the U4C クフィ deleted the comments.
- The U4C considered other complaints made by the filer and a complaint made by クフィ against another editor. The U4C did not find there to be anything needing action by the committee.
U4C行動
- クフィ is de-sysopped in wuu.wp and can reapply 12 months after publication of the U4C decision.
Vote and comments by individual U4C members
- Support. 0xDeadbeef (talk) 11:14, 14 January 2025 (UTC)
- I feel the same with Barkeep49 that if the comments were not deleted I would have pursued further sanctions. I'd like to reaffirm my support as I disagree with this being a minor dispute. This was a clear off-wiki violation of the UCoC, and the U4C should be responsible to handle this. The behavior in the evidence shown to us falls short of what we expect from a contributor, and falls well below the standard for expected behavior of an admin. The removal of sysop permissions is not permanent, and クフィ could re-apply adminship through the local processes if they wish after 12 months. 0xDeadbeef (talk) 10:17, 16 January 2025 (UTC)
- Support. According to UCoC 3.2 Admins must not be disrespectful or cruel. On the other hand, the cooperation was taken into account. --Ghilt (talk) 15:53, 14 January 2025 (UTC)
- Support. If クフィhad not been willing to delete the comments I would have felt we needed to pass other remedies; a block and/or an interaction ban were 2 sanctions I thought about. However, given クフィ's cooperation I do not think those are needed. But as Ghilt writes the UCoC expects more from than other users. This is why I support removing adminship in this case but also am OK with クフィ having the chance to reapply in 12 months. Barkeep49 (talk) 16:05, 14 January 2025 (UTC)
- Noting that I respect all of Ajraddatz's opposition but do disagree with his characterizing this as a minor dispute. Barkeep49 (talk) 03:06, 16 January 2025 (UTC)
- Support. --Civvì (talk) 19:03, 14 January 2025 (UTC)
Support, per ghilts arguments. Luke081515 21:56, 14 January 2025 (UTC)- support --Ibrahim.ID (talk) 18:23, 15 January 2025 (UTC)
- Oppose. After doing a full review of the case, I think the suggested remedy (desysopping) is excessive. There was a content dispute on-wiki, the administrator in the dispute posted an inappropriate insulting comment on X, and with the mediation of the U4C the post was taken down. While I don't think the administrator's actions in this case were acceptable, I also think that as a first time violation, and without a pattern of behaviour to rely on, a more suitable remedy would be an admonishment and warning. Additionally, while I agree that this case could fall to the U4C as the alleged violations occurred off-wiki, neither party appears to be particularly guarding of connection between their on and off-wiki activities and I would prefer that the U4C avoid being drawn in to relatively minor disputes such as this one. Ajraddatz (talk) 01:03, 16 January 2025 (UTC)
代表U4C, 0xDeadbeef (留言) 10:17, 17 January 2025 (UTC)
- 相關話題請於此處討論
Adding to our role
The U4C is considering adding the following permissions to our U4C role on a global basis:
- autoconfirmed
- editsemiprotected
On behalf of the U4C, Barkeep49 (留言) 21:31, 22 January 2025 (UTC)
- 相關話題請於此處討論
Annual review 2025
The Annual Review of the Universal Code of Conduct, the enforcement guidelines and the charter begins today, on 23 January 2025. We are preparing a wider notification than just here. Community members are dearly invited to make proposals or comments on potential changes to these three documents. On behalf of the U4C, --Ghilt (留言) 14:22, 23 January 2025 (UTC)
Commons administrator case suspension
A request regarding a Commons administrator was submitted to the Universal Code of Conduct Coordinating Committee (U4C), you can read the the full request here. The U4C has passed the following motion 7-0 (with 1 member inactive):
The case request is suspended for 6 months to allow the Commons community time to incorporate the UCoC into its practices/procedures (e.g. desysop). Following unsuspension the U4C will consider how to further proceed (accept the case, pass a further motion, or decline the case). All editors who have commented on the case will be notified when the case is unsuspended.
Further comments by U4C members on the motion are available to be read here. On behalf of the U4C, Barkeep49 (留言) 19:13, 31 January 2025 (UTC)
- 相關話題請於此處討論
U4C Non-voting member appointed
The Wikimedia Foundation has decided to appoint Jacob Rogers, Associate General Counsel for the Wikimedia Foundation, to the U4C as a non-voting member. Under the charter, the foundation may appoint up to 2 non-voting members. Please join us in welcoming Jacob to the U4C.
On behalf of the U4C, Barkeep49 (留言) 21:43, 4 February 2025 (UTC)
- 相關話題請於此處討論
Бабкинъ Михаилъ
The U4C received private evidence, that showed abusive behaviour from Mikhail Babkin. The U4C decided that this behavior was unacceptable. Following this assessment, the U4C decided to globally ban Mikhail Babkin. This ban may only be appealed to the U4C. On behalf of the U4C, Luke081515 07:13, 19 February 2025 (UTC)
- 相關話題請於此處討論
U4C會議
Between the 12th and 16th February 2025, 6 of 8 U4C members met in person, one attended online, and one was inactive. Below are topics that we discussed and decisions made that are ready to be announced. Other decisions and tasks will be announced as they are completed.
The U4C discussed these topics:
- Day 1
- What do we want to have the activity report included, how can we reliably collect the data?
- Decision: Report number of public cases and private requests received.
- Optimize email intake workflow
- Discuss and optimize private case process
- Discuss scalability of processes with a possible bigger committee and/or more cases in the future
- Discuss the need and organization of subcommittees once there is a bigger U4C
- Decision: introduction of a U4C Case Coordinator (U6C) who internally organizes cases, has an eye on the deadlines, coordinates the members
- Discuss and optimize the public case process
- Discuss and optimize internal documentation, discuss best practices
- Discuss proposals for annual review, review proposes made by the community for the enforcement guidelines and the U4C Charter
- Decision: UCoC review to go on separate timeline. U4C to reach out to the board
- Discuss ideas how to change the vote process to get more members in the U4C next election
- Decision: propose changes in annual review
- Day 2
- Continue discussion about annual review
- Assign task to members about creating proposals for the annual review
- Discussion about process after public case is accepted
- Decision: Cases will have 4 phases. Request (U4C decides to accept/reject request), Investigation (allow for further evidence), evidence review (allow U4C to review evidence and prepare decision), and proposed decision (feedback on draft decision and U4C voting on it)
- Discussion about template to make the current process step transparent and explain it
- Discussion about deadlines for submitting evidence
- Discussion about next steps and decisions in the following cases:
- Case "Sysop abuse in Swahili Wikipedia"
- Case "A.Savin"
- Private case
- Discussion about the UCoC-Training materials, proposals about improvements, examples
- Open questions about private case handling
- Discussion about working with WMF T&S
- Discussion about possible future cases
- Discussion about previous systemic failures
- Day 3
- Discussion of the incident reporting system
- Discussion about working with Stewards
- Discussion about current U4C-Userrights and need for other user rights
- Discussion about case delegation, for example to a local body
- Discussion about handling minor violations
- Discussion about state of UCoC enforcement
- Discussion about best practices and providing recommendations
- Discussion about off-wiki violations
- Confirm next steps and who is responsible for them
謹代表U4C, Barkeep49 (talk) 15:41, 25 February 2025 (UTC)
- 相關話題請於此處討論
Universal Code of Conduct annual review: proposed changes are available for comment
The proposed changes to the Universal Code of Conduct (UCoC) Enforcement Guidelines and Universal Code of Conduct Coordinating Committee (U4C) Charter are open for review. You can provide feedback on suggested changes through the end of day on Tuesday, 18 March 2025. This is the second step in the annual review process, the final step will be community voting on the proposed changes. Read more information and find relevant links about the process on the UCoC annual review page.
Please share this information with other members in your community wherever else might be appropriate.
-- In cooperation with the U4C, Keegan (WMF) (talk) 19:25, 7 March 2025 (UTC)
Off-wiki incidents & the UCoC
The U4C has received several reports alleging UCoC violations that have occurred on external platforms. The U4C would like to remind the community about UCoC expectations in spaces hosted on platforms like Telegram groups or Discord servers or on other social media and instant messaging platforms dedicated to Wikimedia projects or Wikimedia user groups. According to the Enforcement Guidelines:
"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."
For this reason, we invite all those who have a role in the administration or moderation of these spaces:
- if technically feasible, to include a link to the UCoC in the introductory section and/or welcome message to new members.
- to intervene in cases of need by reminding the participants of the appropriate behaviour in order to maintain a constructive climate of cooperation.
We would also like to point out that maintaining a positive and safe environment is the responsibility of all participants in these groups. If there are concerns about ineffective moderation, please send the relevant information and evidence to u4c
wikimedia
org. On behalf of the U4C, --Ghilt (talk) 16:51, 19 March 2025 (UTC)
Adding checkuser-log temporary to the userrights of the U4C
The U4C has decided by motion to request the following permissions in accordance with section 3.7 of the U4C charter:
For the duration of the case "Systemic failure in enforcing the code of conduct in Hebrew Wikipedia", the checkuser-log permission will be added to the U4C global role to allow members of the U4C to investigate in the past Checkuser-Tool use related to that case. This motion was supported by 7 members, opposed by 0. One member was inactive at the time of the vote on the motion. On behalf of the U4C, Luke081515 14:34, 23 March 2025 (UTC)
Ganímedes
On 9 March 2025, the U4C received a request to consider some comments made offwiki by User:Ganímedes within an email exchange. The U4C decided to accept the case as a private case. The U4C then reached out to the involved users to collect evidence.
The U4C is ready to report on the case.
Findings of fact
The conflict began during an email exchange between User:Ganímedes and other users.
Based on the limited emails in the exchange the U4C received, the U4C finds that comments by User:Ganímedes violated the Universal Code of Conduct section 2 – Expected behaviour
U4C Actions
The U4C decides to close the case with a:
- Warning to User:Ganímedes - even if one feels provoked one can also decide not to reply or to reply without crossing the boundaries of civil behavior and without insulting the other party
- A reminder to involved parties that if a user repeatedly asks not to be contacted again the request should be respected
Vote and comments by individual U4C members
- --Ghilt (talk) 12:28, 18 April 2025 (UTC)
- +1 --Superpes15 (talk) 13:56, 18 April 2025 (UTC)
- Support --Civvì (talk) 14:22, 18 April 2025 (UTC)
- +1 Ajraddatz (talk) 16:17, 20 April 2025 (UTC)
- Barkeep49 (talk) 14:47, 21 April 2025 (UTC)
- --Ibrahim.ID (talk) 09:10, 22 April 2025 (UTC)
- Support 0xDeadbeef (talk) 09:13, 22 April 2025 (UTC)
- Luke081515 20:31, 22 April 2025 (UTC)
謹代表U4C, --Civvì (talk) 10:20, 24 April 2025 (UTC)
中文維基文庫
The U4C has received a case about administrators on Chinese Wikisource (zhsource). The following motion has been adopted to resolve the case:
The U4C resolves this case by motion. We encourage the zhsource community to continue to resolve the conflict presented at this case locally. As a first step, an RFDA for Zhxy 519 should be held. No party to this case may close or remove the RFDA. Any interference with this RFDA may be reported to the U4C. We also warn all zhsource admins against improper interference with RFDAs. This includes not closing or removing any RFDA about them. The U4C may remove adminship by motion against any zhsource admin who improperly interferes with an RFDA in the future.
| Translation/翻譯 |
|---|
|
U4C 收到了有關中文維基文庫 (zhsource) 管理員的案件。為解決此案，特採納以下動議： U4C 藉由動議結案。我們鼓勵 zhsource 社群繼續在本地解決此案所提出的衝突。作為第一步，Zhxy 519 的解任案應該舉行。本案的任何一方都不得關閉或移除此解任案。任何對此解任案的干擾都可向 U4C 報告。我們警告所有 zhsource 管理員不要不當干擾 RFDA。不當干擾包括關閉或移除任何關於自己的 RFDA。U4C 可能會對此後不當干擾 RFDA 的 zhsource 管理員提出除權動議。 |
Further noting some points as per internal discussion about this case:
- Local policy requires a discussion and debate period for all RFDAs. The U4C believes that this case request has served as a discussion and debate period, and therefore the voting period should be started immediately.
- The U4C will closely monitor the RFDA and will action on any misconduct, if they occur during the RFDA, as appropriate.
| Translation/翻譯 |
|---|
|
根據內部討論，進一步說明此案的一些要點：
|
謹代表U4C, 0xDeadbeef (talk) 05:41, 23 May 2025 (UTC)
MediaWiki
The U4C has received a private request regarding the UCoC and the MediaWiki software. The committee has decided to resolve the case by the following motion:
✅ Passed Motion— Date: 2025-06-08
Following the UCoC's expectation that people "Respect the way that contributors name and describe themselves" including "People who identify with a certain sexual orientation or gender identity using distinct names or pronouns" the U4C recommends accommodating more pronoun choices in mediawiki software other than he, she, and they and also add an option for people to decline to say.
This motion was passed with 6 supports and 0 opposes.
Furthermore, the U4C would also like to draw attention to T389706 and T389709 which are specific tickets for tracking these features in the MediaWiki software.
謹代表U4C, dbeef (talk) 08:53, 8 June 2025 (UTC)
2025 U4C election results
The election results for the annual U4C elections have been published. We welcome our new member, BRPever, and welcome back Barkeep49, Civvì and Luke081515! On behalf of the U4C, --Ghilt (talk) 21:25, 2 July 2025 (UTC)
Appeals on Hebrew Wikipedia
By an 8-0 vote the U4C has approved the following motion:
- All people blocked in the mass blockings are eligible to appeal under this process.
- The first step should be a local hewiki appeal. Any bureaucrat and checkuser may accept or deny the appeal or they may delegate an appeal to be heard by an administrator or the entire community. When declining an appeal the reviewing person may also supply additional context to the U4C to consider about that editor's past history.
- If an appeal is accepted nothing further. For any appeals declined, the person declining should send a link of the local appeal to the U4C. The appeal will then be reviewed by the U4C.
- After receiving an appeal the U4C will acknowledge it. If the U4C has not acknowledged it with-in 2 days of the appeal being declined, the person appealing is encouraged to contact the U4C directly at u4c
wikimedia
org. - A U4C member will screen for reasonableness as some of the blocks are clearly correct. If an appeal is reasonable, it will be considered by 3 U4C members (1 of the 3 can be the person who did the initial screen but doesn't have to be). At least 2 of the 3 need to agree to accept an appeal for the person to be unblocked; they may also refer an appeal to be considered by the whole committee.
- If an appeal isn't decided on hewiki within 30 days, the person filing the appeal may go directly to the U4C.
On behalf of the U4C, Barkeep49 (talk) 20:12, 24 July 2025 (UTC)