In Wiktionary, every site/language documents words from every language,
as I am sure you know. A typical wiki page, e.g. "war" contains information
about the English noun as well as the German verb.
Through categories, we also know how many entries there are. How many
English lemmas, how many English nouns, how many German verbs.
But if I want to plot a graph of the growth over time of English nouns
and German verbs, it is a pity that this is not available anywhere.
But it would be possible to generate such data from the history
dump, by finding out when the page "war" was created and when its
English and German sections were created. In SQL terms, it would be
for each combination of page and section (heading), find the earliest
date when that section was present in that page. But a practical
implementation would of course solve that as a single-pass filter,
reading the stdout from bunzip.
So has anybody already written a program that reads through the
XML dump of articles and their history, and generates statistics
of this kind?
--
Lars Aronsson (lars(a)aronsson.se)
Linköping, Sweden
Hello,
This was something that came up during "The Big Open" at Wikimania, when
Katherine Maher talked with Ryan Merkley (CEO of Creative Commons) and
Mark Surman (ED of Mozilla Foundation). One of the themes mentioned was
that our projects need to work together and support each other.
In that vein, I'm interested in what people think about promoting
Firefox to users who are using legacy browsers that we don't support at
Grade A (or some other criteria). As part of the "drop IE8 on XP"
project[1] we're already promoting Firefox as the alternative option. I
was imagining it could be a small and unobtrusive bubble
notification[2], similar to those that Google pushes Chrome on people with.
If users use modern browsers, they're going to have better security
support, and most likely a better experience browsing Wikimedia sites
too. We'd be improving the web by reducing legacy browsers, and allowing
us to move forward with newer technology sooner (ideally).
And we'd be supporting a project that is ideologically aligned with us:
Mozilla.
Thoughts, opinions?
[1] https://phabricator.wikimedia.org/T147199
[2] https://www.mediawiki.org/wiki/Bubble_notifications
Thanks,
-- Legoktm
https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-09-06
= 2017-09-06 =
contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering
<!-- can't believe we're still using H1 elements -->
== callouts ==
* RelEng could use comments/help
[https://phabricator.wikimedia.org/T129149 discovery/analytics
move to scap3]
* Grace to share proposal for redesign of this meeting
-
== Audiences ==
=== Readers ===
==== iOS ====
* Blocked by: none
* Blocking: none
* Updates:
** Releasing 5.6.1 with minor bug fixes (
https://phabricator.wikimedia.org/project/view/2898/ )
** Next up is 5.7.0 ( https://phabricator.wikimedia.org/project/view/2899/ )
- Onboarding updates, Improved analytics
==== Web ====
* Team is focusing on removing OCG from stack. A lot of us are currently
getting up to speed with the stack there to support existing work by Baha
and Gergo.
==== Multimedia ====
* 3D is pretty much working like a charm on beta, except for the puppet
patch being cherry-picked and not deployed correctly. Testwiki ETA 2 weeks
assuming no problems.
(
https://en.wikipedia.beta.wmflabs.org/wiki/File:Crystal-NEW.stl#/media/File…)
* Team is nearly staffed up and ready to roll, we'll be doing some
ramping-up and prioritization over the next few weeks.
====Reading Infrastructure ====
* Blocked by: Security for the ReadingLists review
https://phabricator.wikimedia.org/T174126
* Updates:
** ReadingLists MediaWiki extension merged, working on RESTBase half
** Updates to On-this-day endpoint going to be deployed on Wednesday
** Working on structured references API
=== Community Tech ===
* Subnet contributions patch merged, will ride the train next week
* Preparing ArticleCreationWorkflow for deployment
=== Contributors ===
==== Parsing ====
* Nothing for this week. We are coming off vacation.
==== UI Standardization ====
* Updates:
** OOUI: v0.23.0 released, among changes:
*** icons: Removed obsolete icons and moved icons from alerts pack so it's
leniant & more performant
*** ButtonInputWidget: Fix Safari-specific intrinsic `margin` (Volker E.)
*** WikimediaUI theme: Fix frameless indicator combination buttons'
appearance (Volker E.)
* Ongoing:
** Continuation on WikimediaUI Style Guide work, starting with updating
imagery on color section
https://wikimedia.github.io/WikimediaUI-Style-Guide/visual-style_colors.html
** Remaining work (get patches merged) on aligning arbitrary, historically
grown colors to WikimediaUI color palette
https://phabricator.wikimedia.org/T148708
** Align TransparencyReport to WikimediaUI color palette and make it fully
accessible
==== Global Collaboration ====
===== Language =====
* Blocked: cxserver deployment with
https://phabricator.wikimedia.org/T173038 is WIP.
* CX-VE work continue.
* CX dashboard improvements.
===== Collaboration =====
* Updates
** RCFilters - Mostly improving appearances and messages, some fine-tuning
and bug fixes
*** {{git|2b7fec67}} - <nowiki>WLFilters: convert 'edit watchlist' button
to new UX</nowiki> ({{phabricator|T172030}})
*** {{git|94497cbd}} - <nowiki>WLFilters: reword watchlist-details
slightly</nowiki> ({{phabricator|T172030}})
*** {{git|3ec69e79}} - <nowiki>WLFilters: fix msg keys to comply with
standard</nowiki>
*** {{git|8e099f54}} - <nowiki>RCFilters: Minimize vertical spacing; get
rid of legend and <br>s</nowiki> ({{phabricator|T174121}})
*** {{git|ffb5387c}} - <nowiki>WLFilters: wrap Watchlist-details in a div
instead of a p</nowiki> ({{phabricator|T172030}})
*** {{git|8148d908}} - <nowiki>WLFilters: adapt to customized
watchlist-details</nowiki> ({{phabricator|T172030}})
*** {{git|467fbef0}} - <nowiki>WLFilters: fix server-side tag
filtering</nowiki>
*** {{git|3bf41380}} - <nowiki>RCFilters: Make top links in RecentChanges
expand to full-width</nowiki> ({{phabricator|T174617}})
*** {{git|61696a0b}} - <nowiki>WLFilters: describe how unseen changes
should look</nowiki> ({{phabricator|T172030}})
*** {{git|5e8ba53a}} - <nowiki>RCFilters: Include invert param when reading
default saved query</nowiki> ({{phabricator|T174506}})
*** {{git|0a823840}} - <nowiki>RCFilters: rephrase the feedback link
text</nowiki> ({{phabricator|T174411}})
*** {{git|ba86bd1d}} - <nowiki>WLFilters: Use displaysOnUnstructuredUi
instead of isVisible</nowiki> ({{phabricator|T171134}})
=== Search Platform ===
* Blocked by: none
* Blocking: none
* Updates:
** Continuing work on ML-assisted ranking
** Preparing upgrade to Elastic 5.5 (
https://phabricator.wikimedia.org/T174662 )
** Developing strategy for porting CirrusSearch tests to nodejs (
https://phabricator.wikimedia.org/T174103 )
** Excellent blog post by Trey on search with wrong keyboard:
https://blog.wikimedia.org/2017/08/28/wikipedia-search-phonetic-keyboards/
** Search relevance A/B test analyzed:
https://wikimedia-research.github.io/Discovery-Search-Adhoc-SurveyMVP/
** Explore similar A/B test analyzed:
https://wikimedia-research.github.io/Discovery-Search-Test-ExploreSimilar/
** Per-IP rate limits introduced on maps:
https://phabricator.wikimedia.org/T169175
** Fixed load spikes on some Elastic backend servers:
https://phabricator.wikimedia.org/T169498
=== Scoring Platform ===
*Blocked by: nothing.
*Blocking:
** We need to run our stress tests again before ops can move us to the
dedicated cluster. https://phabricator.wikimedia.org/T174402.
https://phabricator.wikimedia.org/T169246
* Updates:
** Wikilabels incident
https://phabricator.wikimedia.org/phame/post/view/69/wikilabels_incident_re…
** svwiki, eswikibooks, filter support comming soon for RC Filter
== Wikidata ==
* Blocked by https://gerrit.wikimedia.org/r/357985 RewriteRule patch not
being merged
* Franziska Heine is new head of software department (was Abraham
Taherivand before):
https://blog.wikimedia.de/2017/09/01/franziska-heine-ist-neue-leiterin-der-…
* Published the WikidataCon program:
https://www.wikidata.org/wiki/Wikidata:WikidataCon_2017/Program
* Entity serialization will change and include all snak hashes (on main,
qualifier, and reference snaks): https://phabricator.wikimedia.org/T174692
* Did several releases of PHP libraries with MediaWiki integration removed:
https://phabricator.wikimedia.org/T173936
* Investigating ways to do the same with JavaScript ResourceLoader
libraries: https://phabricator.wikimedia.org/T174922
* List of monolingual value languages grows to a point that makes people
uncomfortable why core doesn't support these:
https://gerrit.wikimedia.org/r/374052
== German Technical Wishlist ==
* Preparing for WikiCon (annual German community conference)
* Another Wikidiff2 change needs review:
https://gerrit.wikimedia.org/r/319866
=== Fundraising Tech ===
* No blocker/blocking
* Trying to optimize things for December (db writes, fs access, etc)
* More PayPal Express Checkout tweaks
* More CiviCRM contact de-duplication work
=== Security ===
* No blockers
* Updates:
** Looking into improving password blacklists
** re-review of CentralNotice
** review of vue.js up next
=== Services ===
* No blockers
* Updates:
** restbase1010 disk failure, now fixed
** Cassandra 3 cluster almost set up, continue work on new storage
implementation
** node 8 - if you can start testing your services with it
** All time record on REST API usage - 10k req/s
=== RelEng ===
* Blocking
** None?
* Blocked
** Could use comments/help [https://phabricator.wikimedia.org/T129149
discovery/analytics
move to scap3]
* Updates
** 1.30.0-wmf.17 going out this week
=== Technical Operations ===
* Blocked by: none
* Blocking: none
* Updates:
** All video scalers now running jessie, this completes the migration of
mw* servers
** tin deploy server has bad disk, pending replacement
https://phabricator.wikimedia.org/T174452
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **today 3-4 pm UTC** on
#wikimedia-tech.
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
This meeting is an offer by WMDE’s tech team. Hosts of todays meeting are:
@addshore & @Tobi_WMDE_SW.
Hope to see you there!
Michi (for WMDE’s tech team)
--
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, after a long long journey...
https://www.mediawiki.org/wiki/Special:Newsletters !
The Newsletter extension is a tool to facilitate subscription and delivery
of newsletters hosted on MediaWiki-based sites. You can learn more about
this extension at https://www.mediawiki.org/wiki/Help:Extension:Newsletter
Any newsletters within the scope of MediaWiki.org can be created. In
previous discussions it was agreed to only allow administrators to create
newsletters. Once a newsletter is created, their publishers can announce
new issues at will without requiring administrators anymore.
If you want to create a newsletter and you need an administrator to do it,
we will be happy to help you at
https://www.mediawiki.org/wiki/Topic:Txn15jri131au12s
If you want to report problems, request features, or get involved in the
project, please check https://phabricator.wikimedia.org/project/board/888/
PS: BIG THANK YOU to everybody involved in this project. Proper attribution
and celebration will come in a blog post summarizing these ~2,5 years of
planning, development, testing, and deployment to a first Wikimedia wiki.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
The language engineering monthly report for July 2017 is ready.
*Highlights for this month*
Content Translation dashboard has received a major facelift that aligns it
with the Wikimedia style guide and makes it easier to use.
Translatewiki.net now imports new messages up to 9 times per day. New
messages are made available for translation automatically but any changed
messages must be checked by a human. We want to ensure that users get the
new features in their own language. Please contact me if you want to help
us to have a robust around-the-clock coverage.
*Full report*
https://www.mediawiki.org/wiki/User:Nikerabbit/Monthly_report/2017-07
For those unfamiliar with this report, its goal is to summarize all
technical changes to internationalization, translation tools and other
language support products. It also highlights the diversity of contributors
to this area and that many of them are volunteers.
-Niklas
Hello everyone,
We've released OOjs UI 0.23.0, today. It will be in MediaWiki core from
1.30.0-wmf.18, which will be deployed to Wikimedia production in
the regular train, starting on Tuesday 12 September. As there are five
breaking
changes in this release, at least nominally, please carefully consider if
they
affect your code.
Breaking changes since last release:
* Remove CardLayout and references in IndexLayout (Volker E.)
CardLayout was renamed to TabPanelLayout in v0.21.3 and all its references
updated
back then; now its alias has been removed.
* Remove FloatingMenuSelectWidget (Volker E.)
FloatingMenuSelectWidget got deprecated in v0.21.3 and now has been removed.
Use MenuSelectWidget instead.
* Remove back-compat `OO.ui` prefix assumption in infusion code (Prateek
Saxena)
We've requested that infused data contained the full class name, rather
than assuming
the "OO.ui" prefix, since v0.12.0. Backwards-compatible `OO.ui` prefixing
has been
removed in this release.
* icons: Remove 'caret' icons (James D. Forrester)
The 'caretUp', 'caretDown', 'caretLast', and 'caretNext' icons were
deprecated
and replaced with the almost-identical 'collapse', 'expand', 'previous',
and 'next' ones
in v0.21.3 and are now removed completely.
* icons: Remove 'wikitrail' icon (James D. Forrester)
'wikitrail' icon was renamed to 'mapTrail' for consistency in v0.20.1.
Deprecations since last release:
* BookletLayout: Rename `getClosestPage()` to `findClosestPage()` (Prateek
Saxena)
Renaming this getter for one of the 0+ items inside to `findClosestPage()`
for consistency.
Please switch over to the new name.
* icons: Flag unused 'sun' icon as to be removed (James D. Forrester)
'sun' icon isn't in use in any of our products or products known to us,
nor is it planned to be used. In order to keep things small, we'll remove
the icon
in next breaking release.
* icons: Move 'eye'/'eyeClosed' to 'accessibility' (Volker E.)
We want to use 'alerts' pack more deliberately in major products and gonna
move certain icons to other packs.
* icons: Move 'signature' to 'editing-advanced' (Volker E.)
We want to use 'alerts' pack more deliberately in major products and gonna
move certain icons to other packs.
Please update your icon pack references accordingly in case you're using
this
icon.
Additional details on the 11 new features, 63 code-level and accessibility
changes,
28 styling and interaction design fixes, and all improvements since v0.22.0
are in
the full changelog[0]. If you have any further queries or need help dealing
with breaking changes, please let me know.
As always, a general set of library documentation is
available on mediawiki.org[1], and there is some comprehensive
generated code-level documentation and interactive demos hosted on
doc.wikimedia.org[2].
[0] - https://phabricator.wikimedia.org/diffusion/GOJU/
browse/master/History.md
[1] - https://www.mediawiki.org/wiki/OOjs_UI
[2] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker
--
Senior UX Engineer, Contributors
Wikimedia Foundation
volker.e [at] wikimedia | @Volker_E
On Sat, 02 Sep 2017 02:06:09 +0000, Chad<innocentkiller(a)gmail.com> wrote,
> (3) I would*really* like to have 2--maybe 3--browsers to list. There's
> zero reason to make users think there's only one option when there's a
> couple of valid ones.
I would love that too. Imagine that we do take the step and start promoting Firefox
"alone" to legacy users. I "suspect" the first reaction of a user who doesn't
take the time to realise we're promoting an open-source movement while trying to
help them get rid of their legacy browser to be,
"I thought Wikipedia doesn't show ads/promotions. Seems they have
changed their motive of "Not showing ads for revenue"! May be they'll
be showing more ads in the future. ARRRGGHHH!"
That might be a little over boasted, though! In order to avoid such reactions how about
recommending Firefox in the pop-up/central notice and linking to a list of other good
browsers to show we aren't promoting /advertising browsers. For the list of other browsers
we could link to https://browsehappy.com
To address this,
On Fri Sep 1 13:55:19 UTC 2017, Federico Leva (Nemo) <nemowiki(a)gmail.com> wrote,
> -1 to linking any resource which is not itself free software,
> translatable with free software and managed by a privacy-compliant org.
I guess browsehappy is at least open source.
https://github.com/WordPress/browsehappy
---
Kaartic