Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 3-4 pm
UTC** on #wikimedia-tech.
This time with a Wikimedia Special[1] in English and German!
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)
[1]: https://phabricator.wikimedia.org/T199093
--
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.
Hi All,
Here are the minutes from this week's TechCom meeting:
* IRC Meeting postponed until next week on 2018-07-18 in the
#wikimedia-office channel at 2pm PST(22:00 UTC, 23:00 CET): Unify
various deletion systems <https://phabricator.wikimedia.org/T20493>
Currently there are two systems for deletion of revisions Page deletion
and Revision delete. The current proposal would like to explore
implementing the logic behind “Page deletion” by using the same code and
database logic that is used by “Revision delete”.
* Finalized selection of new committee members (public announcement
coming soon)
* IRC Meeting scheduled for 2018-08-01 in the #wikimedia-office channel
at 2pm PST(22:00 UTC, 23:00 CET) RFC: Modern Event Platform - Choose
Schema Tech <https://phabricator.wikimedia.org/T198256> This RFC is
looking at if Apache Arvo or JSONSchema should be used for the event
schema and serialization method.
You can also find our meeting minutes at
<https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes>
See also the TechCom RFC board
<https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>.
If you prefer you can subscribe to our newsletter here:
<https://www.mediawiki.org/wiki/Newsletter:TechCom_Radar>
Thanks,
Kate
--
Kate Chapman TechCom Facilitator (Contractor)
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
>