Mar 14, 2023 Sprint Planning Notes:

• Recommend keeping in next sprint so we can keep an eye on this

Rolling to next sprint.
Next step: Team review complete by Friday, March 17, 2023.

Touchbase with Legal

• Re-affirming trigger date of mid-April
• will aim to complete footer changes on or soon after the target go-live data

Some Progress We've Made Related To this Work:

• We've recently been able to develop and deploy a liftwing api to the API gateway (which was a blocker to migration)
• We can now work on migrating the model to Liftwing so we can work on it there. Based on internal discussions with the ML/AI team, we believe this should be a relatively small effort. (Working on scheduling)
• We'd then have to work with Research and the ML/AI on improvements to the model

From a product perspective, ok with advancing with the extension solution.

November 28, 2022 Team Discussion
Discussed defining some experiments that help us answer things like:

• How does this integrate with the design system?
• How could this impact with the architecture of the design system?
• How does this integrate with mediawiki?
• How far in scope does this need to be?
• What is the cost to build? What is the cost of maintenance?

Signing off

Adding a few teams for the list:
Potential pilot teams:

• Growth
• Language

In disucssion as a team, there are different tiers of team engagements, they include:

• Tier 1: provide information
• Tier 2: encourage adoption
• Tier 3: support contribution

Proposed roadshow deck for team sign-off is here: https://docs.google.com/presentation/d/1wez_RoSeu8b2nzfqL0psxVUd4LU5M9K0M9N2fyZEsqk/edit

2022-10-27 Office Hours
Roadshow strategy & timeline

• DST is presenting at Product dept meeting November 16
• This will be similar to deep dive we did with Selena: what is DS, brief demos, FAQs

Design System FAQs for Roadshow

• VE: concern about Codex being the Design System - need to involve principal designers, Product Design
• Offsite that week as well -DECISION: remove for now
• EG: do we need help fleshing out answers? I can take a crack at the vue.js answers in beginning re: front-end architecture convos
  • DA: we should add as a sprint activity and divide/conquer

Open questions we need to solve with everyone

• These are things we need collaboration with Product, Engineering, Design:

Apps

• • • Legacy toolkits like WVUI, OOUI
    • Once we update this FAQ, update our mediawiki page with FAQ & roadmap
  • LD create tasks:
    • Figma demo video
    • Codex demo video
    • Update wiki page
    • Survey
• Leading presentation at Product dept meeting - hoping we can split up demos like we did at deep dive, Desiree will let us know how much time we have to present
• Survey at end?
  • What are your open questions
  • Concerns?
  • Have you been to demo site?

October 26, 2022 Tech SC Meeting Notes

• From Growth team: "The high level summary is: we want to provide suggestions to users about "copy edit" fixes they can make to articles. The suggestions will come from a LanguageTool application instance, and those suggestions will be further filtered by a Python application that is responsible for proxying requests to/from LanguageTool (some updates / more reading here https://phabricator.wikimedia.org/T315086). Given that architecture, we would have two services (LanguageTool, and Copyedit) in Wikimedia's Kubernetes cluster."
• After initial review with the Technology steering committee this does not include an ML/AI model and falls more closely in line with what has been implemented for SD image suggestions
• Given that LanguageTool and Copyedit would be developed similarly to image suggestions

2022_10_26 Updates from Conversation with Legal

• Legal is aiming to do a Terms of Use update in Q3 or Q4
  • We will start a community consultation from Feb-April to discuss ToU changes, etc.
  • Once consultation is completed, governance wiki will be updated and changes to licensing may be made
• The CC 4.0 License changes would include:
  • change references and deep links to point to CC 4.0 https://creativecommons.org/licenses/by-sa/4.0/
    • Internationalization - need each language wiki to point to https://creativecommons.org/licenses/by-sa/4.0/ in the correct language
  • For overrides, Legal will engage with the community

thanks! product signing off

product signing off

product sign-off

product signing off

product signing off

product signing off

product signing off

product signing off

looks good. product signing off

product signing off

acceptance criteria met. Signing off

Product sign-off

This is part of a series of tickets related to handling breaking changes. Do we have an epic for this? Maybe add this as a child of make it easier to use codex ticket.

After reaching out to @Catrope, provided a lot of context and clarity on what is needed. Adding discussion summary and potential next steps from discussion below:

create an upcoming needs tracker/forum to capture.

product sign off

Suggested Content & Supporting Documents:

• Overview of Design System Objectives
  • Supporting doc: take from deep-dive deck
• Our Core Offering (aka Key terms in Design System)
  • Supporting doc: take from deep-dive deck
• What We've Accomplished So Far
  • Recorded/Live Component Demo
  • Recorded/Live Visual Style Demo
• What's Next
  • Supporting Doc: Roadmap
• How to Engage
  • Who, When, & How to contact
  • Share links to contribution and adoption docs

Assigning to Volker as per Sept. 6 2022 refinement meeting

Creating visual styles in different places:

• Figma - design implementation
• Codex - only includes tokens

September 1, 2022 Review Session:

• Engineering enclave take-away - okay with concept of distributing less mix-ins
  • compiles down to CSS but is it's own language
  • can compose style rules, decoupling the idea of a link or button from where the design is going to go (aka markups, css, etc.)
• Up to other people how they will apply to what they are building
• this solution can be very incremental
  • only do this for a small subset of global visual styles
• Codex is a bunch of pre-built components, but if you have other things that are floating or not part of an existing component they can grab reusable styles
• designers would not have to do any extra work, this is purely at the engineering level.
• Part of reason why we raised concern around links, is that tempting way to deal with this is to apply universal standards, because we use elements in different ways and would limit flexibility
• operate at a global page level

Currently defining core components in sub-tasks

We will address documentation as part of the documentation task: https://phabricator.wikimedia.org/T313917. This is the first step in that process. Next step is the refinement of core components in: https://phabricator.wikimedia.org/T313357.

Product sign-off complete

Product sign-off complete

Product sign-off complete

Signing-Off and closing out as this is now complete. We've reviewed and prioritized relevant tickets.

Product sign-off complete

Product sign-off complete

Marking this to review for integration into roadmap

Product sign-off complete

Product sign-off complete.

Product sign-off complete.

Product sign-off complete

Product sign-off complete

Product sign-off complete. Kicking off sessions within next 2 weeks

Product sign-off complete

Product sign-off complete

Great work all. We will continue to make improvements to documentation as we iterate on the Design System.

MVP scope has been finalized and we can close this ticket. Product sign-off complete