Re: [Wikitech-l] [Engineering] Pageview API

This is *awesome*. Excellent work Team Analytics! On Mon, Nov 16, 2015 at 9:50 PM, Dan Andreescu wrote: > Dear Data Enthusiasts, > > > In collaboration with the Services team, the analytics team wishes to > announce a public Pageview API >

Re: [Wikitech-l] [Engineering] [Analytics] Pageview API

Hello Bahodir, On Tue, Nov 17, 2015 at 2:15 PM, Bahodir Mansurov wrote: > Agree with everyone else, this is great! > > I just have a question. Is this an evolving thing in a sense that more data > sources will be used to define page views? Let me give an example. Reading

Re: [Wikitech-l] [Engineering] IRC office hour this Thursday: reconnecting with the shared hosting community

Yes, this is exactly what I had in mind. On Tue, Nov 17, 2015 at 12:30 AM, Rob Lanphier wrote: > Hi Gilles, > > Thanks for leading this! My reading of your agenda leads me to believe > that this is intended as a "problem solving" meeting, as described in >

Re: [Wikitech-l] [Analytics] Pageview API

Congratulations from me as well, especially since I was probably the one screaming for it the loudest (or the longest, or both...) I'll now go and have good long lok at which tools to adapt, which to rewrite, and which to invent! On Mon, Nov 16, 2015 at 9:50 PM Dan Andreescu

Re: [Wikitech-l] [Analytics] Pageview API

Agree with everyone else, this is great! I just have a question. Is this an evolving thing in a sense that more data sources will be used to define page views? Let me give an example. Reading Web team is working on a new web app prototype that caches pages which can be viewed without

[Wikitech-l] Gerrit +1 now executes the code you reviewed

I just merged and deployed https://gerrit.wikimedia.org/r/#/c/184886/ , which means: A +1 in gerrit.w.o didn't have any technical effect until now. Now it submits the patch for testing. That means if you +1 a patch from a non-whitelisted user that was not yet tested, it will then, just as if

Re: [Wikitech-l] Gerrit +1 now executes the code you reviewed

Just to clarify, this is a +1 from a user who has +2 rights? Whereas a +1 from some random user will not initiate the tests? On Tue, Nov 17, 2015 at 10:20 AM, Jan Zerebecki wrote: > I just merged and deployed https://gerrit.wikimedia.org/r/#/c/184886/ , > which

Re: [Wikitech-l] Gerrit +1 now executes the code you reviewed

On 2015-11-17 19:30, Chris Steipp wrote: > Just to clarify, this is a +1 from a user who has +2 rights? Whereas a +1 > from some random user will not initiate the tests? No. The permission here is the CI white list in zuul, which is a different one from gerrit +2. The permission and who has it

Re: [Wikitech-l] XML dumps

On 05/28/2015 07:52 PM, Lars Aronsson wrote: > With proper release management, it should be possible to run the old version of the process until the new version has been tested, first on some smaller wikis, and gradually on the larger ones. I understand your frustration; however release

[Wikitech-l] RFC meeting this week

In the next RFC meeting, we will discuss the following RFC: * API-driven web front-end The meeting will be on the IRC channel #wikimedia-office on chat.freenode.net at the following time: * UTC: Wednesday 22:00 * US PST: Wednesday 14:00 * Europe CET:

Re: [Wikitech-l] Pageview API

Dan Andreescu wrote: >The API can tell you how many times a wiki article or project is viewed >over a certain period. You can break that down by views from web crawlers >or humans, and by desktop, mobile site, or mobile app. And you can find >the 1000 most viewed articles

Re: [Wikitech-l] Pageview API

Nice work on the API! I wrote a basic consumer of this API at http://codepen.io/Krinkle/full/wKOMMN#wikimdia-pageviews The only hurdle I found is that the 'articles' property is itself nested/double encoded JSON, instead of a plain object. This was somewhat unexpected and makes the API harder to

Re: [Wikitech-l] [Engineering] Pageview API

This is awesome. Congratulations! On Tue, Nov 17, 2015 at 9:28 AM, Alexandros Kosiaris < akosia...@wikimedia.org> wrote: > It's nice to finally this go live. Great work guys!! > > On Mon, Nov 16, 2015 at 11:50 PM, Dan Andreescu > wrote: > > Dear Data Enthusiasts, > > >

Re: [Wikitech-l] [Engineering] Pageview API

It's nice to finally this go live. Great work guys!! On Mon, Nov 16, 2015 at 11:50 PM, Dan Andreescu wrote: > Dear Data Enthusiasts, > > > In collaboration with the Services team, the analytics team wishes to > announce a public Pageview API. For an example of what

Re: [Wikitech-l] Pageview API

Krinkle wrote: >The only hurdle I found is that the 'articles' property is itself >nested/double encoded JSON, instead of a plain object. This was somewhat >unexpected and makes the API harder to use. I filed about this. MZMcBride wrote: >Now that I'm

Re: [Wikitech-l] Gerrit +1 now executes the code you reviewed

Le 17/11/2015 19:20, Jan Zerebecki a écrit : > I just merged and deployed https://gerrit.wikimedia.org/r/#/c/184886/ , > which means: > A +1 in gerrit.w.o didn't have any technical effect until now. Now it > submits the patch for testing. That means if you +1 a patch from a > non-whitelisted user

Re: [Wikitech-l] Outreachy round 11 results out

On 2015-11-17, Tony Thomas <01tonytho...@gmail.com> wrote: > Hello all, > > Glad to inform that the results of Outreachy round 11 are out, and one of > our candidate - Josephine Lim made it to the program for her proposal > on Easier categorization of pictures in Upload to Commons Android app - >

Re: [Wikitech-l] Security patch for Flow merged

On 11/17/2015 05:12 PM, Matthew Flaschen wrote: Nick Wilson discovered a security issue that affects Flow when used with caching proxies such as Varnish: https://phabricator.wikimedia.org/T116095 (this task will be opened soon). In such a setup, topics in cache would remain accessible after

[Wikitech-l] Security patch for Flow merged

Nick Wilson discovered a security issue that affects Flow when used with caching proxies such as Varnish: https://phabricator.wikimedia.org/T116095 (this task will be opened soon). In such a setup, topics in cache would remain accessible after the board was deleted. We have deployed the fix