Change Details

=== Background information We will be running more waves of the safety survey and will be doing it on Russian and Japanese wikis. Let's see if we can test how this would work. Also, there have been performance surveys run on these wikis with no issues. === Questions [] If we run a survey with coverage 0 on both wikis, do the surveys appear as we expect? [] Are there any other considerations we should be aware of?

=== Background information We will be running more waves of the safety survey and will be doing it on Russian and Japanese wikis. Let's see if we can test how this would work. Also, there have been performance surveys run on these wikis with no issues. === Questions [x] If we run a survey with coverage 0 on both wikis, do the surveys appear as we expect? The survey requires a number greater than zero to be triggered. For example 0.01 will cover 1 percent of the active impressions, whereas 0.1 will cover 10 percent. So a number greater than zero is always required to run a survey. A survey with 0 coverage will be enabled but not triggered. [x] Are there any other considerations we should be aware of? Yes, since the LocalSettings.php file is merge from PROD to BETA we must be aware of the survey config in BETA so that we don't overwrite an existing survey. QuickSurvey provides a (+) and (-) feature whereby adding the +/- will either override BETA config with production or merge the two configs. You can usually tell what is being overwritten or merged by checking the Jenkins diffOuput console in gerrit.

=== Background information We will be running more waves of the safety survey and will be doing it on Russian and Japanese wikis. Let's see if we can test how this would work. Also, there have been performance surveys run on these wikis with no issues. === Questions [x] If we run a survey with coverage 0 on both wikis, do the surveys appear as we expect? The survey requires a number greater than zero to be triggered. For example 0.01 will cover 1 percent of the active impressions, whereas 0.1 will cover 10 percent. So a number greater than zero is always required to run a survey. A survey with 0 coverage will be enabled but not triggered. [x] Are there any other considerations we should be aware of? Yes, since the LocalSettings.php file is merge from PROD to BETA we must be aware of the survey config in BETA so that we don't overwrite an existing survey. QuickSurvey provides a (+) and (-) feature whereby adding the +/- will either override BETA config with production or merge the two configs. You can usually tell what is being overwritten or merged by checking the Jenkins diffOuput console in gerrit.