array( "@description"=> "description of the survey", "description" => "Reader-segmentation-1-description", // (blank) "@link"=> "external link to the survey (must be https)", "link"=> "Reader-segmentation-3-link", //https://docs.google.com/forms/d/171PLghcRKF5ir6hbexBv_6CnxchikDprS_GHxgylhKg/viewform "@question"=> "survey question message key", "question"=> "Reader-segmentation-3-message", // Answer three questions and help us improve Wikipedia. "@privacyPolicy"=> "message key for privacy policy. May contain links.", "privacyPolicy"=> "Reader-segmentation-1-privacy", // Survey data handled by a third party. [https://wikimediafoundation.org/wiki/Survey_Privacy_Statement Privacy]. "@coverage"=> "percentage of users that will see the survey", "coverage"=> "0.00005", // 5 out of 100K (0.005%) "@platform"=> "for each platform (desktop, mobile), which version of it is targeted (stable, beta, alpha)", "platform"=> array( "desktop"=> ["stable"], "mobile"=> ["stable"] ) )
Description
Description
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | leila | T112326 [Epic] Reader segmentation research - Q2 | |||
| Resolved | • jhobs | T116433 Third QuickSurvey for reader segmentation research - run multiple choice survey | |||
| Resolved | • jhobs | T114164 QuickSurveys: Schema changes |
Event Timeline
Comment Actions
@atgo Is there a limit on the number of tags we can show to the survey participant? Also, do we have a sample of QuickSurvey mock-ups I can look at before confirming that all blockers are listed correctly for the current task?
Comment Actions
@leila you can see them here
Mobile:
http://en.m.wikipedia.beta.wmflabs.org/wiki/Headings?quicksurvey=true
Desktop: http://en.wikipedia.beta.wmflabs.org/wiki/Headings?quicksurvey=true
Comment Actions
@atgo: awesome!
There's some minor vertical alignment or padding issue with the text of the buttons that probably needs to be fixed. Also, the div doesn't seem to extend enough to wrap the 4 tags.
Comment Actions
@jhobs If we want the survey to be deployed tomorrow, what is the deadline for finalizing the information in the description. We're actively working on them and should be able to finalize them in the next 3 hours.
Comment Actions
Sorry, but this will not be able to be deployed tomorrow, period. We're listing the bug where no EventLogging table was created by the first survey (T119152) as a blocker for any new surveys until it is investigated, and there's just no way it could be diagnosed, fixed, merged, and deployed by tomorrow's SWAT. In addition, it's much better for us to not SWAT anything right before a holiday and we're more likely to get less skewed results afterwards. The earliest this could be deployed would be Monday, November 30th.
Comment Actions
We shouldn't run this during the Fundraiser, so it looks like it will have
to wait until January.
Comment Actions
@jhobs, what @atgo said about the timing. If we don't do it this week, it seems it will be deferred to Q3 because of Fundraising.
Re T119152, that's not a blocker for this task. We don't need EL tables and responses for this specific survey. With this information, can we make this survey happen tomorrow?
Comment Actions
Ok, ignore my previous comment then. For history's sake, we had an IRC discussion that led to the conclusion that we will be able to run this survey in Q2 by SWAT deploying tomorrow morning.
Comment Actions
Change 254908 had a related patch set uploaded (by Jhobs):
[WIP] Third QuickSurveys external survey
Comment Actions
@jhobs the array in Description is ready. Please go ahead with it. One note about the sampling rate: I kept the description based on the definition of the first survey, and not the second (not sure which one is the way we want to continue using). We need 5 out of 100K. :-)
Comment Actions
@jhobs, while in an internal thread we are figuring out the sources of very few number of responses, can you multiply Coverage by 100, so change the value from 0.00005 to 0.005? I'll update the email thread, too.
Comment Actions
Change 255448 had a related patch set uploaded (by Jhobs):
Disable QuickSurveys reader segmentation survey
Comment Actions
The patch to disable this survey has been scheduled for Monday's morning SWAT (8-9am PST).