Hi,
in the query examples at
https://www.mediawiki.org/wiki/Wikidata_Query_Service/User_Manual/MWAPI#Fin…
,
the way to search for "cheese" is
<code>
bd:serviceParam mwapi:search "cheese" .
</code>
What if the search string I want to use is a composite, e.g. "goat cheese"?
I have tried single quotes, escaping the quotes, and replacing the
spaces with plus signs, but non of these would guarantee that the
search results only contain the search string (plus some grammatical
variations) and not things like "This cheese was made from goat milk".
Any pointers would be appreciated.
Thanks,
Daniel
Hello again,
This is the weekly update from the Search Platform team for the weeks
starting 2018-07-02 and 2018-07-09.
Programming Note: With the Wikimania Hackathon, Wikimania proper, and
resulting travel for folks in coming weeks, the next update will be
for the week starting 2018-07-30.
As always, feedback and questions welcome.
== Discussions ==
=== Search ===
* David and Stas worked on fine tuning of search configs to
mediawiki-config for Wikidata [0]
* Stas and Addshore helped to catch and clean up some bad lookups and
report them properly [1]
* A "Wrong document type" error was corrected by Erik by fixing
Sanitizer MetaStore integration [2]
* Erik worked on tracking queries that run on the Elastic Search
clusters longer than both server side and client side timeouts by
fixing some slow logging functionality [3]
* There was a Meta-wiki error where search suggests non-existent title
due to namespace/redirect mixup. Erik's note: "it's a bit awkward, but
typing Help:Glo into autocomplete on metawiki suggests 'Global
Account' from the main namespace, and selecting it takes you to
Help:Unified login" [4]
* In order to dispatch queries to a particular search setup (cirrus
defaults vs wikibase custom query builder), David created a flexible
way to classify queries, meant to replace the 'getSyntaxUsed' approach
currently in SearchContext. [5]
* Trey and a community volunteer, Athena, created a basic Mirandese
analysis chain. It was tested on RelForge and pushed into production
this week [6]. Trey kicked off, completed and tested the re-indexing
of the Mirandese Wikis [7].
* The Re-Re-Index of the Serbian Wikis after refactored plugins were
deployed has been completed [8] and the re-index of the Croatian,
Serbo-Croatian, and Bosnian Wikis was also done [9]
* We currently mix a tiny number of namespace documents into the
regular indices, which seems inefficient; so Erik built a unified
namespace index [10]
* Erik updated the 'OtherIndex' to operate on a cluster other than the
one holding the wiki [11]
* Trey updated a variety of things on the Analysis Tools with lots
little fixes and improvements as well as a few small errors in the
analysis code that conflated post-analysis types and pre-analysis
types [12]
== Did you know? ==
* The period of this status update includes Friday, July 13, 2018. The
fear of the number thirteen is called "triskaidekaphobia" [13]. There
are two words for fear of Friday the 13th: "paraskavedekatriaphobia"
[14] and "friggatriskaidekaphobia" [15]—the first maintains a
consistent etymology with the Greek word for Friday, "Paraskeví",
while the second invokes "Frigg", the Norse Goddess after whom Friday
is named in English.
[0] https://phabricator.wikimedia.org/T182717
[1] https://phabricator.wikimedia.org/T198091
[2] https://phabricator.wikimedia.org/T197446
[3] https://phabricator.wikimedia.org/T196180
[4] https://phabricator.wikimedia.org/T115756
[5] https://phabricator.wikimedia.org/T197774
[6] https://phabricator.wikimedia.org/T194941
[7] https://phabricator.wikimedia.org/T197890
[8] https://phabricator.wikimedia.org/T196404
[9] https://phabricator.wikimedia.org/T196658
[10] https://phabricator.wikimedia.org/T192699
[11] https://phabricator.wikimedia.org/T194678
[12] https://phabricator.wikimedia.org/T199273
[13] https://en.wiktionary.org/wiki/triskaidekaphobia
[14] https://en.wiktionary.org/wiki/paraskavedekatriaphobia
[15] https://en.wiktionary.org/wiki/friggatriskaidekaphobia
---
Subscribe to receive on-wiki (or opt-in email) notifications of the
Discovery weekly update.
https://www.mediawiki.org/wiki/Newsletter:Discovery_Weekly
The archive of all past updates can be found on MediaWiki.org:
https://www.mediawiki.org/wiki/Discovery/Status_updates
Interested in getting involved? See tasks marked as "Easy" or
"Volunteer needed" in Phabricator.
[1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R
[2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R
Yours,
Chris Koerner
Community Relations Specialist
Wikimedia Foundation
Hello all,
we’re happy to launch the Season of RevisionSlider - and very happy to
invite you in!
Are you a volunteer developer with JavaScript and jQuery skills?*
And interested in:
- working in a team for a limited period of time?
- a project that is nice to work on, with a clear scope and different
small tasks?
- contributing to a MediaWiki extension that is deployed to all
Wikimedia wikis?
- helping to develop the version 2.0 of the RevisionSlider?
Do you have a bit of time *from beginning of August to end of September
2018*?
Then you might be the perfect fit for joining the Season of RevisionSlider
:-)
About the feature
The RevisionSlider is a MediaWiki extension, developed bei Wikimedia
Deutschland’s Technical Wishes team. It adds a slider to the diff page that
allows to easily navigate through revisions. The feature got developed in
2016/2017, and is a default feature on all wikis since May 2017. [1]
About Season of RevisionSlider:
Implementing version 2.0
The work on a feature doesn’t stop in the moment it is deployed everywhere.
It needs to be maintained, and continuous user feedback helps identifying
new use cases that the feature could ideally address on top. We think it is
time for realizing version 2.0 of the feature: Including general
improvements and a few new features - for example, highlighting all edits
of the same user.
Why a Volunteer Dev team
Finding good tasks to work on, getting people to review your patches, or
just getting good advice can be very challenging. With *Season of
RevisionSlider* we want to provide the chance to experience all of this the
easy way - together with us :-)
How to join
We are looking for 4-5 people who would be interested to work as a
development team over a period of 2 months. The team will be supported by a
group of engineers, product management, design and communication. We
plan a *kick-off
meeting* via video call on *Thursday, August 2, 15:00 UTC* (so save the
date!), and will continue with weekly check-ins until end of September.
If you are interested, please let us know by July 26. Just subscribe to the
ticket & say Hi!
https://phabricator.wikimedia.org/T199556
If you have any questions, please comment directly in the ticket.
We’re really looking forward to meeting you :-)
See you soon,
Birgit (for WMDE’s Technical Wishes Team)
* PHP basic skills and a basic understanding of CSS are nice to have, but
it can work without
[1] https://www.mediawiki.org/wiki/Extension:RevisionSlider
--
Birgit Müller
Community Communications Manager
Software Development and Engineering
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.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
If you ran eslint (JavaScript codestyle linter) recently (it was only
compromised for an hour), your npm token might have been compromised
(~/.npmrc).
To identify if you were compromised, run:
$ locate eslint-scope | grep -i "eslint-scope/package.json" | xargs jq
.version
And if any of those show "3.7.2" then you have the bad package version
installed.
Upstream recommends that you 1) reset your npm token and 2) enable 2fa
for npm - both can be done from the npm website. You should probably
also check to make sure none of your packages were compromised.
There are some more details on the bug report[1].
[1]
https://github.com/eslint/eslint-scope/issues/39#issuecomment-404533026
- -- Legoktm
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAltHdC0ACgkQUvyOe+23
/KJpBg//WXBSPKhjmZd43KrHu07NsasWvrU/SAOeBtKjdaLTA3Ry5N+Fdh7LUFFk
oEm1rnz6AnfW0LPIbiDn66FTJ7jF1X6sV1GxpKhFQyYs6SL7LL4wT/XplRSwUTTD
hHccwuqPueYpD208w0zRcWVO7wpU7Lm+8xFrVwjhK7Q1AF6GzfwtmHy22fY05doM
NzXvYgB9urC1fYPQsEO6IhgNH7DT+ZtYOiHnRk2vTgr3fkIjKh4bNEdrnaQ9TOH5
junlio+07llaF/gB/JWycctuy2z2T/zENLPwhy9ZK35DgikGaMsDU7mA6iGgoxhc
TQPDnn3Veel7FBXMPCrxYMDgcBCEqENdOfQcbEl9lXDocr7UjQF/0GsvhFncMoIY
GCfdSThYV6x/U9StyBdxerbX4fCddPgd2RvKjVgDmOdsOVGCU0/iKyhgrBh3AbfP
MNf+AzYCUGvnzfDsDIF+CvJhcddSHX44N5TGLubVwIMIHsvBevC+7D9uHGaLqkem
UR8xa489SZ8LOnsL8TgtRaGXNaWqeJX7tIGPtiS5s2bzhRDr8q062VOd3J/Qw3E0
AQSixX+dQezw282RHYpCk3xuRgbN1oKvCEbOyDB97sbo19f+W2k0CmPVxIaDkr50
D729WS+6XvozYaw0z/R1aOWJTJLTe9ZUO/Zi9qhDfQtLVzTz8M8=
=WybD
-----END PGP SIGNATURE-----
Hello,
The Release Engineering team will be expanding the set of people
responsible for the weekly MediaWiki train deployments[0] to include
people working normal European hours. Unfortunately, the current MW
train deployment window is too late in the day for them.
To address this we are adding a European-focused timeslot for the MW
train (and moving the current "EU SWAT window" 2 hours earlier to
accommodate).
The first planned use of the new window will be next week, the week of
July 9th.
For the avoidance of doubt: the normal MW train windows will not go
away, these EU-timezone ones are in addition to them and only used
during weeks that the train is conducted by someone in Europe. But, the
EU SWAT window will indeed be permanently moved for simplicity (IOW: not
dependent upon who's doing the train).
== European train window and changes ==
This would affect Tuesday, Wednesday, and Thursday
* 1300-1400 CEST (1100-1200 UTC) - EU SWAT window (2 hours earlier)
* 1400-1500 CEST (1200-1300 UTC) - Break
* 1500-1700 CEST (1300-1500 UTC) - EU Train window
* 1700-1800 CEST (1500-1600 UTC) - Break
* 1800-1900 CEST (1600-1700 UTC) - PuppetSWAT (Tue/Thu only, no change)
Also, at the same time we'll be moving the Wednesday morning (SF time)
SWAT window on hour earlier to 9am Pacific. This is to alleviate a
contention with the weekly Scrum of Scrums meeting.
Best,
Greg
[0] https://www.mediawiki.org/wiki/MediaWiki_1.32/Roadmap
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
On Wed, Jul 11, 2018 at 1:26 PM, Nuria Ruiz <nuria(a)wikimedia.org> wrote:
> Hello!
>
> Just a brief note to announce that we have two new things in wikistats
> this quarter. We have reviewed maps by popular demand to give more precise
> pageviews per country.
>
> Check, for example, pageviews for portuguese wikipedia on the world for
> last month:
>
> https://stats.wikimedia.org/v2/#/pt.wikipedia.org/reading/
> page-views-by-country/normal|map|2-Year~2016060100~2018071100|~total
>
> Also, we have included legacy pageviews to the UI, we used to call these
> page-counts and prior to June 2015 this is the metric that we reported as
> pageviews for all wikimedia sites.
>
> Info about metric:
> https://wikitech.wikimedia.org/wiki/Analytics/Archive/Data/Pagecounts-raw
>
> See, for example, pagecounts for portuguese wikipedia from 2008 to 2016.
> https://stats.wikimedia.org/v2/#/pt.wikipedia.org/reading/
> legacy-page-views/normal|bar|All~1980010100~2018071100|~total
>
> Also, all urls are now bookmarkable.
>
> As always suggestions welcome, please file bug reports on phabricator.
>
> Thanks,
>
> Nuria
>
Well yes, but so will the rest of the world that uses DST.
On Wed, 11 Jul 2018, 21:04 Brad Jorsch (Anomie), <bjorsch(a)wikimedia.org>
wrote:
> My point was that if CA and Europe accepts those proposals then the rest
> of the US that still uses DST would have the problem that things would move
> around when DST starts or ends, so it just moves the problem around instead
> of really getting rid of it.
>
> On Wed, Jul 11, 2018 at 4:01 PM, Alex Monk <krenair(a)gmail.com> wrote:
>
>> As long as these get pinned to SF time what the rest of the US does with
>> regards to DST is irrelevant. If California drops DST then it no longer
>> affects deployments pinned to SF time.
>>
>> On Wed, 11 Jul 2018, 19:42 Brad Jorsch (Anomie), <bjorsch(a)wikimedia.org>
>> wrote:
>>
>>> On Wed, Jul 11, 2018 at 12:19 PM, Kunal Mehta <legoktm(a)member.fsf.org>
>>> wrote:
>>>
>>>> (un)relatedly:
>>>> * EU survey to remove summertime/DST:
>>>> <
>>>> https://ec.europa.eu/eusurvey/runner/2018-summertime-arrangements?surve
>>>> ylanguage=EN
>>>> <https://ec.europa.eu/eusurvey/runner/2018-summertime-arrangements?surveylan…>
>>>> >
>>>> * California Proposition 7 (2018) to institute a permanent DST:
>>>> <
>>>> https://ballotpedia.org/California_Proposition_7,_Permanent_Daylight_Sa
>>>> ving_Time_Measure_(2018
>>>> <https://ballotpedia.org/California_Proposition_7,_Permanent_Daylight_Saving…>
>>>> )>
>>>>
>>>> Hopefully we can get rid of this problem at the root cause as well :)
>>>>
>>>
>>> You forgot about most of the rest of the US ;)
>>>
>>>
>>> --
>>> Brad Jorsch (Anomie)
>>> Senior Software Engineer
>>> Wikimedia Foundation
>>> _______________________________________________
>>> Engineering mailing list
>>> Engineering(a)lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/engineering
>>>
>>
>
>
> --
> Brad Jorsch (Anomie)
> Senior Software Engineer
> Wikimedia Foundation
>
= 2018-07-11 =
== Callouts ==
* Fundraising campaigns
https://meta.wikimedia.org/wiki/CentralNotice/Calendar
* Datacenter switchover will happen on the end of this quarter. Dates not
fully set, but a tentative range is 17-29 September 2018 and a switchback
on 8-19 October 2018. We plan for at least 3 weeks this time around.
* Analytics: Spark is now available in Jupyter notebooks
== Audiences ==
=== Readers ===
==== iOS native app ====
Natalia
* Blocked by:
* Blocking:
* Updates:
** Planning to be feature complete on 6.0.0 (
https://phabricator.wikimedia.org/tag/ios-app-v6.0-walrus-on-a-unicycle/) by
the end of the week of July 9
** User testing of feed redesign and search coming up (
https://phabricator.wikimedia.org/T198932 )
==== Android native app ====
* Blocked by:
* Blocking:
* Updates:
** Multi-language release is in production.
** Working on completing prototypes for A/B testing at Wikimania (includes
navigation redesigns, table-of-contents variations, and Wikitext Keyboard)
** https://phabricator.wikimedia.org/project/view/3367/
==== Readers Web ====
* Blocked by:
* Blocking:
* Updates:
**Mobile website (MinervaNeue / MobileFrontend):
***Page issues UI T199005 T191532 T197932 T191528 T199005 T198115 T197931
***Improve diff UI T197491 T197729
***Fixes and hygiene T193418 T193821 T198930 T197106 T199156 T193754
T196767 T188937 T193069
***Finalizing designs for collapsible templates T111565
***Planning for advanced mobile contributions
**Desktop website (Popups):
***Abort outdated HTTP requests T197700
***Send the Accept-Language header when calling API T198619
**Design and product are preparing user interviews for Wikimania
==== Readers Infrastructure ====
James
* Blocked by:
** Release Engineering (CI) for merge of
https://gerrit.wikimedia.org/r/c/integration/config/+/442126
** Language Team for review of the stack with
https://gerrit.wikimedia.org/r/c/mediawiki/core/+/443687
* Blocking:
* Updates:
** Working with the iOS and Android teams on using the Page Library's
transforms in the service. (T170584)
** Still working on supporting lang variants in MCS via the uselang
parameter to MW API requests. (T195948)
** Safari Reading List extension now submitted, awaiting approval from
Safari extension store. (T191998)
** Maps work continues; working with Discovery colleagues to move the test
cluster out of production. (T172090)
==== Multimedia ====
Matthias
* Blocked by:
* Blocking:
* Updates:
** Working on search interface prototyping, so users can search by Wikibase
properties/values
** Continuing work on search backend
=== Contributors ===
==== Community Tech ====
Moriel
* Blocked by:
** PageTriage, can't merge anything right now:
https://phabricator.wikimedia.org/T198137 (help)
* Blocking:
* Updates: GlobalPreferences is deployed; we're working on API modules
**
==== Anti-Harassment Tools ====
Moriel
* Blocked by:
* Blocking:
* Updates:
** RfC coming
==== Editing ====
* Blocked by:
* Blocking:
** Updates:
**
==== Parsing ====
* Blocked by:
* Blocking:
* Updates:
==== Growth ====
* Blocked by:
* Blocking:
* Updates:
**
==== Language ====
Kartik
* Blocked by:
* Blocking:
* Updates:
** Content Translation v2 - work continues: MT warnings and calculations,
Users to notify about old drafts and bug fixes
=== Audiences Design ===
* Blocked by:
* Blocking:
* Updates:
**
==== UI Standardization ====
* Blocked by:
* Blocking:
* Updates:
** New OOUI release coming to MW master today, nothing major.
== Technology ==
=== Analytics ===
Francisco
* Blocked by:
* Blocking:
**Eventlogging outage -
https://wikitech.wikimedia.org/wiki/Incident_documentation/20180705-EventLo…
* Updates
**Close to deploy pagecounts (legacy pageviews) to wikistats, they been
available on API for a while
**Maps improvements
**Working with security on threat model of analytics stack. [wiki, email]
**We had a data drop (now backfilled) that highlighted lack of alarms in
our current eventlogging hadoop pipeline, we will be working on those.
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
**
=== Fundraising Tech ===
Elliott
* Blocked by:
* Blocking:
* Updates:
** Running another 1-hour test on new API for main CC processor
*** sorry for the email disruption!
**** Amazon IP address change led to a failmail for each incoming payment
notification
**** Casey working with net ops team to get firewall rules updated
** More CiviCRM core updates
** More work on CiviCRM donor data deletion extension
** More work on backend for EventLogging-based banner/landingpage
impressions stats
** Testing new CiviCRM extension for recurring donations
** Adding per-country email opt-in checkbox on donation forms
=== MediaWiki Core Platform ===
Cindy
* Blocked by:
* Blocking:
* Updates:
** MediaWiki Platform Team is now part of the Core Platform Team (with
Services)
** Deployed a change to Phabricator config in response to more Phabricator
vandalism
** Working on https://phabricator.wikimedia.org/T100782, "Redirect loop
detected" error live in production
** Platform Evolution Program:
*** Sent kickoff emails to stakeholder teams
*** preparing questions for stakeholders to get input for Wikimedia
Technical Conference
** patches needing review
*** https://gerrit.wikimedia.org/r/c/mediawiki/core/+/443440 (<style>-in-TOC
bugfix)
*** https://gerrit.wikimedia.org/r/c/mediawiki/core/+/322729 (Externallinks
indexing)
*** https://gerrit.wikimedia.org/r/c/mediawiki/core/+/444464 (mobile
Commons login failure bugfix)
2** the usual code review and bug work
=== Performance ===
Ian
* Blocked by:
** None
* Blocking:
** None
* Updates:
** All wikis are writing to both nutcracker and to mcrouter (
https://gerrit.wikimedia.org/r/444932). Reads are coming only from
nutcracker for the time being to ensure the mcrouter cache is hot before
switching.
** Fixed a regression in SaveTiming related to an MCR change:
https://phabricator.wikimedia.org/T198483
** Working on a patch that will cause a warning when a duplicate parse
occurs: https://phabricator.wikimedia.org/T172941
** Released CSSJanus 1.3.0
=== Release Engineering ===
Antoine
* Blocked by:
* Blocking:
** James F. https://gerrit.wikimedia.org/r/c/integration/config/+/442126
** Moriel: UBN https://phabricator.wikimedia.org/T198137 (help)
* Updates:
** Mediawiki train happening during European time this week:
https://lists.wikimedia.org/pipermail/wikitech-l/2018-July/090287.html
** MediaWiki 1.29 is end of life https://phabricator.wikimedia.org/T197669
** Working with MediaWiki Platform Team / Cindy about MediaWiki releasing
** (Security team) Two-factor authentication to be enforced on GitHub
https://phabricator.wikimedia.org/T198810
** Phabricator spam / anti vandalism is ongoing
** Help clean up unused config in production:
https://wikitech.wikimedia.org/wiki/User:Krinkle/Unused_config
=== Research ===
* Blocked by:
* Blocking:
* Updates:
=== Scoring Platform ===
Adam W.
* Blocked by:
** JADE deployment discussions, around schema scalability.
*** https://phabricator.wikimedia.org/T196547
*** https://www.mediawiki.org/wiki/Everything_is_a_wiki_page vs. scalability
***
https://en.wikipedia.org/wiki/User:Risker/Risker%27s_checklist_for_content-…
*** Are we going to re-architect this away from wiki pages after all?
* Blocking:
* Updates:
=== Search Platform ===
Stas
* Blocked by:
* Blocking:
* Updates:
** Refactored search configs to move tuning to mediawiki-config:
https://phabricator.wikimedia.org/T182717
** Fixed namespace/redirect mixup in search:
https://phabricator.wikimedia.org/T115756
** Created separate namespace index:
https://phabricator.wikimedia.org/T192699
** Working on puppet setup multi-instance Elasticsearch:
https://phabricator.wikimedia.org/T198351
** Working on fixing Polish analyzer:
https://phabricator.wikimedia.org/T186046
** Working on ES 6.3 upgrade: https://phabricator.wikimedia.org/T198067
** Working on Lexeme fulltext search:
https://phabricator.wikimedia.org/T196188
** Working on query parsing refactoring:
https://phabricator.wikimedia.org/T185108
=== Security ===
* Blocked by:
* Blocking:
* Updates:
**
=== Site Reliability Engineering ===
* Blocked by:
** None
* Blocking:
** None
* Updates:
** Proton is up and running.
** Eqiad network maintenance ongoing, mostly handled without issues, do
expect the occasional hiccup
** Work started on PHP7 for MediaWiki
** grafana-admin.wikimedia.org last users, update your bookmarks.
== Wikidata ==
* Blocked by:
* Blocking:
* Updates:
**
https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-07-11
== German Technical Wishlist ==
* Blocked by:
* Blocking:
* Updates:
**
== Multi-Content Revisions ==
* Blocked by:
* Blocking:
* Updates:
** read old / write both mode for revision / content schema migration will
be enabled on beta and master (not WMF) next week. See full timeline at
https://docs.google.com/spreadsheets/d/1TkznqoaMH6HTQBSMxXPRhSOo8auf1oMLx6c…
** Storage layer (phase 1) tasks nearing completion
** Delivery date of MCR code for SDC use case is '''1 Sept 2018'''
== SoS Meeting Bookkeeping ==
* Updates:
**Removed the goals dependency check-in from notes template. Will address
that communication via another mechanism.