The-Strategy-Unit / The-Strategy-Unit/data_science
How do we decide to sunset/retire repos?
Open
Nobody has claimed this yet.
documentation
section: style guide
- Dominant language
- Jupyter Notebook
- Stars
- 11
- Forks
- 5
- Avg merge
- 5h 34m
- Merged PRs (30d)
- 1
Description
Would this be useful to discuss and write about for the style guide? I'm not sure we have 'rules' per se ('it depends'). Add to team standup AOB for discussion.
Was chatting about this with @Lextuga007, which prompted:
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
Review the linked issues in nhp_evidence_maps#96 and renal_evidence_map#49, then bring the question to the team standup AOB as requested. The work is complete when the team agrees whether retirement guidance belongs in the style guide and records the agreed criteria or decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100