Wikimedia Meta-Wiki

קוד ההתנהגות האוניברסלי/ועדת התיאום/הודעות

< Universal Code of Conduct | Coordinating Committee
This page is a translated version of the page Universal Code of Conduct/Coordinating Committee/Announcements and the translation is 36% complete.
Other languages:
ועדת תיאום קוד ההתנהגות האוניברסלי (U4C)
לוח מודעות זה מיועד להודעות והצהרות של ועדת תיאום קוד ההתנהגות האוניברסלי (U4C). רק חברי ה-U4C והמעצבים שלה רשאים לפרסם בדף זה, אך כל העורכים מוזמנים להגיב בדף השיחה.

רשימת כלים מוצעת

ה-U4C היה עסוק בהתקנה הראשונית שלנו. כחלק מכך, הועדה שוקלת לבקש את הכלים הבאים (ראה גם סעיף 3.7 (כלים) באמנת U4C):

גלובלית:

  • צפייה ביומן ההשחתות (abusefilter-log)
  • צפייה ביומן ההשחתות המפורט (abusefilter-log-detail)
  • צפייה ברשומות יומן של מסנני השחתות שסומנו כפרטיים (abusefilter-log-private)
  • צפייה במסנני השחתות (abusefilter-view)
  • צפייה במסנני השחתות שסומנו כפרטיים (abusefilter-view-private)
  • חיפוש דפים מחוקים (browsearchive)
  • צפייה בגרסאות שנמחקו, ללא הטקסט המשויך אליהן (deletedhistory)
  • צפייה בתוכן שנמחק ובהבדלים בין גרסאות שנמחקו (deletedtext)
  • הפעלת אימות דו־שלבי (oathauth-enable)
  • צפייה ברשומות מוסתרות ביומן ההשחתות (abusefilter-hidden-log)

ובמטא:

  • ניהול מוגבל במטא לניהול דפי ה-U4C באופן מקומי

ה-U4C מקבלת בברכה כל משוב מהקהילה לפני שנצביע רשמית על כל בקשת כלי.

מטעם ה-U4C, Barkeep49, ה-13 בספטמבר 2024

דיון בזה בדף השיחה

כלל מוצע של חוסר פעילות

ה-U4C עבדה על יצירת נוהל חוסר פעילות בתקווה לעזור לנו לעמוד בדרישות המניין שלנו לכמה עניינים עתידיים של עבודה לפנינו.

סעיף 3.2. באמנה (התנהגות חברי ה-U4C) נאמר כי:

חברי U4C צריכים:

  • לעסוק באופן פעיל בעבודת ה-U4C, ולהודיע ​​ל-U4C בתחילת כל היעדרות מהשתתפות U4C.

דווח על היעדרויות או תקופות חוסר פעילות

  • חברים יכולים לסמן את עצמם כלא פעילים לתקופה של היעדרות צפויה בקוד התנהגות האוניברסלי/ועדת תיאום/חברות. על החברים גם ליידע את חברי הועדה האחרים במידת האפשר באמצעות ערוצי התקשורת הרגילים.
  • כל חבר ב-U4C שלא השתתף במרחבי דיונים רשמיים של U4C (למשל מטא, ויקי פרטי, רשימת תפוצה, דיסקורד) במשך שבועיים לפחות עשוי להיות מסומן כנעדר בדף החברות ב-U4C על ידי כל חבר ב-U4C. במידת האפשר, תאריך חוסר הפעילות ייקבע בתאריך ההתקשרות הידועה האחרונה.
  • חוסר הפעילות מסתיים כאשר החבר ישתתף בפעם הבאה בדיון U4C, אלא אם כן החבר ציין או אכן ציין שהוא רוצה להישאר לא פעיל אחרת.

חוסר פעילות והצבעות

  • חבר ייחשב נמנע בכל העניינים המתרחשים במהלך תקופת חוסר הפעילות שלו.
  • למרות האמור לעיל, אף הצבעה לא תעבור עם פחות קולות תומכים ממה שנדרש כדי להגיע לרוב עם מניין של חברים שיצביעו בעד או נגד (כלומר >50%).

