Create a checklist for MDN short surveys #17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As discussed in the previous WebDX meeting, an initial checklist to guide future discussions of MDN short surveys.
|
|
||
| # Mandatory fields | ||
| - [ ] Topic: The topic of the survey | ||
| - [ ] Category: E.g. CSS, JavaScript, Accessibility, documentation |
There was a problem hiding this comment.
is it the category of the pages on which the survey will be shown? if so, that should be clarified
| - [ ] Actions: Actions which will be taken based on the results | ||
| - [ ] Audience percentage: Suggested percentage of the MDN audience to be exposed to the survey. Default is 5%, if higher a clear motivation is needed. | ||
| - [ ] Questions: Suggested questions and answers | ||
| - [ ] Other: Any other information which is relevant. |
There was a problem hiding this comment.
Probably not "mandatory" :)
|
|
||
| This document lists the standard operating procedure for creating MDN short surveys. | ||
|
|
||
| # Mandatory fields |
There was a problem hiding this comment.
I realize these comes from the MDN short survey process, but suggestions below to improve a bit from there
short-survey-checklist.md
Outdated
| - [ ] Does any of the lists need to appear in random order? | ||
| - [ ] Do any of the items in a list need to appear in a specific order? | ||
| - [ ] Is there a free form field that needs to be excluded from random order? | ||
| - [ ] Is there a gating question that should diqualify people from taking the survey? |
There was a problem hiding this comment.
The MDN short survey guidelines also specifically asked not to ask PII beyond what's included in the privacy policy for the survey takers
Co-authored-by: Dominique Hazael-Massieux <[email protected]>
Co-authored-by: Dominique Hazael-Massieux <[email protected]>
Co-authored-by: Dominique Hazael-Massieux <[email protected]>
Co-authored-by: Dominique Hazael-Massieux <[email protected]>
Co-authored-by: Dominique Hazael-Massieux <[email protected]>
|
|
||
| This document lists points that need to be checked before publishing an MDN short survey. | ||
|
|
||
| # Mandatory fields |
There was a problem hiding this comment.
Suggested change
| # Mandatory fields | |
| # Filing a survey request |
|
|
||
| # Mandatory fields | ||
| - [ ] Topic: The topic of the survey | ||
| - [ ] Category: E.g. CSS, JavaScript, Accessibility, documentation |
There was a problem hiding this comment.
Suggested change
| - [ ] Category: E.g. CSS, JavaScript, Accessibility, documentation | |
| - [ ] Areas of MDN where the survey should show: E.g. CSS, JavaScript, Accessibility |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed in the previous WebDX meeting, an initial checklist to guide future discussions of MDN short surveys.