Investigation is still underway, but as of the end of Thursday wmf.2 is
only on group0 (testwikis) and group1 (non-'pedias). See the
tracking/blocker task at:
https://phabricator.wikimedia.org/T163512
The issue that caused the revert is being tracked at:
https://phabricator.wikimedia.org/T166345
You can track the status of the wmf.2 rollout via that tracking task
above or by watching https://tools.wmflabs.org/versions/
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-05-24
*= 2017-05-24 =*
== Call outs:==
* Analytics is working on a script for purging EventLogging Mysql (for
those of you who don't expect that, please talk to us :).
contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering
== Reading ==
==== iOS ====
* Last Week
** 5.5 - https://phabricator.wikimedia.org/project/view/2602/
*** Analytics https://phabricator.wikimedia.org/T164801
*** Update `In the news` feed logic and design:
https://phabricator.wikimedia.org/T148739
*** Other bug fixes & enhancements
* This Week
** 5.5 - https://phabricator.wikimedia.org/project/view/2602/
*** Places search updates: https://phabricator.wikimedia.org/T159733
*** Update `Top Read` feed design: https://phabricator.wikimedia.org/T165510
*** Places accessibility: https://phabricator.wikimedia.org/T159733
*** Other bug fixes & enhancements
==== Android ====
* Dmitry, Rita at the hackathon. Mostly a testing and tech debt paydown
week.
* Beta release planned for late this week.
* Current release board:
https://phabricator.wikimedia.org/project/view/2352/
== Wikimedia Deutschland ==
* Very slow week. Many attended the Hackathon in Vienna, many still in
Vienna for WikiCite. This Thursday is a public holiday, Friday typically a
day off.
* Wikidata team makes progress on the Lexeme UI.
=== Analytics ===
* Missed past 2 weeks - Apologies.
* Last week we were in offsite + hackathon (2) - Yearly and preliminary
quarterly goals have been discussed/agreed.
* Ongoing: EventLogging to Hive code is in code review, we should have some
tests soon.
* Vetting Last_access_uniques for global sites (*.wikimedia.org) is taking
us long time because of unexpected data issues.
* We just deployed Event Logging with better bot detection (bot events are
not stored in Mysql anymore).
* Reportcards updated to mark notable data events.
* Pageview data in Druid is now updated hourly (less than 2 hours late).
* Pivot (data visualisation for Druid) is not Opensource anymore, we need
to find a replacement.
* We are working on a script for purging EventLogging Mysql (for those of
you who don't expect that, please talk to us :).
* Druid and pivot currently not working due to upgrade.
=== Technical Operations ===
* Blocking: none
* Blockers: none
* Updates:
** BBR rollout https://phabricator.wikimedia.org/T147569
** Progress on asia DC continues
=== Services ===
* Blockers: none
* NOT ATTENDING. nothing to report due to hackathon and vacations
== Fundraising Tech ==
* More code cleanup and de-duplication as we move stuff from mediawiki
extension to libraries
* Fixing behavior of fraud filters on connection failure
* CentralNotice deployment delayed on oojs-core library dependency, Andrew
Green is talking to editing about a bugfix release
* More Civi integration with third party email house
== Editing ==
=== Language ===
* No blockers/blocking.
* Work on ContentTranslation migration to OOjs UI continue.
=== Parsing ===
* The preprocessor patch that tweaks language variant handling got merged
and is riding the train this week (
https://www.mediawiki.org/wiki/Parsoid/Language_conversion/Preprocessor_fix…
)
* We are ready to pursue using CSS to style Parsoid cite output without
wiki messages (that are used currently for the Cite extension) (
https://phabricator.wikimedia.org/T156351 )
* Linter fixes probably done this week (
https://gerrit.wikimedia.org/r/#/c/350958/ ), and if all goes well, we mght
be able to reenable Linter on large wikis within the next 2 weeks.
* Once this week's train rolls out everywhere, we will be ready to merge
and test Parsoid's red link (and redirect and disambig) support -- if all
goes well, this might land within the next 2 weeks.
=== Collaboration ===
==== Blocking ====
* Coordinating with Ops about a Flow dump issue
==== Blocked ====
==== Updates ====
* Continued work on RC Filters UX, especially regarding namespace filters
* Work on Echo patches at the hackathon
** Notification blacklist to block certain senders from notifying you.
This won't be in production (other than testwiki) anytime soon, but we're
working on getting it ready to test
** Improvements to edit-user-talk notification, to also notify for subpages
=== Discovery ===
* No blockers
* Recovering from Hackaton/offsite/travel
* Working on upgrade to Elastic 5.3
* Working on ML-enabled search ranking infrastructure
=== CommTech ===
* Rolling out LoginNotify to Test Wiki (
https://www.mediawiki.org/wiki/Extension:LoginNotify)
* Fixed bugs in PageTriage extension at Hackathon
* Polishing CodeMirror and getting community feedback (
https://www.mediawiki.org/wiki/Extension:CodeMirror)
* No blockers
Perhaps this would interest some Wikidatans and software developers.
Pine
---------- Forwarded message ----------
From: Michael Maggs <Michael(a)maggs.name>
Date: Wed, May 24, 2017 at 7:58 AM
Subject: [Wikimedia-l] Wikimedia genealogy and historical research software
- a proposal for HRE
To: "Discussion about the Wikimedia genealogy project." <
wikimedia-genealogy(a)lists.wikimedia.org>, Wikimedia Mailing List <
wikimedia-l(a)lists.wikimedia.org>
Cc: John Lubbock <wikimediauk-l(a)lists.wikimedia.org>
There has been quite bit of discussion over the years about how the
Wikimedia movement could engage with those who have research interests in
family history or genealogy, and a centralised discussion page [1] has been
set up on Meta.
I am posting to ask whether there would be Wikimedian developers who would
be interested in joining an open source project to create a free platform
independent application called History Research Environment [2] (‘HRE’) for
the serious genealogist or historical researcher. Considerable effort has
been put into high-level planning over several years, and we are now ready
to start writing code.
While the proposed software is not currently an official Wikimedia project,
if there is enough interest we are open to it becoming integrated or
affiliated in some way. The plan is, in any event, that the software should
be interoperable with Wikidata to allow (subject to the agreement of the
Wikidata community) the exchange of a variety of structured data including
verified and fully sourced family trees.
I'd be happy to answer queries.
Michael Maggs
[1] https://meta.wikimedia.org/wiki/Wikimedia_genealogy_project
[2] https://historyresearchenvironment.org
(please excuse cross-posting for greater visibility, as the
[wikimedia-genealogy] mailing list still has very few subscribers)
_______________________________________________
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wik
i/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
Hi,
I wondered about some things around the Chinese variant conversion:
* When a person uses a search engine, do the links in the results point
directly to one of the variants? That is, does it point to
https://zh.wikipedia.org/zh-cn/Article_name , etc., or simply to
zh.wikipedia.org/wiki/Article_name ? I guess that among Chinese-speaking
people Google is not necessarily as ubiquitous as elsewhere, so there is
probably a separate answer for each search engine.
* If for any search engine the answer above is "yes", does anybody have an
idea about how does that search engine guess the preferred variant? Usage
of simplified / traditional characters in the search query? Geolocation?
Preferred language settings in the browser ("Accept-Language")? Preferences
in the search engine itself? A combination of all of the above? Something
else?
* Does any of the search engine show direct links to country-based variants
- zh-cn, zh-hk, zh-tw, zh-sg, zh-mo? Or to the more generic zh-hans and
zh-hant?
* For users who didn't log in, is the variant selection remembered in a
cookie or in localStorage?
I cannot easily test any of these things myself, because I don't speak
Chinese, I'm not familiar with Chinese search engines, and I don't live in
a Chinese-speaking country (and geolocation matters). But since I care
about language, I'm very curious about this.
Thanks!
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
Forwarding.
Pine
---------- Forwarded message ----------
From: Kirill Lokshin <kirill.lokshin(a)gmail.com>
Date: Sun, May 21, 2017 at 5:41 PM
Subject: [Affiliates] Recognition of the Wikimedia Tool Developers Group
To: Wikimedia Movement Affiliates discussion list <
affiliates(a)lists.wikimedia.org>, Wikimedia Mailing List <
wikimedia-l(a)lists.wikimedia.org>
Hi everyone!
I'm very happy to announce that the Affiliations Committee has recognized
the Wikimedia Tool Developers Group [1] as a Wikimedia User Group. The
group is international cooperative of developers who create freely-licensed
tools for improving the Wikimedia projects.
Please join me in congratulating the members of this new user group!
Regards,
Kirill Lokshin
Chair, Affiliations Committee
[1] https://meta.wikimedia.org/wiki/Wikimedia_Tool_Developers_Group
_______________________________________________
Affiliates mailing list
Affiliates(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/affiliates
We just completed another great Wikimedia Hackathon with a ton of great
work happening across many different areas and projects.
>From a release engineering perspective this can also be a bit scary :).
The normal 'train' deployment is scheduled for this week starting
Tuesday May 23rd (per usual).
However, we request that due to the large variance of changes going out
this week please be on the alert and let us know if you see anything out
of the ordinary.
How? We (Release Engineering) have a tracking task per weekly deploy.
This week's is: https://phabricator.wikimedia.org/T163512
Comment on that task or add a subtask to it to indicate a blocker. We'll
respond accordingly. As you can see there's also a number of blockers
being tracked.
Thank you,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
**** DEADLINE EXTENSION****
Due to several requests the SEMANTiCS 2017 conference extends its
submission deadlines.
3rd Call for Research & Innovation Papers
SEMANTiCS 2017 - The Linked Data Conference
13th International Conference on Semantic Systems
Amsterdam, Netherlands
September 11 -14, 2017
http://2017.semantics.cc
The Research & Innovation track at SEMANTiCS welcomes the submission of
papers on novel scientific research and/or innovations relevant to the
topics of the conference. Submissions must be original and must not have
been submitted for publication elsewhere. Papers should follow the ACM
ICPS guidelines for formatting
(http://www.acm.org/sigs/publications/proceedings-templates) and must
not exceed 8 pages in lenght for full papers and 4 pages for short
papers, including references and optional appendices.
Research & Innovation Papers are published within ACM ICP Series.
Important Dates (Research & Innovation)
* Abstract Submission Deadline: extended: May 31, 2017 (11:59
pm, Hawaii time)
* Paper Submission Deadline: extended: June 7, 2017
(11:59 pm, Hawaii time)
* Notification of Acceptance: July 3, 2017 (11:59 pm,
Hawaii time)
* Camera-Ready Paper: August 14, 2017 (11:59 pm,
Hawaii time)
For details please go to: https://2017.semantics.cc/calls
or contact the Research and Innovation Chairs:
Catherine Faron Zucker, faron [@] i3s.unice.fr, Université Nice Sophia
Antipolis
Rinke Hoekstra, rinke.hoekstra [@] vu.nl, Vrije Universiteit
Amsterdam/University of Amsterdam
As in the previous years, SEMANTiCS’17 proceedings will be published by
ACM ICP (pending).
SEMANTiCS 2017 will especially welcome submissions for the following hot
topics:
* Data Science (special track, see below)
* Web Semantics, Linked (Open) Data & schema.org
* Corporate Knowledge Graphs
* Knowledge Integration and Language Technologies
* Data Quality Management
* Economics of Data, Data Services and Data Ecosystems
Following the success of previous years, the ‘horizontals’ (research)
and ‘verticals’ (industries) below are of interest for the conference:
Horizontals
* Enterprise Linked Data & Data Integration
* Knowledge Discovery & Intelligent Search
* Business Models, Governance & Data Strategies
* Semantics in Big Data
* Text Analytics
* Data Portals & Knowledge Visualization
* Semantic Information Management
* Document Management & Content Management
* Terminology, Thesaurus & Ontology Management
* Smart Connectivity, Networking & Interlinking
* Smart Data & Semantics in IoT
* Semantics for IT Safety & Security
* Semantic Rules, Policies & Licensing
* Community, Social & Societal Aspects
Data Science Special Track Horizontals
* Large-Scale Data Processing (stream processing, handling large-scale
graphs)
* Data Analytics (Machine Learning, Predictive Analytics, Network Analytics)
* Communicating Data (Data Visualization, UX & Interaction Design,
Crowdsourcing)
* Cross-cutting Issues (Ethics, Privacy, Security, Provenance)
Verticals
* Industry & Engineering
* Life Sciences & Health Care
* Public Administration
* e-Science
* Digital Humanities
* Galleries, Libraries, Archives & Museums (GLAM)
* Education & eLearning
* Media & Data Journalism
* Publishing, Marketing & Advertising
* Tourism & Recreation
* Financial & Insurance Industry
* Telecommunication & Mobile Services
* Sustainable Development: Climate, Water, Air, Ecology
* Energy, Smart Homes & Smart Grids
* Food, Agriculture & Farming
* Safety, Security & Privacy
* Transport, Environment & Geospatial
For details please go to: https://2017.semantics.cc/calls