Why don't we continue to use the bits cache for all things resourceloader.
Can you provide a different path for these requests, such as instead of:
http://bits.wikimedia.org/en.wikipedia.org/load.php?..
use something like:
http://bits.wikimedia.org/m/en.wikipedia.org/load.php?..
Then we can if
Welcome Brandon!!
On Fri, Mar 29, 2013 at 3:00 PM, Ct Woo wrote:
> All,
>
> We are excited to announce that Brandon Black will join us this Monday
> (2013-04-01) as a full-time member of the Operations Engineering team.
>
> Brandon comes with deep and wide technical experience. Previously, he he
fyi, there is a nice % of grants for technical projects approved.
You can find the list at
https://meta.wikimedia.org/wiki/Grants:IEG#ieg-engaging or keep reading.
Original Message
Subject: [Wikimedia-l] Announcing Round 1 Individual Engagement Grantees
Date: Fri, 29 Mar 201
All,
We are excited to announce that Brandon Black will join us this Monday
(2013-04-01) as a full-time member of the Operations Engineering team.
Brandon comes with deep and wide technical experience. Previously, he held
senior systems engineering positions in companies like SqueezeNetwork.com,
This approach will require either:
1) Adding device detection to bits for device variance
2) Using mobile varnish to handle load.php requests for resources requested
from .m domains
From conversations with Max and some folks from ops, it sounds like #2 is
the preferred approach, but I am a little
On 29.03.2013, 21:47 Yuri wrote:
> Max, do we still plan to detect javascript support for mobile devices, or
> do you want to fold that into "isWAP" ?
> Non-js-supporting devices need very different handling, as all HTML has to
> be pre-built for them on the server.
ResourceLoader has a small st
Hello all,
Next week we'll be seeing the usual round of deployments, with these
highlights:
* For those that care about version numbers, we'll be starting 1.22wmf1
on Monday. :)
* On Wednesday we'll be deploying Phase II of WikiData to English
Wikipedia; expect big and good things!
For all
Max, do we still plan to detect javascript support for mobile devices, or
do you want to fold that into "isWAP" ?
Non-js-supporting devices need very different handling, as all HTML has to
be pre-built for them on the server.
On Fri, Mar 29, 2013 at 2:45 AM, Max Semenik wrote:
> Hi, we at the m
This sounds like a great plan. Thank you!
On Fri, Mar 29, 2013 at 2:45 AM, Max Semenik wrote:
> Hi, we at the mobile team are currently working on improving our
> current hit rate, publishing the half-implemented plan here for review:
>
> == Current status ==
> * X-Device header is generated by
Hi, we at the mobile team are currently working on improving our
current hit rate, publishing the half-implemented plan here for review:
== Current status ==
* X-Device header is generated by frontend Varnish from user-agent.
* There are currently 21 possible X-Device values, which we decreased to
Quick question. If I'm correct, Vagrant is supposed to be for setting up
development environments. Under this assumption, why is the mediawiki git
repository only fetched with a depth of 1? Isn't is pretty useless to have
a development VM you can't push or pull from?
*-- *
*Tyler Romeo*
Stevens In
11 matches
Mail list logo