November 2019 Planning

[designertyler]

Timeline

Week 1: October 7th, 2019 - October 11th, 2019

• Project kickoff
• Start release cycle

Week 2: October 14th, 2019 - October 18th, 2019

• Project work - no endgame tasks

Week 3: October 21st, 2019 - October 25th, 2019

• Project work - no endgame tasks

Week 4: October 28th, 2019 - November 1st, 2019

• Patch release
• Pre-endgame planning
• Code freeze by Friday, November 1st

Week 5: November 4th, 2019 - November 8th, 2019

• Endgame - All week
• Release Candidate cuts and smoke tests

Week 6: November 11th, 2019 - November 15th, 2019

• Release, Endgame done, demo, retro, planning for next release
• Release on Tuesday, November 12th

Projects

Project assignment goals:

• No single-discipline project teams
• Using RACI (responsible, accountable, consulted, informed) terminology
  • Every project has one Carbon team member who is accountable for the project's completion
  • Carbon team members only responsible for one project at a time
• Prevent project carry-over by getting projects to done done
• As a team, find a way to not neglect support responsibilities

Design system support (including component enhancements), Website support

• Accountable: @aagonzales
• Responsible: @jnm2377 , @asudoh
• Consulted: @alisonjoseph , @jeanservaas , @mattrosno , @shinytoyrobots (for support definition)
• Informed:

To do: better define support model/project.

Outcomes

• Continuous improvement (process, tooling) to best engage inbound community input
• Not let valuable feedback slip through the cracks

Scope

• Bug fixes in the codebase
• Issue triage and backlog grooming three-in-a-box (design, dev, OM)
• Self-serve documentation and FAQ (support audit findings)
• Component enhancement backlog - define scope

Ready for dev:

