rubyforgood / rubyforgood/alongwithyou
MVP exit criteria tracking checklist
Open
Nobody has claimed this yet.
type:tracking
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 4
- Avg merge
- 9h 34m
- Merged PRs (30d)
- 16
Description
Single tracking issue, checklist from brief section 14:
- Approved scope requirements and acceptance criteria pass
- Authentication, authorization, data deletion, and recovery behaviors documented and tested
- No prohibited high-risk field is collected
- Core flows pass accessibility review and testing with representative users
- Users can create, read, update, and delete their included information
- Users can recover from validation, network, and server errors without losing completed work
- Privacy notice, support path, content ownership, hosting ownership, and incident ownership are assigned
- Stakeholder sign-off that the experience is simple, supportive, and consistent with the mission
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
No files, tests, or entry points are named. Start with brief section 14 and identify the implementation, documentation, accessibility, privacy, and ownership areas covered by each checklist item; done means every item has evidence of completion and stakeholder sign-off.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100