A collection of survey questions we've used at Microsoft's Open Source Programs Office (OSPO)
Перейти к файлу
microsoft-github-policy-service[bot] b0d33b59e8
Microsoft mandatory file
2022-08-17 14:45:16 +00:00
.github/ISSUE_TEMPLATE updates 2021-12-15 09:49:13 -08:00
about-you updates 2021-12-15 09:49:13 -08:00
company-innersource/participation updates 2021-12-15 09:49:13 -08:00
company-opensource Merge branch 'microsoft:main' into main 2021-12-15 09:57:40 -08:00
foss-fund Merge branch 'main' of https://github.com/emmairwin/OSPO-Surveys into main 2021-12-15 09:49:32 -08:00
.gitignore Initial commit 2021-09-30 17:44:44 +00:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2021-09-30 11:08:10 -07:00
CONTRIBUTING.md Update CONTRIBUTING.md 2021-12-15 11:41:31 -08:00
LICENSE.txt Create LICENSE.txt 2021-09-30 11:13:41 -07:00
README.md Update README.md 2021-12-15 11:38:28 -08:00
SECURITY.md Microsoft mandatory file 2022-08-17 14:45:16 +00:00

README.md

Microsoft OSPO-Surveys

A collection of survey questions we've used at Microsoft's Open Source Programs Office (OSPO).

Categories

Questions are grouped by topic area, and then survey question which we welcome contributions to, should you use these and identify ways of improving. Beneath each topic are, is the list of questions.

We've also included survey questions for FOSS Fund awardees, to better understand how to support maintainers with and beyond the fund. These questions should all be optional.

Question Standards

Something we learned in previous surveys is that providing a 'Neither Agree Nor Disagree' option, dilutes the responses if a large number of people opt for that. It really tells us nothing and makes the other responses less actionable. As a result the question standard for agreement is structured this way:

  • Strongly Agree
  • Agree
  • Disagree
  • Strongly Disagree
  • Other _______________________

With 'Other' being a place people can elborate on why none of those responses fit.

Question Best Practices

  • Each section should include a final question 'If you would like, please use this space to expand your answers about the [Section Area].'
  • Unless you have a specific need to know who responded in what way, provide an option for people to respond anonymously to encourage honestly.
  • All surveys run on behalf of an Open Source Program's Office (OSPO) should include privacy and data retention policy.
  • Unless otherwise agreed upon by your legal and HR team, no senstive information should be collected including dimensions of diversity.
  • Should you run an external-facing survey you can sometimes asking questions about diversity dimensions, but only if there ais no personally identifying information including location. For more running external surveys please reach out to the CHAOSS DEI working group.

Contributing

Contributions are welcome! Please checkout our CONTRIBUTING.md file to learn more.


Copyright (c) Microsoft Corporation. Licensed under the Creative Commons Attribution 4.0 International (CC-BY-4.0) license.

Trademarks This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsofts Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-partys policies.