Page MenuHomePhabricator

Implement schema for portal A/B tests and background data
Closed, ResolvedPublic8 Estimate Story Points


We need implemented for the testing and background data!


Related Gerrit Patches:
wikimedia/portals : event logging

Event Timeline

Ironholds raised the priority of this task from to Needs Triage.
Ironholds updated the task description. (Show Details)
Ironholds added a subscriber: Ironholds.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 29 2015, 8:42 PM
Restricted Application added a subscriber: StudiesWorld. · View Herald TranscriptNov 3 2015, 7:48 PM
Jdrewniak claimed this task.Nov 3 2015, 7:48 PM
Jdrewniak set Security to None.
NOTE: If we are going to pull in any new JS libraries (such as for JSON generation), they need to be approved by security.
NOTE: If we are going to pull in any new JS libraries (such as for JSON generation), they need to be approved by security.

Was it discussed in some meeting that we were? That comment lacks wider context.

@Ironholds: My comment appears to have been truncated. I'm not sure if it was censored because I said something that I shouldn't have said (I didn't think so), or if it was a phab glitch, or if it was user error.

There was a small meeting, in which we were reminded of the policy that any third-party code being brought in should be reviewed by our securiity team.

Gotcha. And, was that because something had happened...? I wasn't in that 'small meeting' and I'm left trying to glean if this means that we need to integrate wider code and that'll slow down the EL implementation, or what.

The meeting was about T117512: Give security a heads-up about plans and scripts to deploy portal from gerrit, and was attended by Chris, Max, Erik, and me.

After getting through the main topic, we mentioned we would be adding JS event logging and A/B testing capabilities to the portal, at which point he reminded us of this policy. I felt it was valuable to pass it along, especially to our newer developers. I don't think we know yet whether this will impact our schedule.

@Ironholds, @ksmith Third-party code shouldn't impact the event logging implementation schedule, as we're only using a handful of third-party snippets for polyfilling older browsers. We're not using (and were given instructions not to use) any third-party libraries (no jQuery, not even mw.js) which brings it's own challenges, but none relating to security concerns.

Change 251091 had a related patch set uploaded (by JGirault): event logging

Restricted Application added a project: Discovery. · View Herald TranscriptNov 17 2015, 10:16 PM

Change 251091 merged by MaxSem: event logging

Jdrewniak edited a custom field.Dec 8 2015, 10:21 PM
Deskana closed this task as Resolved.Dec 23 2015, 5:33 AM
Deskana triaged this task as Medium priority.
Deskana moved this task from Needs triage to On Sprint Board on the Discovery board.
debt moved this task from Done to Completed on the Discovery-Portal-Sprint board.Jan 26 2016, 12:33 AM