Hey everyone,
apologies for the cross-posting, we're just too excited:
we're looking for a new member for our team [0], who'll dive right away in
the promising Structured Data project. [1]
Is our future colleague hiding among the tech ambassadors, translators,
GLAM people, community members we usually work with? We look forward to
finding out soon.
So please, check the full job description [2], apply, or tell/recommend
anyone who you think may be a good fit. For any questions, please contact
me personally (not here).
Thanks!
Elitre (WMF)
Senior Community Liaison, Technical Collaboration
[0] https://meta.wikimedia.org/wiki/Community_Liaisons
[1] https://commons.wikimedia.org/wiki/Commons:Structured_data
[2]
https://boards.greenhouse.io/wikimedia/jobs/610643?gh_src=o3gjf21#.WMGV0Rih…
Hey all,
TL;DR: In April 2017, the jQuery library in MediaWiki was upgraded from 1.x
to 3.x (the current stable version), with the jQuery Migrate plugin enabled
to
ease migration. We temporarily still load jQuery 1.x on Wikimedia wikis.
Read about the API changes at https://jquery.com/upgrade-guide/3.0/
== Upgrade guide ==
An overview of the important changes is available at:
https://jquery.com/upgrade-guide/3.0/
This page also contains advice on how to migrate your code. In most cases
it involves fairly
simple changes, such as using a different method name, or adding quotes in
selectors.
The vast majority of the added requirements and removed methods are
restored through
the jQuery Migrate plugin with a deprecation warning in the console. As
such, it's unlikely
your code will require any immediate changes.
If you do find a deprecation warning in the console, you can use the
warning documentation
to find out more:
https://github.com/jquery/jquery-migrate/blob/e967c3b98b/warnings.md
Once jQuery 3 is in Wikimedia production (with jQuery Migrate) it will be
easy to
find uses of deprecated methods with the deprecation warnings. However, you
don't
need to wait for August to start migrating. The methods removed in jQuery 3
have
been deprecated for a while already, and their replacements are already
available
in jQuery 1.x in production, today.
== Timeline ==
* April 2017: jQuery 3 lands in MediaWiki core master with jQuery Migrate
plugin.
* April to July 2017: Testing and fixing of issues arising from the switch.
* July 2017: jQuery 3 enabled in Wikimedia's Beta Cluster. [1]
* August 2017: jQuery 3 enabled on Wikimedia wikis in production.
jQuery 3 will also be released as part of MediaWiki 1.30.0 (expected in
November 2017). [2]
As part of MediaWiki 1.30, inclusion of jQuery Migrate will made
configurable so that sites
that have already migrated may disable the plugin for better run-time
performance.
Track progress at <https://phabricator.wikimedia.org/T124742>.
-- Krinkle
[1] https://www.mediawiki.org/wiki/Beta_Cluster
[2] https://www.mediawiki.org/wiki/MediaWiki_1.30
Hi all,
as an update on the changes I flagged last month:
there are still several articles that need to be fixed, including some on
big wikis.
We put a lot of explanations and details at mediawiki.org.
Among the most affected wikis:
*Arab, Russian, Ukrainian, Farsi, Serbo-Croatian Wikipedias...*
*What does "broken" look like?*
https://phab.wmfusercontent.org/file/data/qkhxzdqawssnkcanzfdp/PHID-
FILE-gtxssxmfuhlxo23xqcgo/Broken_article_after_preprocessor_change
(infobox exposing syntax in view mode; you may need to purge the cache to
actually be able to see the issue live in some articles.)
*How to check and fix:*
See the *latest list *at https://www.mediawiki.org/wiki/Parsoid/Language_
conversion/Preprocessor_fixups/20170620 , then head to
https://www.mediawiki.org/wiki/Parsoid/Language_conversion/Preprocessor_
fixups#How_to_fix for *instructions*. When actually necessary, fixes are
fast and easy (speaking for personal experience). False positives are
possible. Tools-assisted fixing is also possible (AutoWikiBrowser has been
used to that effect); please ask if you need assistance with that.
*A note about communications:*
Throughout the year, the Parsing team will make several changes that will
require kind community assistance. So far, the preprocessor one looks quite
successful, with several volunteers coming to the rescue (thanks again!).
There have been multiple mentions and updates in Tech News, emails, Village
Pump announcements, talk pages at mw.org, Phabricator... most fixes are
done, and the remaining fixes to be done do not justify additional
communication effort. As said before, other breaking changes will occur in
time (which may affect way more pages), and over-communicating risks to
distract and confuse helpful volunteers.
This means you are welcome to communicate with the team directly at
https://www.mediawiki.org/wiki/Talk:Parsoid/Language_
conversion/Preprocessor_fixups , but shouldn't expect any more nudges on
this specific project, as we prepare to communicate about others (and the
current workflow is probably too heavy and time-consuming to be applied to
each and every of such changes). If you have feedback about current and
future communications strategy, we are looking forward to hearing from you
at https://meta.wikimedia.org/wiki/Talk:Technical_Collaboration.
Thank you!
Elitre (WMF)
https://meta.wikimedia.org/wiki/Technical_Collaboration
Hi everybody,
(With apologies for cross-posting...)
You may have seen the recent communication [1
<https://www.mediawiki.org/wiki/Wikimedia_Engineering/June_2017_changes>]
about the product and tech tune-up which went live the week of June 5th,
2017. In that communication, we promised an update on the future of
Discovery projects and we will talk about those in this email.
The Discovery team structure has now changed, but the new teams will still
work together to complete the goals as listed in the draft annual plan.[2]
A summary of their anticipated work, as we finalize these changes, is
below. We plan on doing a check-in at the end of the calendar year to see
how our goals are progressing with the new smaller and separated team
structure.
Here is a list of the various projects under the Discovery umbrella, along
with the goals that they will be working on:
Search Backend
Improve search capabilities:
-
Implement ‘learning to rank’ [3] and other advanced machine learning
methodologies
-
Improve support for languages using new analyzers
-
Maintain and expand power user search functionality
Search Frontend
Improve user interface of the search results page with new functionality:
-
Implement explore similar [4]
<https://www.mediawiki.org/wiki/Cross-wiki_Search_Result_Improvements/Testin…>
-
Update the completion suggester box [5]
<https://www.mediawiki.org/wiki/Extension:CirrusSearch/CompletionSuggester>
-
Investigate the usage of a Wiktionary widget for English Wikipedia [6]
Wikidata Query Service
Expand and scale:
-
Improve ability to support power features on-wiki for readers
-
Improve full text search functionality
-
Implement SPARQL federation support
Portal
Create and implement automated language statistics and translation updates
for Wikipedia.org
Analysis
Provide in-depth analytics support:
-
Perform experimental design, data collection, and data analysis
-
Perform ad-hoc analyses of Discovery-domain data
-
Maintain and augment the Discovery Dashboards,[7] which allow the teams
to track their KPIs and other metrics
Maps
Map support:
-
Implement new map style
-
Increase frequency of OSM data replication
-
As needed, assist with individual language Wikipedia’s implementation of
mapframe [8] <https://www.mediawiki.org/wiki/Maps/how_to:_embedded_maps>
Note: There is a possibility that we can do more with maps in the coming
year; we are currently evaluating strategic, partnership, and resourcing
options.
Structured Data on Commons
Extend structured data search on Commons, as part of the structured data
grant [9] via:
-
Research and implement advanced search capabilities
-
Implement new elements, filters, relationships
Graphs and Tabular Data on Commons
We will be re-evaluating this functionality against other Commons
initiatives such as the structured data grant. As with maps, we will
provide updates when we know more.
We are still working out all the details with the new team structure and
there might be some turbulence; let us know if there are any concerns and
we will do our best to answer them.
Best regards,
Deborah Tankersley, Product Manager, Discovery
Erika Bjune, Engineering Manager, Search Platform
Jon Katz, Reading Product Lead
Toby Negrin, Interim Vice President of Product
Victoria Coleman, Chief Technology Officer
[1] https://www.mediawiki.org/wiki/Wikimedia_Engineering/June_2017_changes
[2]
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/…
[3] https://en.wikipedia.org/wiki/Learning_to_rank
[4]
https://www.mediawiki.org/wiki/Cross-wiki_Search_Result_Improvements/Testin…
[5]
https://www.mediawiki.org/wiki/Extension:CirrusSearch/CompletionSuggester
[6]
https://www.mediawiki.org/wiki/Cross-wiki_Search_Result_Improvements/Testin…
[7] https://discovery.wmflabs.org/
[8] https://www.mediawiki.org/wiki/Maps/how_to:_embedded_maps
[9] https://commons.wikimedia.org/wiki/Commons:Structured_data
---------- Forwarded message ----------
From: "Aaron Halfaker" <aaron.halfaker(a)gmail.com>
Date: Jun 12, 2017 12:00 PM
Subject: [AI] ORES operating at slightly reduced capacity
To: "Application of Artificial Intelligence and other advanced computing
strategies to Wikimedia Projects" <ai(a)lists.wikimedia.org>
Cc:
One of our worker nodes in CODFW went down (scb2005). See
https://phabricator.wikimedia.org/T167638 for details.
This should not affect the service except that we'll have a slightly
reduced capacity to handle high request rates. Let us know if you see any
issues with ORES.
https://ores.wikimedia.orghttps://mediawiki.org/wiki/ORES
-Aaron
_______________________________________________
AI mailing list
AI(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/ai