Hello Everyone,
I would like to propose two - probably new - features for MediaWiki.
Since my native language is German, I would like to discuss these
features with some developers from Germany, Austria, or Switzerland.
My Englisch is really bad and therefore, I would prefer to discuss in
German language. Please feel free to contact me via e-mail.
Best regards,
Siegfried
--
Siegfried.Schmitt(a)web.de
Hello all,
I like to get top 1000 contributors for ta.wikipedia.org based on their
usercontribution metric.
is there any code this or api?
Please share.
Thanks.
--
Regards,
T.Shrinivasan
My Life with GNU/Linux : http://goinggnu.wordpress.com
Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com
Get Free Tamil Ebooks for Android, iOS, Kindle, Computer :
http://FreeTamilEbooks.com
Hi,
I have nominated Dreamy_Jazz for +2 rights in the CheckUser extension,
please feel free to comment at <https://phabricator.wikimedia.org/T311331>.
Thanks,
-- Legoktm
This email is a summary of the Wikimedia production deployment of
1.39.0-wmf.16
* Conductor: Brennen Bearnes
* Backup Conductor: Dan Duvall
* Blocker Task: T308069 <https://phabricator.wikimedia.org/T308069>
* Current Status <https://versions.toolforge.org>
📈 Numbers
Sparklines comparing with the last 5 trains.
* 212 Patches █▆▃▅▁
* 0 Rollbacks ▁▁▁█▁
* 0 Days of delay ▁▁▁█▁
* 4 Blockers █▁▁█▁
✨ Trainbow Love 🥰
Thanks to folks who helped report or resolve blockers:
* Seddon
* Tim Starling
* PleaseStand
* Timo Tijhof
* Aaron Schulz
* Tyler Cipriani
* Jon Robson
* James D. Forrester
Worth highlighting in particular: Krinkle's breakdown of increased
Mcrouter requests <https://phabricator.wikimedia.org/T310532#8004500>.
--
Brennen Bearnes
Release Engineering
Wikimedia Foundation
Hi All
There will be no train the week of 2022-07-11 (Mon, 11 Jul–Fri, 15
Jul)—this is the Wikimedia Foundation's Inspiration Week.
There is a long-term calendar of upcoming deployment disruptions available
on Wikitech: https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar
Thanks!
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
Open main menu
Wikimedia Meta-Wiki
Search
Ombuds commission
Language
Watch
Edit
Other languages:
Bahasa Indonesia Cymraeg Deutsch Deutsch (Sie-Form) English Esperanto Lëtzebuergesch Nederlands Ripoarisch Scots Sunda Tiếng Việt Türkçe Zazaki asturianu català dansk español français hrvatski italiano lietuvių magyar occitan polski português português do Brasil română suomi svenska čeština български русский українська հայերեն עברית العربية سنڌي فارسی پښتو नेपाली বাংলা ગુજરાતી தமிழ் తెలుగు മലയാളം ไทย 中文 日本語 粵語 한국어
For legal and security reasons, the Wikimedia Foundation has decided to require two-factor authentication for this role.
Ombuds Commission
Wikimedia Ombuds logo.svg
About the commission
Discuss the ombuds
Send a complaint
Email the commission
Activity reports
2013
2014
2015
2016
2017
2018
2019
2020
2021
The ombuds commission, on behalf of the Board of Trustees, investigates complaints about infringements of the Privacy Policy, the Access to nonpublic personal data policy, the CheckUser policy and the Oversight policy, on any Wikimedia project. They also investigate for the Board the compliance of local CheckUser or Oversight policies or guidelines with the global CheckUser and Oversight policies.
Tasks
In addition to official investigation, they will mediate between the complainant and the respondent (usually a CheckUser, oversighter, Bureaucrat, Administrator, or arbitration committee member). When legally necessary, the ombuds will assist the General Counsel, the Executive Director or the board in handling the case.
When the case is litigious, the ombuds will be in charge of educating CheckUsers or others about the Foundation's privacy policy. When the Privacy Policy, Access to Nonpublic Information Policy, CheckUser Policy, or Oversight policy have been breached, the ombuds commission should report to the Executive Director or designated staff and recommend a course of action (such as removal of access to tools). Additionally, the commission might suggest suitable changes to policies or software.
Neutrality
An ombuds' investigation should be conducted in a manner determined by the ombuds to ensure fairness and impartiality. As a general guideline, it is best that ombuds avoid conflicts of interest as much as possible, particularly by avoiding routine use of CheckUser or oversight access and not processing complaints on the projects on which they are very active editors. However, matters that come before the commission are not clear-cut, and the language and culture of various projects may pose barriers to outsiders. As such, how the commission investigates complaints is left to the discretion of its appointed members.
Membership
Members of the ombuds commission are selected from the Wikimedia community by Wikimedia Foundation officials. A call for volunteers is issued each year in early December on the Wikimedia-L mailing list and on the talk page of this policy, as well as other project forums as appropriate. They are appointed (assuming they agree) for a period of approximately one year. A non-voting alternate member may be appointed to serve for one year, with an expectation for a seat as a full member the following year.
Assigned rights
Ombuds have the following rights globally, among others:
Search deleted pages (browsearchive)
Check users' IP addresses and other information (checkuser)
View the checkuser log (checkuser-log)
View deleted history entries, without their associated text (deletedhistory)
View deleted text and changes between deleted revisions (deletedtext)
View private logs (suppressionlog)
View revisions hidden from any user (viewsuppressed)
Current members
User Home wiki(s) Language spoken IRC nick
Ameisenigel (CA) dewiki, wikidatawiki de, en-4, nds-2, fr-1, tlh-1 Ameisenigel
Érico (CA) ptwiki pt -
Faendalimas (CA) wikispecies en, pt-3, it-2, fr-1 faendalimas
Galahad (CA) eswikivoyage es, en-1 Galahad
Infinite0694 (CA) jawiki ja, en-3, de-3, fr-2, it-1 -
JJMC89 (CA) enwiki en JJMC89
Mykola7 (CA) ukwiki uk, ru-4, en-2, de-1 -
Olugold (CA) enwiki, wikidatawiki, igwiki ig, en-5, Ha-4 Olugold
Udehb (CA) wikidatawiki ig, en-5 -
Zabe (CA) wikidatawiki, mediawikiwiki de, en-3, la-1 zabe
See also automatically generated list (terms expire February 2023).
For the prior membership, see here.
Submission
Complaints may be made to the ombuds commission through the following ways (preferably in a language spoken by one of the members):
To use the form, access this link: Special:Contact/ombudscommission
To write an email, access this link: Special:EmailUser/Ombuds commission
Both ways will send message directly to OC mailing list.
Please follow these guidelines when submitting an inquiry to the commission:
Be concise. Lengthy emails with unnecessary information make it harder for the commission to process the case in a timely manner.
Be objective. Avoid making inquiries based on speculations or subjective judgements.
Provide evidence. Please provide us with diff links and/or permanent links when possible.
Be specific. Specify what part of which policy has been violated.
Please inform us if your wiki has an Arbitration Committee (or a similar committee) and if you have reached them (or used other dispute resolution procedure customary to your community) before reaching the ombuds commission. Provide a link to the relevant case page if appropriate.
Processing/Reporting
Cases brought to our attention will be processed the following way:
Confirmation of the request: we will send a notice of confirmation to the requester, and if necessary ask for further information.
Scope: if the request is within the scope of the ombuds commission, we will do the investigation, if not we will decline the request and try to direct the complainant to a better place to get help for his/her individual problem.
Investigation: We do whatever is necessary to find out whether or not there was a breach of the policies or a non-compliance or conflict of local policies with the global ones.
Result: We give the result of our investigation to the requester, and if there was indeed a breach of the privacy policy, we will inform the user who was investigated and if necessary inform the Board of Trustees and if necessary recommend removing OS, CU or steward rights from the user breaking the policy.
Activity reports
Activities:
in 2013: February–June, July–December.
in 2014: January–June, July–December.
in 2015: January–June, July–December.
in 2016: January–June, July–December.
in 2017: January–June, July–December.
in 2018: January–June, July–December.
in 2019: January–June, July–September, October–December.
2020 Commission: January-March, April-January 2021.
2021 Commission: February-April, May-July, August-October, November-January 2022.
2022 Commission: February-April.
See also
Board resolutions: Ombudsperson Checkuser (July 2006) — Wikimedia Committees (minutes of presentation on Ombudsman Commission; January 2009) — Amending the Scope of the Ombudsman Commission (November 2015)
Requests for comment: Scope of Ombudsman Commission (May—December 2013)
Announcement Ombudsman commission wider scope (January 2016)
New commission announcements: 2007 — 2009 — 2011 — 2012 — 2013 — 2014 — 2015 — 2016 — 2017 — 2018 —2019 — 2020 —2021 — 2022
Information on the ombuds global user group:
Ombuds: global permission · global groups (toolforge) · member list · group changelog
Special global permissions
2021 workflow updates
Last edited 1 month ago by Ameisenigel
Wikimedia Meta-Wiki
Content is available under CC BY-SA 3.0 unless otherwise noted By Ai.A13(key)msg
Privacy policy Terms of Use Desktop
Language
Watch
Edit
Other languages:
Bahasa Indonesia Deutsch English Lëtzebuergesch Nederlands Tiếng Việt Türkçe dansk español français hrvatski italiano magyar polski português português do Brasil sicilianu suomi čeština Ελληνικά русский українська العربية روچ کپتین بلوچی فارسی پښتو नेपाली বাংলা മലയാളം ไทย 中文 日本語 한국어
Users who are given the ipblock-exempt flag ('ipblock-exempt' user group) are not affected by autoblocks, blocks of IP addresses and rangeblocks (both global and local). They are also exempt from proxy blocks and Tor blocks. This right is automatically assigned to administrators, however the flag must be added separately for non-administrators to enable editing from IP addresses affected by IP or IP range blocks. The ipblock-exempt flag cannot be granted to editors who do not use an account.
There is also a global group to override IP blocks globally. See Global block exemptions for more information.
Historically, administrators would "softblock" IP's allowing named editors to continue to edit, while disallowing any anonymous editing and user registrations. With this flag, this is no longer required.
How to get this flag
Edit
To get this flag and become IP block exempt on a specific project one must ask an administrator of that project. The information on who should or should not get this userright can be found on the no open proxies page. However every project may have its own IP block exemption policy.
For specific information about IP block exemption on Meta, see Meta:IP block exemption
To get a global exemption from global blocks one must make a request to stewards at Steward requests/Global permissions.
Note: that an exemption granted by a steward will only circumvent a global block placed by stewards. An global exemption will not circumvent a local block placed at a wiki by a local administrator. Blocks at wikis (local blocks and local exemptions) override global actions for that wiki.
Interactions of local and global block exemptions
Edit
Blocks and exemptions work differently depending on where they are imposed, and by whom they are imposed.
Local blocks
Edit
A local block only works at the one wiki.
Local blocks are applied by local administrators.
A local block exemption only overrides the block at the one wiki, and it exempts all blocks placed.
Global blocks
Edit
A global block works on all centralised wikis, with the exception of metawiki (this wiki)
Global blocks are typically only placed by stewards.
Global IP block exemptions override global blocks only, it has no impact on local blocks.
Local administrators can override (whitelist) for their wiki a steward's global block through that wiki's Special:GlobalBlockWhitelist page
Comparison of local/global blocks and local/global exemptions.
Block imposed by Local administrator
(local block) Steward
(global block)
Type of exemption
Local IP block exemption unblocked unblocked
Global IP block exemption blocked unblocked
No exemption blocked blocked
See also
Edit
Blocked user
Global IP block exemption
Policy on Meta
Phabricator (phabricator.wikimedia.org) will be down tomorrow sometime
during the 15:00–17:00 UTC[0] maintenance window[1].
We're deploying updates during that time, and we'll stop Phabricator
briefly to run database migrations.
I'm sorry if the timing of the upgrade window is inconvenient for
anyone. But having more folks around at the time of the upgrade
mitigates some of the risks, too.
Thank you!
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
[0]: <https://zonestamp.toolforge.org/1655305257>
[1]: <https://wikitech.wikimedia.org/wiki/Deployments#deploycal-item-20220615T1500>