[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
[inform] Started to document the discrepancies between the Figma spec and what’s currently implemented in Paragon
I plan to get this more fleshed out and ensure tickets are filed for the discrepancies this week, and how this will play into the Blended Development backlog.
@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.
Status of Components 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
[clarification] Why is Card.Status it’s own distinct thing when it’s essentially an Alert used within the card contents?