i dont know if this affects us but mw jquery is being updated to 3
Zppix
Volunteer developer for WMF
enwp.org/User:Zppix
---------- Forwarded message ----------
From: "Krinkle" <krinklemail(a)gmail.com>
Date: Jun 29, 2017 3:35 PM
Subject: [Wikitech-ambassadors] Upgrade to jQuery 3 is coming
To: "Wikitech-ambassadors(a)lists.wikimedia.org" <
Wikitech-ambassadors(a)lists.wikimedia.org>
Cc:
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
>
>
> _______________________________________________
> Wikitech-ambassadors mailing list
> Wikitech-ambassadors(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
>
>
Hey,
ORES right now is under pressure and returns overload errors, we are
investigating the cause and we'll send you notice once it's back online.
Sorry for any inconvenience happened
Best
--
Amir Sarabadani Tafreshi
Software Engineer (contractor)
-------------------------------------
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
http://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.
Perhaps of interest.
Pine
---------- Forwarded message ----------
From: Chris Koerner <ckoerner(a)wikimedia.org>
Date: Fri, Jun 16, 2017 at 8:31 AM
Subject: [Design] Design in the Era of the Algorithm
To: design(a)lists.wikimedia.org
Josh Clark on design principles for addressing flaws in machine learning.
(via waxy.org)\
"The answer machines have an overconfidence problem. It’s not only a
data-science problem that the algorithm returns bad conclusions. It’s a
problem of presentation: the interface suggests that there’s one true
answer, offering it up with a confidence that is unjustified.
So this is a design problem, too. The presentation fails to set appropriate
expectations or context, and instead presents a bad answer with
matter-of-fact assurance. As we learn to present machine-originated
content, we face a very hard question: how might we add some productive
humility to these interfaces to temper their overconfidence?
I have ideas."
https://bigmedium.com/speaking/design-in-the-era-of-the-algorithm.html
Yours,
Chris Koerner
Community Liaison - Discovery
Wikimedia Foundation
_______________________________________________
Design mailing list
Design(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/design
Also ORES is moving to its dedicated nodes:
https://phabricator.wikimedia.org/T165171
Best
On 14 June 2017 at 03:18, Gabriel Wicke <gwicke(a)wikimedia.org> wrote:
> I checked the pdfrender instances on the other SCB nodes, and some used 7G
> and 15G respectively. My patch limits this to 2G, which should be enough
> for normal operation.
>
> Memory on the SCB nodes has been tight for a while. I think there are plans
> to move OCG (which uses the vast bulk of memory) to a separate cluster.
> There is also https://phabricator.wikimedia.org/T146664 for limiting the
> memory used by ORES.
>
> On Tue, Jun 13, 2017 at 3:29 PM, Daniel Zahn <dzahn(a)wikimedia.org> wrote:
>
> > - 19:24 mutante: scb1001 - killed process 10971
> (pdfrendering/electron)
> >
> > This apparently fixed it.
> >
> > I see there is already this https://gerrit.wikimedia.org/r/358888 now
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
>
>
>
> --
> Gabriel Wicke
> Principal Engineer, Wikimedia Foundation
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
--
Amir Sarabadani Tafreshi
Software Engineer (contractor)
-------------------------------------
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
http://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.
Hey,
We are currently having problem with ORES service which sends out time out
errors intermittently. More information can be found in
https://phabricator.wikimedia.org/T167819
We will let you know when the service is back to full capacity.
Best
--
Amir Sarabadani Tafreshi
Software Engineer (contractor)
-------------------------------------
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
http://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.
Hello,
I'm wondering how to find out the details of edit and article quality
models, specifically the *reverted* and *damaging* edit quality models, and
the *wp10* article quality model. I'm wondering what algorithm is being
used and what features are being trained on.
I believe the *wp10* model may have originated with Warncke-Wang, Cosley, &
Riedl (2013) Tell me more: An actionable quality model for Wikipedia, in
which case I can figure out the model specification and features from the
paper. But I'm not sure if the details of the edit quality models have been
similarly summarized in any papers or in any online documentation.
Thanks for your help!
Pierce
Hey folks,
I'll be starting to post updates here on our new blog[1], but if you'd
prefer to be notified via the mailing lists we used to post to, that's OK.
I'll make sure that the highlights and the link to these posts gets pushed
there too.
We had a big presence at the Wikimedia Hackathon 2017 in Vienna. We kicked
off a lot of new language focused collaborations (Greek, Tamil, Bengali)
and we deployed a new Item Quality model for Wikidata.
French and Finnish Wikipedias now have advance edit quality prediction
support!
ORES is available through api.php again via rvprop=orescores and
rcprop=oresscores.
Wiki labels now has a new stats reporting interface. Check out
https://labels.wmflabs.org/stats
We had a major hiccup when failing over to CODFW, but we worked it out and
ORES is very happy again.
See more details on our new blog: "Score all the things"
https://phabricator.wikimedia.org/phame/blog/view/8/
-Aaron
Principal Research Scientist @ WMF
Head of the Scoring Platform team
Hello, I just wanted to introduce myself, for you that dont know me, My
name is Zppix (on irc,onwiki etc) I'm a volunteer devloper upon seeing the
metric meeting from May 25th and seeing Aaron's presentation about Kalani
effect it peaked my interested in the AI-related projects, and now here I
am.
Other WMF projects I've ever worked on/contributed to:
-Operations/puppet
-Operations/mw-config
-Mw/core
-tools.zppixbot, tools.quarrybot-enwiki (both i created)
-grrrit-wm (before merge with wikibugs)
and im sure i've missed a few.
Anyway i'm looking forward to collaberating with you all, have a great rest
of the day!
--
Thanks,
Zppix
Volunteer Developer for WMF
www.enwp.org/User:Zppix