Decide on process of how survey results get incorporated into specification doc

[edwardchalstrey1]

We are trying to create a pipeline from all raw survey results to open issues for community discussion on the specification repo.

The survey responses are broadly split into 3 categories, and we have created an issue for each to show how these answers can be incorporated into the repo:

1. Multiple choice answers (Questionnaire summary: Decide how to handle multiple choice Qs #11)
2. Free text (answers from a definable set) (Questionnaire summary: Decide process for handling free text (answers from a definable set) #12)
3. Free text (answers from a non-definable set) (Questionnaire summary: Decide process to handle free text (answers from a non-definable set) #16)

Currently, we are focused on preparing 1) and 2) for the community to engage with. 3) will take more time to consider a rigourous analytical approach that is comprehensive and clear. We're also working to clean the data and accompanying analytical code to remove possible identifiers, and share these more foundational resources with the community.

Current process:

1. Decide how issues for each type of question will be shared as an issue on the specification repo
2. Prepare open, reproducible code that allows us to prepare these issues for each type of question:

• Questionnaire summary: Results from multiple choice questions #17
• Questionnaire summary: Results from free text (answers from a definable set) #18
• Questionnaire summary: Results from free text (answers from a non-definable set)  #19

3. Use this code to evaluate responses, and present them as laid out in:

• Questionnaire summary: Decide how to handle multiple choice Qs #11
• Questionnaire summary: Decide process for handling free text (answers from a definable set) #12
• Questionnaire summary: Decide process to handle free text (answers from a non-definable set) #16

4. Use these results to open issues for the community to discuss on the specification repo