בשם U4C, Barkeep49 (שיחה) 18:23, ה-2 באוקטובר 2024 (UTC)

דיון בזה בדף השיחה

כלל חוסר פעילות

לאחר התייעצות קהילתית על כלל חוסר הפעילות המוצע, ה-U4C החליטה בהצעה:

1. לאמץ את הכללים הבאים הנוגעים לחוסר פעילות והצבעה:
כלל חוסר פעילות

סעיף 3.2. באמנה (התנהגות חברי ה-U4C) נאמר כי:
חברי U4C צריכים:

  • לעסוק באופן פעיל בעבודת ה-U4C, ולהודיע ​​ל-U4C בתחילת כל היעדרות מהשתתפות U4C.

דווח על היעדרויות או תקופות חוסר פעילות

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

חוסר פעילות והצבעות

  • חבר ייחשב כלא נוכח בכל הנושאים שיצוצו במהלך תקופת אי-פעילותו.
  • 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. לפרסם ולתחזק רשימה של חברים פעילים ולא פעילים במטא־ויקי.

This motion has been adopted with 7 supporting (0xdeadbeef, Ajraddatz, Barkeep49, Civvì, Ghilt, Ibrahim.ID, Luke081515), 0 opposed and 1 abstaining (Superpes15).

On behalf of the U4C,

Ajraddatz, 15 October 2024

Discuss this on the talk page

זכויות המשתמש

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:

Globally:

  • צפייה ביומן ההשחתות (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

Discuss this on the talk page

ויקימילון הגרמני (de.wiktionary)

A request regarding de.wiktionary was submitted to the U4C, you can read the request here.

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.

On behalf of U4C, Barkeep49 (שיחה) 01:23, 10 December 2024 (UTC)[reply]


Discuss this on the talk page

קופי (クフィ)

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.

ממצאי עובדה

  1. The conflict began as an on-wiki content dispute on zhwiki.
  2. クフィ posted comments about the content dispute off wiki.
  3. The U4C finds that those comments by クフィ violated the Universal Code of Conduct section 3.2 – Abuse of power, privilege, or influence.
  4. When asked by the U4C クフィ deleted the comments.
  5. 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

  1. クフィ is de-sysopped in wuu.wp and can reapply 12 months after publication of the U4C decision.

הצבעה והערות על ידי חברי U4C בודדים

  • Support. 0xDeadbeef (talk) 11:14, 14 January 2025 (UTC)[reply]
    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)[reply]
  • 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)[reply]
  • 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)[reply]
    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)[reply]
  • Support. --Civvì (talk) 19:03, 14 January 2025 (UTC)[reply]
  •   Support, per ghilts arguments. Luke081515 21:56, 14 January 2025 (UTC)[reply]
  • support --Ibrahim.ID (talk) 18:23, 15 January 2025 (UTC)[reply]
  • 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)[reply]

מטעם U4C, 0xDeadbeef (שיחה) 10:17, 17 January 2025 (UTC)[reply]

דיון בזה בדף השיחה

הוספה לתפקיד שלנו

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)[reply]

Discuss this on the talk page

סקירה שנתית 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)[reply]

מקרה של השעיית מפעיל מערכת בויקישיתוף

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)[reply]

Discuss this on the talk page

חבר U4C ללא הצבעה מונה

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)[reply]

Discuss this on the talk page

בבקין מיכאל (Бабкинъ Михаилъ)

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)[reply]

Discuss this on the talk page

מפגש 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

On behalf of the U4C, Barkeep49 (talk) 15:41, 25 February 2025 (UTC)[reply]

Discuss this on the talk page

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)[reply]

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)[reply]

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)[reply]

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Universal_Code_of_Conduct/Coordinating_Committee/Announcements/he&oldid=28493420"