Hi,
texvc is a OCaml program that generates PNG images for the Math
extension. Packages for Debian and Ubuntu are now available, please see
<https://www.mediawiki.org/wiki/User:Legoktm/Packages/texvc> for more
details.
This package is useful regardless of whether you are using the mediawiki
package or not - it allows you to use texvc without needing to install
the full OCaml toolchain to build it manually.
Finally, in the long term the Math extension maintainers would like to
phase out texvc in favor of the mathoid-based code. If you do use texvc
(packaged or not), your comments on
<https://phabricator.wikimedia.org/T155201> would be appreciated.
-- Legoktm
Hi,
This shouldn't affect very many installations as CentralAuth is very
WMF-specific but letting everyone know that a fix for CentralAuth has just
been released.
It allowed user impersonation by a combination of the apioutput.js (used
for api.php output customization) and the central auth cookie.
The bug is: https://phabricator.wikimedia.org/T144573
The gerrit change is: https://gerrit.wikimedia.org/r/#/c/333316/
-Chad
Russian Wikipedia just replaced all of their map links in the upper right
corner (geohack) with the <maplink> - Kartographer extension! Moreover,
when clicking the link, it also shows the location outline, if that object
exists in OpenStreetMap, using corresponding Wikidata ID. My deepest
respect to my former Interactive Team colleagues and volunteers who have
made it possible! (This was community wishlist #21)
Example - city of Salzburg (click coordinates in the upper right corner, or
in the infobox):
https://ru.wikipedia.org/wiki/%D0%97%D0%B0%D0%BB%D1%8C%D1%86%D0%B1%D1%83%D1…
Forwarding from WikimediaAnncounce-l to Wikimedia-l because auto-foward is
still not working. Also forwarding to Wikitech-l and MediaWiki-l because
the "Reconstructing MediaWiki history" presentation sounds like it may be
of interest to some people on those lists.
Pine
---------- Forwarded message ----------
From: Lena Traer <ltraer(a)wikimedia.org>
Date: Thu, Jan 19, 2017 at 4:41 PM
Subject: [Wikimedia Announcements] Invitation to WMF January 2017 Metrics &
Activities Meeting: Thursday, January 26, 19:00 UTC
To: wikimediaannounce-l(a)lists.wikimedia.org
Hello everyone,
The next Wikimedia Foundation metrics and activities meeting will take
place on Thursday, January 26, 2017 at 7:00 PM UTC (11 AM PST). The IRC
channel is #wikimedia-office on irc.freenode.net, and the meeting will be
broadcast as a live YouTube stream.
The theme of the January meeting is: "Building our future” – Exploring how
we can build for the future of the Wikimedia movement together.
Meeting agenda:
* Welcomes, theme introduction
* Movement update
* Reconstructing MediaWiki history
* Community capacity development
* Executive update
* Questions and discussion
* Wikilove
Please review
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_metrics_and_activities_
meetings
for further information about the meeting and how to participate.
We’ll post the video recording publicly after the meeting.
Thank you,
Lena
Lena Traer
Project Assistant // Communications // Advancement
Wikimedia Foundation
149 New Montgomery Street
San Francisco, CA 94105
_______________________________________________
Please note: all replies sent to this mailing list will be immediately
directed to Wikimedia-l, the public mailing list of the Wikimedia
community. For more information about Wikimedia-l:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
_______________________________________________
WikimediaAnnounce-l mailing list
WikimediaAnnounce-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikimediaannounce-l
Hallo Wikitech community,
Remind me please, were there ever any efforts to get client-side JavaScript
errors monitored centrally?
What happens currently is that JS code can frequently fail, taking down the
rest of JS on the page with it. It happens both with JS code properly
deployed from Gerrit and loaded by RL, but even more so with local gadgets,
Common.js, and user scripts.
The most frequent effects of this into which I ran are Visual Editor not
working at all and WikiEditor's toolbar not appearing in the source editing
window. There are many more.
On projects with a lot of editors and administrators, like the English and
the German Wikipedia, this will probably be quickly noticed and
fixed—sometimes fixed locally, and sometimes fixed in Gerrit and deployed
in SWAT. But in smaller projects it can fail for months without being
noticed. And when I say "smaller", I don't mean the tiny projects with
almost no editors—such a thing happened recently in the Japanese Wikipedia,
a top-10 project, and I helped administrators there to fix the buggy code,
which appeared in the second most-popular gadget.
I did this dozens of times, and Krinkle probably does this even more than
me. Often admins from different projects help each other, and it is great
that we have this mutual help in the community, but aren't there better
ways to catch such errors?
I remember there were discussions about this, but I don't remember what was
the outcome.
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
tl;dr: I have removed the Tuesday 19:00 UTC SWAT window from the
deployment calendar due to conflicts. Pick one of the other 11 SWAT
windows.
The (current) Tuesday 19:00 UTC SWAT window is directly before the 20:00
UTC MediaWiki train window.
The nature of SWAT windows meant that the state of the deployed
MW+Extension+Config code was changing while the creation of the new MW
train version (eg: 1.29-wmf.8) was happening. This causes delays and
confusion.
The simple solution is to not have a normal SWAT window at that time.
Other deploys (eg Services) are fine to happen at that time which is why
I didn't just extend the MW train window to include that earlier hour.
Luckily, you still have 11 SWAT windows to choose from. :)
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
Hello,
Continuing the storage redundancy and reliability efforts for Labs (
https://phabricator.wikimedia.org/T126083), the final migration to the new
NFS storage cluster for Labs projects with NFS enabled is upcoming. The
migration is planned to happen 2017-01-18 starting 09:00 PST(16:00 UTC).
This *does not* affect tools, maps or any other projects that don't have
/home or /data/project mounted. The migration window is expected to be
fairly short (<3 hours) - but could last up to 6 hours.
During the migration, no new data will be written to NFS (/home or
/data/project), but existing data will be accessible in Read-only mode for
the most part. Post migration, any services or jobs that were running on
top of NFS (/home or /data/project) will require manual restarts. Jobs
running on top of /scratch or /public/dumps will be unaffected. I will keep
the lists and #wikimedia-labs updated on progress during and after the
migration.
The list of labs projects that will be affected in this migration are:
- catgraph
- account-creation-assistance
- contributors
- wikidata-topicmaps
- sugarcrm
- wikidumpparse
- video
- openstack
- testlabs
- wikidata-dev
- quarry
- huggle
- editor-engagement
- utrs
- wmt
- cvn
- fastcci
- toolsbeta
- project-proxy
- dumps
- bots
- snuggle
- math
- wikisource-tools
The tracking task on phabricator is here -
https://phabricator.wikimedia.org/T154336. Let us know if you have any
questions or concerns on the list or on #wikimedia-labs.
--
Madhu Viswanathan
Operations Engineer, Wikimedia Labs
Hi all!
Here are the minutes from this week's ArchCom meeting. You can also find the
minutes at <https://www.mediawiki.org/wiki/Architecture_committee/2017-01-18>.
See also the ArchCom status page at
<https://www.mediawiki.org/wiki/Architecture_committee/Status> and the RFC board
<https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>.
Here are the minutes, for your convenience:
* 2 RFCs approved after final call: Deprecation Policy
([[Phab:T146965|T146965]]) and Content Model Storage ([[Phab:T105652|T105652]]).
* Multi-Content-Revisions (MCR, [[Phab:T107595|T107595]]) discussed at
DeveloperSummit. Sorted out details of the DB schema with Jaime.
* Ongoing discussion regarding distribution methods for MediaWiki and suppor for
3rd party installs.
** Related discussion about whether new features can require services serparate
from MediaWiki core.
* Thumbnail API is mostly stalled for now [[Phab:T66214|T66214]].
* Oldimage RFC ([[Phab:T589|T589]]) to go on final call this week.
** Decided to keep media type and mime type fields for now. Thy are small, and
now exposed via Cirrus Search; if we removed them from the table, they would
need to love somewhere else. Also they are enums, and thus small.
** Tentative plan to fold image revision management into MCR at some point, but
not until MCR is mature. Also, this schema change will make a later migration to
MCR much easier.
* ArchCom is considering changes to the RFC process. Discussion is ongoing. Key
points:
** More focus on discussion in Phabricator
** More leight weight process for “small” RFCs
** ArchCom to focus more on review, less ond process
** IRC meeting should not be the primary tool for discussing and approving RFCs
* Next week’s IRC discussion: [[Phab:T154738|T154738]] (Accessing page
properties from wiki pages). Related:
** T71441: Feature request: add detection for disambiguation pages to Scribunto
** T131911: Allow retrieving/getting page image file name from wikitext using
Scribunto/Lua or parser function or something
** T154346: Provide "wikitext" means of accessing arbitrary wiki page's default
category sort key
--
Daniel Kinzler
Principal Platform Engineer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-01-18
= 2017-01-18 =
== Product ==
=== Reading ===
==== Mobile Content Service (MCS) ====
* Board: https://phabricator.wikimedia.org/project/board/1323/query/open/
* Working on:
** Clicking on references is broken (Broken in the Android app; a Parsoid
change caused this) https://phabricator.wikimedia.org/T155070
** Improving regression testing
====Android====
* Last week:
** Dev summit and all hands
** Start on improving offline support quarterly goal
** New account creation broken in API 25 T155535
** Investigate reverted edit notifications failure
* Next week (https://phabricator.wikimedia.org/project/view/2352/ ):
** Work towards release of Wikidata description editing
** Continue on improved offline experience
==== iOS native app ====
* Last Week
** Dev summit, All hands, released 5.3.4 -
https://phabricator.wikimedia.org/project/view/2396/
** Continued work on 5.4 -
https://phabricator.wikimedia.org/project/view/2326/
* This week
** Continue work on 5.4 - Places, Login enhancements
https://phabricator.wikimedia.org/project/view/2326/
==== Web ====
* Last week:
** Dev summit and all hands
** Current sprint:
https://phabricator.wikimedia.org/tag/reading-web-sprint-89-%F0%9F%8E%82/
* Next sprint: https://phabricator.wikimedia.org/project/view/2426/
** Deploy Wikidata description and Related Articles on enwiki mobile
=== Editing ===
==== Collaboration ====
* Blocked -
* Blocking -
* Updates
** Main patch for RecentChanges page UI finished and merged (Adding new
interface for review filters to RecentChanges).
** Add userExpLevel filter in the RCFilters UI
** Continuing related work to this, including backend.
** Some meetings at Dev Summit about ReviewStream (part of Edit Review
Improvements) and WikiLabels admin interface
** Flow consistency fixes
== Technology ==
=== Analytics ===
Updates:
* Continuing with the work to replace front end and backend of
http://stats.wikimedia.org : Wikistats 2.0, a mjor development is that
we will be able to import the edit history from labs rather than prod dbs,
huge advantage as this data is redacted and already public.*
* Working on launching RCStream replacement, review stream plus several
other real time streams. Will start working with collaboration
on augmented ORES recent changes stream.
* Started work on processing user_agent field on eventlogging tables, it
will be a json string like {"OS_Family": "Windows",
"Browser_family":"Chrome"....}
* Found issue with Heap on cluster, set up alarms, will be solved with
update to cloudera's newest
* Still waiting for hardware for pageview API, getting closer
=== Release Engineering ===
* '''Bocked'''
** None
* '''Blocking'''
** None?
* '''Updates'''
** Deployment is back to normal, train is on schedule:
https://tools.wmflabs.org/versions/
** Scap 3.5 release eminent, changelog will be sent, check on beta please
=== Services ===
* Blockers: none
* Updates:
** Node 6 upgrade is coming: https://phabricator.wikimedia.org/T149331
*** RESTBase updated, great improvement in memory consumption
*** Parsoid today
*** SCB tomorrow
*** MCS, CXServer, EventStreams - if you have something to deploy - do
it TODAY!
=== Discovery ===
* No blockers
* Continuing work on crosswiki searches
* Special:Search refactoring merged in
* Started work on improving wikidata search
* Started preparing for upgrade to ElasticSearch 5
* Added app links to portal homepage
== German Technical Wishlist ==
* Collecting what we learned at the Dev Summit
* Decided to not render URLs in the Electron PDF export any more
https://phabricator.wikimedia.org/T152393
* Can we help investigating why Kartographer does not work with flagged
revs, to support German Wikipedia? https://phabricator.wikimedia.org/T151665
== Wikidata ==
* Slow week, key people are still in the US
* Currently focusing on backend services for federation ("Wikidata on
Commons") https://phabricator.wikimedia.org/T76007
== Fundraising Tech ==
* CentralNotice banner impressions in pivot:
https://pivot.wikimedia.org/#banner-impressions-hourly
* More work to prevent unintended duplicate donations
* More CiviCRM customization moved to a real Civi extension
* Easing import of employer matching gifts
* Examining contractor fileshare change
* Casey training on ops-y stuff with Jeff and preparing to announce a job
opening