Smalyshev added a comment.
Not sure what's the plan for this one - are we still going to do it?TASK DETAILhttps://phabricator.wikimedia.org/T170547EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: SmalyshevCc: Smalyshev, JanMuehlig, Lydia_Pintscher, Jonas,
daniel added a comment.
In T170547#3443359, @Jan_Dittrich wrote:
I thought that one can collect metrics even without AB-Testing, but one can't AB-Test without metrics.
Yes, exactly. That means metrics blocks A/B-testing, because A/B testing can't be done without metrics. Since the child blocks
Jan_Dittrich added a comment.
I thought that one can collect metrics even without AB-Testing, but one can't AB-Test without metrics. But as long as both collecting and AB-setup are considered, I don't mind which is the parent…TASK DETAILhttps://phabricator.wikimedia.org/T170547EMAIL
daniel added a comment.
In T170547#3443236, @Jan_Dittrich wrote:
I suppose for me it was not evaluation of the data, but getting the right data needed for the right evaluation
In that case, the dependency between the tasks is going the wrong way: We need to tracking code before we can do
Jan_Dittrich added a comment.
I'm asking because implementing the tracking is a precondition to A/B testing,
but A/B testing is a precondition to evaluating the data.
I suppose for me it was not evaluation of the data, but getting the right data needed for the right evaluationTASK
daniel added a comment.
The cope of this ticket is a bit unclear - does it ask for the tracking mechanism to be implemented, or for the data to be available and evaluated? I'm asking because implementing the tracking is a precondition to A/B testing, but A/B testing is a precondition to evaluating
daniel added a comment.
A few comments from a discussion with Jan:
Track the entry point: quick search or statement editor
the clock should start ticking as soon as the search box gets the focus
we may also want to track letters entered (prefix length) before selection
"reactivity" could be
