The-Strategy-Unit / The-Strategy-Unit/data_science
The code repository lifecycle
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 11
- Forks
- 5
- Avg merge
- 5h 34m
- Merged PRs (30d)
- 1
Description
How can we indicate to each other and to the public about the lifecycle status of a repo?
This helps people decide whether the code is current, for example, without necessarily needing to contact authors.
Some questions to address in the session:
- Possible states (active, just a concept, moved, etc).
- Making a decision (project status, time since last activity, etc).
- Making it clear to users (README badges, README callouts, archiving).
- Recognising that things change, man.
Feel free to add more ideas/questions below.
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 with the open questions in this issue, then inspect the repository README for existing badges or callouts. Resolve the proposed lifecycle states, decision criteria, and user-facing signals; done means the agreed approach is documented and actionable.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100