Create structure on Methods/UXGuide as a team new designers and volunteers can participate in.
bpdesigns opened this issue · comments
what structure to create?
- create sprint meetings - planning/review/retro/ regular (not daily) standups
- team "how we work" articulation, doc or activity. Reference team onboarding materials that includes how we use labels
- define the best way to label issues and document that in repo wikis
- define what a good first task looks like
- structure quick github issues for folks to have early success
a good initial task might look like:
- meet with Methods/Guide product owners for context
- updating text on a site using github
- get an example of how teams are using this method and document two.
Created issue #304 in the ux guide repo to see if we can align labels between repos
With that, what else needs to be done to call this closed, @bpdesigns? Do we want to document what a good first task looks like in the README? Is it still needed?
I think we should skip that last one. I believe we were thinking of it for folks who were new to github but I realize now that a good first issue is likely different for different people.