Call-for-Code-for-Racial-Justice / Call-for-Code-for-Racial-Justice/Open-Sentencing
Identify Data Gaps or Needs for Each Step (Based on User Stories)
- Dominant language
- No language data
- Stars
- 76
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
### Background on the problem the feature will solve/improved user experience
Based on reviewing/implementing updates from the user stories, work on figuring out any data missing or still needed. Document clearly.
### Describe the solution you'd like
Once User Stories put into place, figure out if all data is there or more is needed. Document clearly.
### Acceptance Criteria
Mark the data going into / out of each step. Document clearly any gaps.
Contributor guide
Research direction
Start by reviewing the user stories and the related feature updates to identify each step and the data it uses. Mark the data entering and leaving every step, then document any missing or still-needed data as the completion criterion.
Written by the indexing model from the issue text.
Assessment
- Domain
- data, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100