2021-10-28 Meeting notes

PAR board statuses

@Gabriel Weinberg (Deactivated)

• Jira Board doesn’t reflect our current process. Statuses like “to do” and “in progress” are not clear enough against our current working process. Should reflect various stages of component life cycle, such as “ready for engineering” or “ready for design specs”. Proposed board status changes (swim lanes):

  • Needs proposal (needs detail in order for PWG to determine if it should be a component or variant)

  • In Design (PWG agrees it should be a component or variant, needs design specs)

  • Design Spec Review (Needs PWG input)

  • In Engineering (design specs have been approved in PWG)

  • In Q/A (design and technical)

  • Shipped (now live and usable by designers and engineers using Paragon)

• Design system status proposal:

  • “Stable” (currently live and usable by designs)

  • “Needs Design Update“

  • “Needs Engineering Update“

  • “Deprecated” (no longer available for use)

• Group feedback:

  • Example:

    • Data Table Epic

    • Data Toggle View “Feature” Task

    • Design and engineering “child of” tasks

  • DataTable has a component epic DataTable Toggle view has a project epic with child tickets. project epic shows up in swim-lanes. component epic has design system status

    child tickets of project epic do not show up in swim lanes

  • is it too complicated to make sure people are keeping their tickets up to date?

  •