Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Date

Participants

Discussion topics

Time

Item

Presenter

Notes

Adam Stankiewicz

  • [inform] @edx/paragon-working-group Github team was created, with the initial members as Ben W., David J., George B., and myself.

    • This Github team will be marked as the code owners of Paragon (and automatically request reviews when PRs are opened), and will require review/approval from at least one member of this team before merge.

  • I’d like to add Gabe and Marco to the Github team as well; same for at least the lead of RacoonGang in support of the blended development efforts.

  • Will update governance docs (including notes on how to escalate should PR reviews take longer than expected) and share decision around code owners later this week.

    • [discuss] What is a reasonable amount of time to get something reviewed? Within 24 hours? Within 48 hours?

Adam Stankiewicz

Adam Stankiewicz

  • [discuss] Jira workflow and “source of truth” of component status

  • Jira process established by Adam Butterworth:

    • Epic per component; its ticket status remains in “To Do” to leave it open for future modifications.

    • Implementation stories filed as children of the epic.

    • “Design System Status” field is updated accordingly.

  • https://openedx.atlassian.net/wiki/spaces/BPL/pages/3019571586/Status+of+Components?search_id=0db1f07f-b49c-4518-a156-6e4fca996dc0 is an automatically generated list of components and their associated statuses based on Jira epics, their “Design System Status”, and labels (e.g., “ready-for-eng”).

  • [discuss] Can we explicitly document our Jira workflow?

Adam Stankiewicz



Adam Stankiewicz

  • [clarification] What is the difference between Menu and Dropdown components from a design POV?

    • I’m slightly concerned that we have 2 components that are doing nearly the same thing without much guidance around when to use which and why.

Action items

  •  

Decisions

  • No labels