This is a small script that we adapt (on a per project basis) as a type of'user testing' aka 'contributor testing'. Participants must not be familiar with the project, code or community, although they should be confident with the technology.
Steps should allow for someone reasonably confident with the technology to do a scan of project assets, people and tinker with the environment in 1.5 hours or less. It's OK if the environment build is not completed, the intention is to see how well a project is setup to accommodate those without luxury of hours of time to figure things out.
- Open Your browser, and navigate to the project main page (provide this link).
- Learn about this tool, project, initiative (5 minutes)
- What did you learn?
- Do you have questions still, of so what are they?
- Find and follow the 'getting started' information to setup an initial instance, copy or version of the project.
Even if you didn't finish...
- How did that go?
- What was well documented? What could have been improved and why?
- Find the Code of Conduct.
- Find information on the community leaders and staff.
- Log into the chat channel and say hi.
- Review the contributing document (CONTRIBUTING.md usually, but sometimes the README.md)
- How did that go?
- What did you observec about the community channel?
- If you found information on the community leaders/staff how did that information make you feel more or less likely to contribute?
- Based on the contributing document, do you feel about contributing? What would you attempt first?
- Is it easy to understand who to ask for help, and who project leaderhip is?
- Complete the environment build steps, use the community channel to ask for help if you're stuck, or have questions.