Page MenuHomePhabricator

[EPIC] Design Systems Team Communication Improvements Q1 2022-23
Closed, DuplicatePublic

Description

Current state 2022-10-27
  • Merged as duplicate into T313905 & removed still-relevant subtasks for future prioritization.
Background/Goal

Ongoing requests and collaborations with other teams have surfaced several unfulfilled needs related to communication, transparency, expectations, and strategic alignment of Design Systems Team (DST) priorities and collaboration norms:

  • Release communications, especially with regard to "breaking changes"
  • Value proposition of using Codex & working with the Design Systems team
  • What partner teams can expect from the Design Systems team in terms of collaboration & engagement
  • Roadmap clarity on Codex component development & what it means for OOUI, WVUI, and WiKit.
User stories
    • As a contributor, given that I am on a WMF team that has implemented Codex, I want to access and understand information about upcoming Codex releases/updates so that I can better plan for breaking changes and where to go for support.
  • As a contributor, given that I have heard of Codex, I want to understand why I should use it as my component library for front-end development (i.e., what's in it for me?), what risks might be involved, and how to partner with the Design Systems team on implementing Codex.
  • As a Design Systems team member, given that another team at WMF wants to collaborate with me on implementing Codex, I want to provide clearer expectations on the different levels of support we can provide, and what decision-making looks like.
  • As a contributor or WMF stakeholder, I want to access and understand 1) what Codex components are in progress, and 2) what Codex components will be developed next, so that I can make more informed UI/front-end decisions about my projects.
Considerations
  • This epic is time-boxed to one quarter, July - September 2022. Our efforts should be scoped to fit within that timeframe (knowing that we will continue to iterate).
Acceptance criteria / Deliverables
  • Partner-team-facing value proposition T312170
  • Engagement/support models are defined for Codex development T309307
  • Codex release communication framework / template T312167
  • Roadmap updates T312172
  • Document FAQ T312648
Questions & Answers

[log Q&A for the epic level]

Details

Due Date
Sep 30 2022, 4:00 AM

Event Timeline

ldelench_wmf renamed this task from [EPIC] DST Process Improvements Q1 22-23 to [EPIC] DST Communication Improvements Q1 22-23 .Jul 5 2022, 8:03 PM
ldelench_wmf updated the task description. (Show Details)
ldelench_wmf moved this task from Inbox to Quarterly Plan on the Design-System-Team board.
ldelench_wmf renamed this task from [EPIC] DST Communication Improvements Q1 22-23 to [EPIC] Design Systems Team Communication Improvements Q1 2022-23 .Jul 7 2022, 9:03 PM
ldelench_wmf updated the task description. (Show Details)
ldelench_wmf set Due Date to Sep 30 2022, 4:00 AM.

I've added T75714 as a sub-task here. There are definitely folks in the gadget and user-script developer community who are interested in using modern JS (ES6), Vue, and Codex in their projects.

DST should help enable this and include these developers in the guidelines/communications that go out about who can use what where.

ldelench_wmf changed the task status from Open to In Progress.Aug 12 2022, 4:24 PM