Hello,
People usually ask me how they can patrol edits that affect their Wikipedia
or their language. The proper way to do so is by using watchlist and
recentchanges (with "Show Wikidata edits" option enabled) in Wikipedias but
sometimes it shows too many unrelated changes.
Also, it would be good to patrol edits for languages you know because the
descriptions are being shown and editable in the Wikipedia app making it
vulnerable to vandalism (so many vandalism in this area goes unnoticed for
a while and sometimes gets fixed by another reader which is suboptimal).
So Lucas [1] and I had a pet project to allow you see unpatrolled edits
related to a language in Wikidata. It has some basic integration with ORES
and if you see a good edit and mark it as patrolled it goes away from this
list. What I do usually is to check this page twice a day for Persian
langauge which given the size of it, that's enough.
It's in https://tools.wmflabs.org/wdvd/index.php the source code is in
https://github.com/Ladsgroup/Vandalism-dashboard and you can report
issues/bug/feature requests in
https://github.com/Ladsgroup/Vandalism-dashboard/issues
Please spread the word and any feedback about this tool is very welcome :)
[1]: <https://www.wikidata.org/wiki/User:Lucas_Werkmeister_(WMDE)>
https://www.wikidata.org/wiki/User:Lucas_Werkmeister_(WMDE)
<https://www.wikidata.org/wiki/User:Lucas_Werkmeister_(WMDE)>
Best
Friends,
Anyone interested in ORES and Scoring Platform’s recent progress can read an exhaustive list on our engineering blog,
https://phabricator.wikimedia.org/phame/post/view/84/status_update_january_… <https://phabricator.wikimedia.org/phame/post/view/84/status_update_january_…>
Aside from supporting several new languages, the biggest changes that might affect other developers are that: we now supply enwiki new article draft quality predictions, already loaded into the MediaWiki database via Extension:ORES; and all of our models now include statistics that can be used to calculate appropriate cutoff points.
Enjoy!
-Amir, Aaron, Adam, and Sumit
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2018.01. This bundle is The bundle is compatible with MediaWiki
1.29 and 1.30 or above and requires PHP 5.5.9 or above.
Next MLEB is expected to be released in 3 months. If there are major
changes or important bug fixes, we will do intermediate release.
Please give us your feedback at
[[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.01.tar…
* sha256sum: a6d90633cf16dbf48c0481d1e073130717d98b9540c0d1b80059bb34946c6749
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://phabricator.wikimedia.org/
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Highlights and upgrade notes ==
== Babel and LocalisationUpdate ==
=== Noteworthy changes ===
* Localisation and maintenance updates only.
== cldr ==
=== Noteworthy changes ===
* Updated to CLDR 32.
* Localisation and maintenance updates.
== cleanchanges ==
=== Noteworthy changes ===
* Added wgCCFiltersOnly to disable "clean changes" (which has issues
with new recent changes interface) while keeping filters available.
* Localisation and maintenance updates.
== Translate ==
=== Noteworthy changes ===
* Special:PageMigration: Fixed save button, added RTL direction
support and fixed broken icon in delete button. (T179182, T139463)
* Added RESTBaseWebService support to allow using Apertium using
CXServer MT API through RESTBase.
* Removed MediawikiExtensionFFS. Migrate to JsonFFS if you were still
using this format.
* Almost all legacy non-TUX code has been removed. (T132546)
* Added "Link to this message" to translation editor tools.
* GettextFFS keyAlgorithm default value changed to "simple" from
"legacy". This will produce shorter page titles and shorter titles.
You must add legacy to your configuration to keep using existing
titles for GettextFFS. (T178882)
* Translation filter is now part of the new recent changes interface
if the new interface is available.
== UniversalLanguageSelector ==
=== Noteworthy changes ===
* User interface and search improvements.
* Fixed page scroll to the top when the the ULS gear icon is clicked. (T178188)
==== Fonts ====
* Removed non-default webfonts for some languages. (T180422)
* Remove the autonym font and tofu detection.
* ULS no longer serves TTF files to browsers because all recent
browsers support the woff format.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
Hello,
Iam trying to figure out a discrepancy between
(i) querying statistics numbers returned by the API (e.g.
http://www.grazwiki.at/api.php?action=query&meta=siteinfo&siprop=statistics…)
and
(ii) querying the page titles and metadata using the API (e.g.
http://www.grazwiki.at/api.php?action=query&list=allpages&aplimit=500&apnam…)
(i) reports
12816 pages
6300 articles
46584 edits
6551 images
137 users
(ii) sums up to
17788 pages (sum over all namespaceIDs >=0)
46906 edits (parsed using
http://www.grazwiki.at/api.php?action=query&prop=revisions&pageids=100&rvpr…)
72 users
(http://www.grazwiki.at/api.php?action=query&list=allusers&aulimit=500&forma…)
! So I have much more pages when fetching them step by step than
reported by the statistics query (only namespaceIDs >= 0, ensuring that
I do not count duplicated)
! API lists 72 users, but statistics report 137
! Edits roughly match, but I have other Wikis in the pipeline where the
difference is much higher
First I thought that the official statistics leave out some namespaces,
but I could not figure combination which would explain the results.
Could it be cached results? That would be quite a difference and it
would not really explain the user-delta.
Iam extracting the Wikis for research and want to make sure that I have
an accurate extraction/representation of the Wikis.
=> I would appreciate any information and ideas that can explain the
differences.
Regards,
Rüdiger
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 4-5 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Hello,
Due to both the SRE (nee Technical Operations) team traveling this week
combined with the Release Engineering team at an offsite we are
cancelling the remaining SWAT deploys this week.
For the most up to date and canonical version of the deployment calendar
please see, as always:
https://wikitech.wikimedia.org/wiki/Deployments
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
Hello. I have a watching issue. Writing here and not in phabricator,
because it's absolutely non reproduceable. So if somebody is interested -
here are the details.
I found now an article in my watchlist that I never added to it. I checked
and saw more articles like this. Including the first one, 12 articles I
never added, never edited and never opened. All of them talk about the same
city. I never was there and never read aboit it in wiki. After some more
checks I saw that all of them are in the same category, about some small
neigbourhood in this city. I never heard its name. The category includes 13
articles. The redundant one was created a couple of weeks ago. The category
itself is not in the watchlist. And I don't thing I just don't remember,
because I do not work on this wiki so much, so there are 61 articles in my
watchlist there, 20% of them problematic. It's a murricle.
Igal (User:IKhitron)
Hello,
Some background:
The Sunsetting Working Group[0], which came out of a WMF Technology
manager's face-to-face after Wikimania and is made up of
cross-departmental members, was given the goal of determining how we
can reduce the set of un-, under-, or not clearly maintained code
running in Wikimedia production. To be clear, the goal was not to
"sunset" (aka: remove) all un-, under-, or not clearly maintained
code, but instead make an effort to resolve
'stewardship'/'ownership'/'maintainership' issues as best we can.
The process the working group devised is outlined on mediawiki.org[1].
In short it is: propose something to review, fill out the rubric, give
time for wider feedback, submit a prioritized list to the WMF Chief
Product and Chief Technology officers so they can make the hard
decisions of what to fund and how.
This is the first time we are doing this process and we are on an
abbreviated schedule with respect to the Foundation Annual Planning
timeline. We will be doing these quarterly on a known schedule (to be
published at a later date) to remove any future similar time schedule
stress.
The point of this email:
We have 4 reviews currently proposed[2]. They are:
* AbuseFilter (and dependencies)
* IRC RecentChanges feed
* RelatedSites extension
* TimedMediaHandler
We are soliciting wider feedback on wiki[3]. Please leave feedback on
the relevant talk page.[4][5][6][7]
Again, unfortunately our timeline is abbreviated this time around and we
will be closing the feedback on February 7th.
Thank you for your feedback!
Greg
[0] https://www.mediawiki.org/wiki/Sunsetting_Working_Group
[1] https://www.mediawiki.org/wiki/Code_stewardship_reviews#Process
[2] https://phabricator.wikimedia.org/project/board/3144/
[3] Subpages of https://www.mediawiki.org/wiki/Code_stewardship_reviews/Feedback_solicitati…
[4] https://www.mediawiki.org/wiki/Talk:Code_stewardship_reviews/Feedback_solic…
[5] https://www.mediawiki.org/wiki/Talk:Code_stewardship_reviews/Feedback_solic…
[6] https://www.mediawiki.org/wiki/Talk:Code_stewardship_reviews/Feedback_solic…
[7] https://www.mediawiki.org/wiki/Talk:Code_stewardship_reviews/Feedback_solic…
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **today, Wednesday 4-5 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting: https://www.mediawiki.org/
wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.