• Low contrast notifications: ([Notification] Low contrast style bugs #4282)
• File uploader bugs ([File uploader] Several bugs in style & behavior  #3587)
• 40px search field ([Search] add 40px search size #3457)
• Tooltip bugs: ([Copy button] Tooltip style wrong, icon wrong #3208)
• Copy button bugs ([Copy button] Tooltip style wrong, icon wrong #3208)
• Data table skeleton state (Update DataTableSkeleton component to v10 #3032)
• Inline loading style updates ([Inline loading] Update checkmark icon and loader size #3040)
• New tab variation ([Tabs] Add a secondary style #1329)
• React Pagination nav (feat:(Pagination): Stand alone Small pagination #2634)

Needs design work first:

• Modal (Modal discussion follow up #2922)
• Search functions: (Recommend adding Autosuggest, Autocomplete and Scoping to Search Functionality #3513, Search component is missing a CTA #3489)
• Progress bar (Progress Bar component #3025)
• Reusable floating menu (Separate the "Menu" part of the overflow menu into its own component #1903)
• Phone number field (Phone number field with country selector (new component request) #3948)
• Data table style bugs ([Data table] Multiple styling bugs #3210)

Theming (type tokens and size-related constraints) (cont.)

• Accountable: @joshblack
• Responsible: @laurenmrice , @emyarod
• Consulted: Jeff Chew, James Dow, Olivia Flory
• Informed: @jeanservaas , @mattrosno

Outcomes

• Enable expressive typography theming for all Carbon components in a future friendly way to assist Digital Design's use of Carbon

Scope

• Add support for all tokens in our themes (focus on type tokens, others like spacing could get deferred)
• Add constraints, or update styles, such that updating size-related tokens doesn’t break a component

Accessibility (cont.)

• Accountable: @dakahn
• Responsible: @aledavila , @abbeyhrt
• Consulted: @aagonzales , Sharon Snider
• Informed: Marc Johlic, Erick Renteria

Outcomes

• 100% component WCAG compliance (if not, documented deviations) to prevent adoption pushback and set adopters up for success
• Document a11y efforts, audits, justifications to demonstrate the large body of work that supports our components and build trust with IBM development teams
• Short term: currently at 32% component coverage towards WCAG compliance, get to 54%

Scope

• Tackle 12 components and bring them to WCAG compliance
  • Breadcrumb
  • Dropdown
  • Timepicker
  • FormItem
  • Loading
  • TextInput
  • TextArea
  • Tag
  • Slider
  • Select
  • OverflowMenu
  • Notifications

Patterns (cont.)

• Accountable: @designertyler
• Responsible: @janchild , @connor-leech
• Consulted: @chrisconnors-ibm , @joshblack , @dakahn
• Informed: Craig Moser, @mattrosno

Outcomes

• Facilitate alignment around and publish the priority patterns as production-quality design guidance.

Scope

• Patterns lifecycle and governance
• Production and anatomy guidelines Pattern production guidelines carbon-website#488
• Priority patterns consolidation work, based initially on Craig's list:
  • Navigation Global header pattern carbon-website#328
  • Forms Form pattern carbon-website#329
  • Notifications Notification pattern carbon-website#332
  • Guide [needs issue]
• Audit of existing main branch patterns against checklist (Markdown template) to determine work required for completion

Stretch goals:

• Audit of existing experimental patterns against checklist (Markdown template) to determine work required for completion
• Audit pattern and create a spreadsheet that tracks the components used in each pattern

Component documentation (cont.)

• Accountable: @jeanservaas
• Responsible: @jillianhowarth , @vpicone , @alisonjoseph (implement template for component page accessibility tab)
• Consulted: @dakahn (accessibility content) , @aagonzales (demo component)
• Informed: Sharon Snider, Marc Johlic, Erick Renteria (all accessibility content)

Outcomes

• Provide relevant developer documentation for our canonical implementation (React) so it's easy/simple to build high-quality web apps with Carbon
• Simplify the experience for designers to fully understand our components (what to use, when to use, how to use) via improved usage guidelines and examples

Scope

• Provide new accessibility tab on component pages, template for IBMa to populate, facilitate contribution
• Remove vanilla JS component documentation from website
  • Find new home for vanilla JS docs and provide way to find those docs when looking
• Implement demo component
  • Render React components
  • Interactive React source that can be copied/pasted
  • Variant/modifier consolidation
  • Theme switcher
• As a prototype deliverable, improve component page information architecture with supporting designs (e.g. floating anchor links)
• Identify gaps in design guidance

Icons (cont.)

• Accountable: @joshblack
• Responsible: @laurenmrice
• Consulted: @vpicone
• Informed:

Note: blocked by the completion of the theming project above.

Outcomes

• Process and workflow to maintain assets (icons, pictograms) isn't manual effort to reduce maintenance overhead of the team going forward

Scope

• Figure out what is left with pictograms and finish
• General polish/refactoring for internal tooling we rely on that would make it easy to build with icons on the site
• Investigate size issue for projects using TypeScript, could mean multiple entrypoints or figuring out ways to reduce generated icon build
• Define deprecation lifecycle
• Fix bundle and import file size issues (not being able to code split)

Theming (colors) (cont.)

• Accountable: @joshblack
• Responsible: @laurenmrice , @tw15egan
• Consulted: @aagonzales , @jeanservaas
• Informed: @mattrosno

Note: blocked by the completion of the icons project above.

Outcomes

• 100% of components theme-able (UI shell) so color token usage is done done
• Form a (documented) opinion on how to apply color to the page (zones? light variants?)

Scope

• Update components like UI shell to use theming tokens (or not)
• Figure out on design and dev side how we introduce zone concepts (or not)

[shinytoyrobots]

Once this is "set", can we also write it up as a wiki page at https://github.com/carbon-design-system/carbon/wiki (at least until we confirm the "single source of truth" destination).

[mattrosno]

@shinytoyrobots yes. I'm looking to have this ready for endgame team by end of day tomorrow (Tuesday) so they can proceed with the Medium article.

[stale]

We've marked this issue as stale because there hasn't been any activity for a couple of weeks. If there's no further activity on this issue in the next three days then we'll close it. You can keep the conversation going with just a short comment. Thanks for your contributions.

[stale]

As there's been no activity since this issue was marked as stale, we are auto-closing it.