opensafely / opensafely/documentation
Add a checklist for users to work against before the co-pilot period
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 48
- Forks
- 10
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 17
Description
Mentioned in the OpenSAFELY researcher show and tell event today.
So that researchers get the most out of their co-pilot time and, for instance, aren't spending time getting software installed (which might require some wrangling with their IT department).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the documentation section covering researcher onboarding or preparation for co-pilot time. Turn the installation requirement and other useful pre-period tasks into a checklist, using the issue context to identify what researchers should complete beforehand. Done means the checklist is published where researchers will find it before their co-pilot period.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100