Since all the subtasks are resolved, can this be resolved?
Tue, Mar 19
If the code for QuickSurveys loads AFTER MobileFrontend, the hook will be registered too late and the survey will never show.
The task that led to the introduction of the mobile.betaoptin event: T111188
- Data for clicks to all new links can be collected using https://meta.wikimedia.org/wiki/Schema:MobileWebMainMenuClickTracking
@Jdlrobson: Would changing the message require that any existing workflows are updated or would folk still have to refer to the tag by its name when querying the DB or specifying it as an argument for the tagfilter parameter in an MW API call, for example? That is, would the tag look like it was called "mobile web action" but still actually be called "mobile web edit"?
Mon, Mar 18
Fri, Mar 15
As for on-wiki uses by the general public:
Thu, Mar 14
Would replacing the textarea with a div if the page is protected work? This would be cleaner than manipulating the DOM in JS IMO.
This appears to have been fixed in https://en.wikipedia.org/w/index.php?title=Calculus&type=revision&diff=887407355&oldid=886050145, which is the fix that @Tacsipacsi proposed in T217526#5012719.
Wed, Mar 13
Tue, Mar 12
Fri, Mar 8
Thu, Mar 7
@mforns: I'm pretty sure this is deployed and (re)started as there are log lines appearing in Kibana for the following query: https://logstash.wikimedia.org/goto/36329f5fd2348e181177ff879800d9c0
Wed, Mar 6
Tue, Mar 5
Mon, Mar 4
Thu, Feb 28
Also CCing @dr0ptp4kt
Wed, Feb 27
- Nice find, @Jdlrobson!
- Should we discard surveys that required CentralNotice to be loaded if it isn't?
@Tbayer pointed me at this task during our 1:1 yesterday.
Tue, Feb 26
Feb 14 2019
@ovasileva: This is in Triaged but Future in our backlog but doesn't appear to have a priority.
Following @Tbayer's advice, I did a little digging in wmf.webrequest:
The "Extra data:" error is raised by json.loads as it encounters the ; character at the end of the JSON string:
Feb 13 2019
@Edtadros and I worked through testing the
4th 5th acceptance criterion together during our 1:1 today.
Feb 12 2019
I've removed this from our (Readers Web's) kanban board as Proton has been handed over to Readers Infrastructure.
@ovasileva: Could you update https://phabricator.wikimedia.org/project/profile/2960/ accordingly?
Per our (@Jhernandez, @Tgr, @pmiazga, and me) conversation in last Thursday's Audiences Platform Sync, Proton has officially been handed over to Readers Infrastructure for ongoing maintenance. I'll follow up with an email to email@example.com and firstname.lastname@example.org to confirm this.
Drop proton-staging as it is not used (chromium-pdf.reading-web-staging.eqiad.wmflabs) - can be done after the handoff
@Capt_Swing: Thanks for the additional detail. Given that, I think it's reasonable to keep both tasks separate.
Feb 11 2019
To minimize the traffic sent to the stats endpoint we should track MinervaClientError counter only once after the request is done, not on every error occurrence.
@Joe: Yes. That's correct. Do note that this is the current behaviour for the beta mode of the mobile site (visit https://m.mediawiki.org/wiki/Special:MobileOptions and enable "MediaWiki ß"). I think it's worth wondering how caching best works for both that and this new opt-in feature.
Feb 9 2019
Thanks for hashing this out, y'all. FWIW I think the proposed interim solution seems reasonable.
Feb 8 2019
Feb 7 2019
FeaturesManager::isFeatureAvailableInContext will need to be updated to take a User object and check the stored value of AMC. This is needed for the talk tab task (T212216).
☝️ I pulled out the very technical AC from the AC section and into the Developer notes section as:
I apologise for not including an approver on the task. I wasn't actually sure who should approve access in this case but realise now that @Nuria would've been the sensible choice.
Feb 6 2019
What's the rationale for this skipping Needs QA (the first time it moved to Ready for Signoff, I guess)?
AFAICT there's no instrumentation about how (or how frequently) our various overlays are being interacted with. Nevertheless, it's a production feature, so we should do our best to make sure that we don't introduce regressions while doing this refactoring. With that in mind, could we add tests so that this can go through Needs QA.
Feb 5 2019
I'll add a note as to why my proposed change should work and testing instructions for reviewing engineers and @Edtadros.
Is there any chance that you did get time to look at this during All Hands, @hashar? I know it was very busy.
Jan 30 2019
select round(sum(if(uri_query like '%Special:Log%', 1, 0)) / sum(1) * 100, 2) as log, round(sum(if(uri_query like '%Special:AbuseLog%', 1, 0)) / sum(1) * 100, 2) as abuse_log, sum(1) as all_clickthroughs from wmf.webrequest where year = 2019 and month = 1 and day = 28