Fireline responsibilities - carbon-design-system/carbon-for-ibm-dotcom GitHub Wiki

Aka support duty. Team members on fireline do not take up regular sprint load. For details and rationale: https://ibm.ent.box.com/notes/529594537702

Slack #carbon-for-ibmcom

On some common topics:

We should try to link to the expressive storybook when possible for people asking for the ‘core’ components.
We do drive users to the Carbon documentation for the core components, letting them know the expressive theme increases the type, container and icon size of the component.

Watching New issues lane

if urgent / critical (sev 1), bring to #digital-design-squad channel. Make sure it gets attention, and is moved to Doing.
answer questions
ask follow up questions
if not an issue with an easy answer, we move it to To be triaged lane, with our best guesses for labels (adopter support, bug, feature request, react, web components, package: styles)
cherry pick issues that are low hanging fruits

Watching for Pull requests that need design review

Keeping an eye on the Pull requests page for PRs that need design review, which are indicated with :eyes: eyes needed and Needs design review labels
At a daily basis, post the list of out standing PRs in Slack dds-designers channel.
Occasionally it might make sense to DM a designer assigned to PR if s/he has been unresponsive for a week.
This helps to unblock the dev team, prevent PRs becoming stale and collect too much conflicts, and keep up the visual design quality of the library