opensafely-core / opensafely-core/reports
Add a review step before publication of routine reports [wip]
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 5
Description
Best practice on mandating review is in place in place across a lot of Bennett Institute websites. I propose that we introduce a mandatory review stage before publishing new/updated reports for reports.opensafely.org
This may include code review but at this stage I'm most keen on getting a sense check on charts, figures etc before they are made publicly available front and centre.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the current publication workflow for reports.opensafely.org and the existing review practice described for other Bennett Institute websites. Define what must be reviewed, who approves it, and where the review gate belongs; the work is done when a concrete, agreed workflow for charts, figures, and other report content is documented and actionable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- content, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100