Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Finalize and publish definition of done #4996

Closed
2 of 3 tasks
aubrey-oneal opened this issue Apr 29, 2024 · 2 comments
Closed
2 of 3 tasks

Finalize and publish definition of done #4996

aubrey-oneal opened this issue Apr 29, 2024 · 2 comments
Assignees
Milestone

Comments

@aubrey-oneal
Copy link
Member

aubrey-oneal commented Apr 29, 2024

After the workshop, we have a more solid definition of done. Let's get this finalized so that we can compare our assets to the definition of done.

Acceptance criteria

  • Boxnote: Write up a definition of done based on our mural and workshop
  • Meet with Scott, Jeannie, Linda, Jeff, and other stakeholders to finesse this
  • Publish on both the product PAL and core site.
@sstrubberg sstrubberg added this to the 2024 Q2 milestone May 8, 2024
@carrenelloyd
Copy link

  • Audit this against it in the Product PAL
  • Outline where we want the community to contribute and where Core will help (Code + Kit + Docs)

Notes from Post workshop sync on next steps
Needs refinement: Need to get answers to these questions
Where to publish this (maybe on both PAL + Core)
What are we publishing?
What are the sections?
Do we bring in PDLC?

This could be a visual representation on the published site—highlight areas where Core could help. PDLC highlight “discovery zone”

@aubrey-oneal
Copy link
Member Author

Closing this for now as we have the rough draft box note and need to refine next steps.

Ideas for next steps are:

  • Ask devs in core, dotcom, and product to discuss which of the technical requirements they can achieve
  • Maybe have a visual designer do a really rough mockup of how we might display these requirements in contributing section without being overwhelming.
  • Determine which of our requirements might need more documentation work. I.e. Making Figma templates of Style, Code, Accessibility docs in addition to MDX. And then prioritizing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

3 participants