- Given participant questions tasks all meet definition of done
- then the participant questions feature should be enabled on BETA
|beta: Enable $wgCampaignEventsEnableParticipantQuestions
|T341392 Mark the CampaignEvents extension as stable
|T321822 [EPIC] Participant Questions - MVP
|T347591 Remove original data collection text if Participant Questions enabled
|T347608 Remove feature flag for Participant Questions
|T347607 Enable Participant Questions in production
|T339246 Enable feature flag in BETA for Participant Questions
Wait, I just remembered my comment in T321822#8876110: I'm not really sure if this can be enabled on beta, at least for the questions that are considered PII. Other PII-related features are intentionally kept out of beta because the data there is much more easily accessible, see for instance T214820 and T188862. I don't think this feature here would be different.
Indeed, that's why I said "not really sure" instead of "I'm sure we can't". However, my reasoning was: even if beta is meant for testing, there is no notice in the registration form or elsewhere informing users that the information they write there is not confidential. For instance, see the warning about passwords displayed upon logging in. I'm worried that someone could still provide real data, e.g., because they don't realize that it wouldn't be private on beta.
Where would we test if we are discouraged to use beta?
We need these two constraints to be able to move with these tasks.
1 - List of answers is finalized
2 - Get an answer if we can store PII data on beta
3 - Decide to show only not PII on beta