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 all,
This change might impact people who run tools based on the *patrolling
status of edits*. This could also be relevant for admins. Feel free to
share with your local communities.
Currently, MediaWiki is storing the information about if an edit has been
patrolled or autopatrolled in the logging table. This table is getting very
very big, causing significant infrastructure issues.
Therefore, we plan to make the following changes:
- Stop adding new entries for autopatrolling to the logging table
- Remove the old entries for autopatrolling from this table
- Since the distinction between autopatrol and manual patrol was
introduced in April of 2016, We need to remove every patrol action (manual
or not) before that date.
- Include information about autopatrolled in the recentchanges table.
The fields rc_patrolled is current 0 for unpatrolled edits, and 1 for
patrolled edits. In the future, it will be 0 for unpatrolled, 1 for
manually patrolled, and 2 for autopatrolled edits.
This means that the information about if an edit is autopatrolled, will be
accessible *only in the Recent Changes table, for 30 days*. For now, manual
patrolling actions will continue to be recorded in the logging table as
before, and will remain visible on Special:Log. More details can be found
in the technical RFC document, see phab:T184485
<https://phabricator.wikimedia.org/T184485>.
We plan to deploy these changes on April 4th. The script removing patrol
actions in the database may take several weeks to run.
If you’re maintaining a tool using logging.log_action = "autopatrolled",
please consider changing your code to use recentchanges.rc_patrolled = 2.
If this is going to cause large issues for an important tool, please let us
know.
If you have any technical question, feel free to write to user:Ladsgroup
<https://www.wikidata.org/wiki/User:Ladsgroup>.
--
Léa Lacroix
Project Manager Community Communication for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
Hi mobile-l and wikitech-ambassadors friends!
Rita shared with colleagues a cool diagram of the Wikipedia for Android app
flows, and we thought you may be interested to see it as well. Here you go:
https://commons.wikimedia.org/wiki/File:Wikipedia_Android_app_workflow_-_Fe…
-Adam
---------- Forwarded message ----------
From: Rita Ho <rho(a)wikimedia.org>
Date: Fri, Mar 2, 2018 at 9:05 AM
Subject: Friday freebie - updated Android app diagram
Hi folks,
I recently updated the diagram of the Android app, which gives an overview
of all the major flows in the app (including somewhat 'hidden' editing and
article interaction features).
Thought I'd share with the wider team as it enables a quick glance of the
current state of the app for those who don't have it readily available on a
device.
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 everyone,
On behalf of the Parsing Team @ the WMF, I am announcing our plans to
replace Tidy with Remex on the next set of wikis.
On March 13th, we plan to turn off Tidy on about 100 wikis that have
fewer than 25 issues in all high-priority linter categories [1].
On March 14th, we plan to turn off Tidy on mzn, ko, nl, war, ceb
wikipedias [2].
Later in the month, probably March 20th, we plan to turn off Tidy on all
wikiversities [3] and wikimedia chapter / user group wikis [4]. This
step requires a bit more investigation to identify if all those wikis
are ready for the switch.
In February, we replaced Tidy on all wikinews wikis [5], private wikis
[6], and a bunch of miscellaneous wikis [7]. Once we are done with this
round in March, about 600 wikis on the wikimedia cluster would have had
Tidy replaced. We plan to complete this switch on all wikis (about 900)
by July 2018.
If you have any questions or concerns, please leave a comment on the
associated phabricator tickets or leave a message on mw.org [8].
Thanks,
Subbu.
[1] https://phabricator.wikimedia.org/T188010
[2] https://phabricator.wikimedia.org/T188869
[3] https://phabricator.wikimedia.org/T188880
[4] https://phabricator.wikimedia.org/T188881
[5] https://phabricator.wikimedia.org/T188000
[6] https://phabricator.wikimedia.org/T188009
[7] https://phabricator.wikimedia.org/T188008
[8] https://www.mediawiki.org/wiki/Help_talk:Extension:Linter
Hello,
If you're not active community member in these wikis, feel free to ignore
this message:
arwiki, bgwiki, iawiki, idwiki, kuwiki, mywiki, ptwiki, thwiki, viwiki,
zhwiki
Because of an old Lua module in these wikis, they are actually checking for
all statements of items and that makes them receive too many notifications
for edits that are happening from Wikidata. There is a ticket that explains
the situation in more depth: https://phabricator.wikimedia.org/T178114
I wrote an script and fixed it everywhere possible except in these wikis
where the Wikidata module is protected. It would be great if you fix this
performance issue in these cases or reach out to people who can: This is an
example of what we did to fix English Wikipedia:
https://en.wikipedia.org/w/index.php?title=Module:Wikidata&diff=816019402&o…
Any help would be really appreciated.
Thanks!