GSA / GSA/service-design-analytics
consider adding CTA and how-to-contribute guidance
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 7
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Goal
Engage interested parties in public service design analytics work, along data specification, best practices, and more.
Questions
- how to engage meaningfully around Service Design Analytics in a multi-agency environment?
- what does success look like?
- how do we identify Service Design opportunities? and what does MVP look like? what does the rest of the maturity scale look like?
- what standards are in use? are worth looking into?
Ideas
- include project goals
- include opportunities to share and collaborate (online and asynchronous stuff)
- include events, trainings (in-person stuff)
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 file, test, or entry point is named. Review the existing project materials first, then define the scope for the CTA and contribution guidance; done would require an agreed description of goals, engagement paths, success criteria, MVP and maturity scale, and relevant standards.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100