I'm going to be gone for the next couple weeks on vacation, but I want to
make sure that someone follows up on further investigating bug 62241. Now
that the debugging code has been merged, some time next week there will be
a new debugging log that should help us solve this bug.
The believe the new debugging log will be created as:
/a/mw-log/upload.log on fluorine
For now, this log will only be recording bad filename errors (both on
desktop and mobile). It should include enough information to figure out why
the badfilename error was triggered, although you may need to refer to the
UploadBase class to decipher it.
If you have any questions about this, please let me know by the end of
In MobileFrontend I wish to remove the 'Privacy' link at the bottom of
all mobile view pages. Can I do that somehow via $wgMFRemovableClasses
in my single LocalSetttings.php, rather than having to put a '-' in a
MediaWiki namespace page on each of my wiki family members?
We introduced a pre-review hook in mobile that makes it hard for you
to submit new code when there is existing code to review (check out
 if you are interested)
The problem I find is it tells _me_ to do code review, but all the
patches belong to me so I can't review them. I can poke people and ask
them to review it, but this usually isn't fruitful as it results in
"I'll do that later" or "I'm busy right now".
I feel that the pre-review hook is making me aware of other people's
patches more often but I've had to force override it a few times like
just now when I've found that I own all the existing patches (as I'm
scared I'll lose the patch or forget about the patch otherwise). This
actually has had the effect on me of investing time in other projects
like data analysis, mailing list discussions, coding on VectorBeta,
Limn and core rather than concentrating my energy on MobileFrontend. I
also feel reluctant to pick up new cards to work on when I'm in this
limbo state as I don't want to overwhelm the code review queue or end
up managing various patches that might conflict with each other.
I feel like I've contributed less to the MobileFrontend project as a
result - not sure if this is a good or a bad thing. That said it is
certainly a frustrating thing for me as I want to work on it more...
Something to think about.
ConfirmEdit extension has run out of captcha images. That needs to be
there - Kaldari do you have any ideas - is this related to your message
Loading pages tests failed due to 503s on beta labs
Watchlist tests are still waiting for
https://gerrit.wikimedia.org/r/120938to be merged
VisualEditor is indeed broken due to a Parsoid error.
While working on https://gerrit.wikimedia.org/r/#/c/123117/ I
encountered the parameter 'agent' in action=zeroconfig API call, which
is part of the extension providing Wikipedia Zero. I was trying to
figure out what it does, and the most I got was this documentation
agent - When setting type to message, include a source
agent value as well
which is totally unclear :)
Can someone who works on Zero stuff clarify? Also what is the default
value? Is it the current user-agent? If not, why not?
Yuvi Panda T
We are considering changing the colours in the diff page view for mobile.
Previously Vibha and Munaf had explored this (see results below). Have we
run similar tests for the new colours on the diff page?
---------- Forwarded message ----------
From: Munaf Assaf <massaf(a)wikimedia.org>
Date: Thu, Mar 28, 2013 at 3:21 PM
Subject: Diff views for the colorblind
To: Jon Robson <jrobson(a)wikimedia.org>
Cc: Vibha Bamba <vbamba(a)wikimedia.org>, Maryana Pinchuk <
Vibha and I tested these settings out and they work pretty well.
[image: Inline image 1]