Get the quick surveys extension deployed to Wikimedia wikis without any enabled surveys.
First campaign to be decided by Anne, Jon and I before this can happen.The first survey is defined in T113443
Description
Description
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | leila | T112326 [Epic] Reader segmentation research - Q2 | |||
| Resolved | • jhobs | T113443 First QuickSurvey for reader segmentation research - external survey | |||
| Resolved | Jdlrobson | T111445 GOAL: Run our first survey campaign | |||
| Resolved | • jhobs | T110661 Deploy QuickSurveys extension to the English Wikipedia | |||
| Resolved | • rmoen | T110662 QuickSurveys extension should pass security review | |||
| Resolved | • rmoen | T110199 Get QuickSurveys enabled on beta cluster | |||
| Resolved | Jdlrobson | T110200 Spike: Release first version of QuickSurveys | |||
| Resolved | Jdlrobson | T111292 Don't load Mustache and Hogan on mobile | |||
| Declined | None | T111472 QA: No browser tests covering QuickSurveys in mobile skin | |||
| Resolved | Jdlrobson | T110198 Add basic browser tests | |||
| Resolved | • bmansurov | T110225 Add basic browser tests: external surveys | |||
| Resolved | phuedx | T110196 Badly defined surveys cause issues | |||
| Resolved | Jdlrobson | T114485 QuickSurveys throws exception on non-HTTPS |
Event Timeline
Comment Actions
I think we're ready to do this with the 0.6 release (maybe we should rename to 1.0?). I'm assuming this involves including the extension within mediawiki-config and letting it ride the train, not actually doing a SWAT deploy? @bmansurov or @Jdlrobson, confirm? If there's more to it than just including the wfLoadExtension line, then maybe someone would want to walk me through it.
Comment Actions
mediawiki-config changes don't 'ride the train'. You shouldn't be deploying new extensions as part of SWAT windows either.
Comment Actions
Thanks for the info. I haven't deployed a new extension before, so if there's a mediawiki page you could point me to re:the process, I'd appreciate it!
Comment Actions
You need to make sure the extension is getting branched in the make-wmf-branch tool, is currently included in the deployed code, and then you can add your wfLoadExtension call, after coordinating with @greg. https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment has details of the process up to that point.
Comment Actions
@atgo - do we know the survey we want to run first? It would be good to set this up at the same time for testing purposes.
Comment Actions
Looks like this will be next Tuesday.
I'll make the necessary patch but I'll need someone to own it and make this happen next sprint.
This comment was removed by • jhobs.
Comment Actions
Change 251130 had a related patch set uploaded (by Jdlrobson):
Deploy QuickSurveys to all wikis
Comment Actions
Change 251144 had a related patch set uploaded (by Jdlrobson):
Add QuickSurveys branch
Comment Actions
I confirmed with Anne that only English Wikipedia is needed for the time being due to lead time on being able to translate the survey.
Comment Actions
Code Review isn't quite the right place for this but then neither is Ready for Signoff.
Comment Actions
I'd appreciate some review and +1s on the patchs. After all there are only 2 r's in array.
Comment Actions
Change 252606 had a related patch set uploaded (by Jhobs):
Deploy QuickSurveys to English Wikipedia
Comment Actions
@phuedx I noticed this task is still linked from InitialiseSettings.php, wmgUseQuickSurveys. Considering the recent performance improvements which seem to prevent loading client-side modules and data when no surveys are configured, do you think we can simplify the configuration to enable QuickSurveys everywhere, and just rely on wgQuickSurveysConfig to enable or disable specific campaigns? -> New task created T317841: Simplify QuickSurveys configuration by enabling everywhere.