---
# System prepended metadata

title: 'January Project Cycle: (Jan 4 - Jan 29)'
tags: [status]

---

---
robots: nofollow, noindex
tags: status
---

# January Project Cycle: (Jan 4 - Jan 29)

## Quick links

- [GitHub Milestone](https://github.com/microsoft/fluentui/milestone/20)
- [Create a New Proposal](https://github.com/microsoft/fluentui/issues/new?body=%23%20Project%20Proposal%0A%0A%23%23%20Problem%0A%23%23%20Appetite%0A%23%23%20Solution%0A%23%23%20Risks%20%28Rabbit%20holes%29%0A%23%23%20Out%20of%20scope%20%28No-gos%29&labels=Type:%20Feature)

## Projects for Jan
### [January Project Cycle 2021 Milestone (github.com)](https://github.com/microsoft/fluentui/milestone/20)

- [Continued styling convergence](https://github.com/microsoft/fluentui/issues/16372) 
- [Menu Convergence](https://github.com/microsoft/fluentui/issues/16371)
- [Separator Convergence](https://github.com/microsoft/fluentui/issues/15759)
- [Avatar convergence](https://github.com/microsoft/fluentui/issues/16373)
- [Link convergence](https://github.com/microsoft/fluentui/issues/16572)
- [Produce set of new Fluent UI icons (svg)](https://github.com/microsoft/fluentui/issues/15758)
- [Memory consumption measurement](https://github.com/microsoft/fluentui/issues/16098)
- [Finish up Version 8 release tasks](https://github.com/microsoft/fluentui/issues/16357)
- [Version 8 partner upgrade and rollout plan](https://github.com/microsoft/fluentui/issues/16358)
- [Fluent UI Ecosystem](https://github.com/microsoft/fluentui/issues/16445)
- [TS 4.0](https://github.com/microsoft/fluentui/issues/16101)

## Project updates

### [Continued styling convergence](https://github.com/microsoft/fluentui/issues/16372) - Miro, Shift, Mak, Xu
#### Week 4 - 1/26
#### Achievements
- Another round of perf tests showing `makeStyles` is slightly slower than `margeStyles` v7
    - But `mergeStyles` is reportedly fast in those scenarios
    - Can we find a scenario where `mergeStyles` does not perform well?
- We are not fully confident, but we don't see any major blocker and need to move on - **GO**
  - If we would find out we need to change the implementation, we will do breaking changes to fix it
	- Styling is important for converged components but those are much more than the styling
- First version of `makeStyles` spec - ready for review
- Helped with `Button` High Contrast issues in Ribbon (Mak) - [PR merged](https://office.visualstudio.com/OC/_git/office-online-ui/pullrequest/676090)

#### Objectives
- Finalize the pattern so that components can use it
- Continue investigating and fixing perf, but do not block components

#### Learnings
- Atomic CSS makes layouting more expensive!



#### Week 3 - 1/19
#### Achievements
- Office Ribbon perf test (Xu) - slow with runtime styles, on par with `mergeStyles` (=good enough) when build-time styles are used
- `react-button` to use `makeStyles` (Mak) - WIP also adding React layer for `makeStyles`
    - perf concerns re composed components (`MenuButton`, `SplitButton`) - update: no concerns - similar to mergeStyles
- updated `react-button` styles in Teams theme (Mak) - now it matches designs
- babel plugin for build time styles evaluation (Shift) - first PoC version ready (passes basic UTs)

#### Objectives
- Test in N*
- Continue with `makeStyles` in `react-button` adoption
- Continue with build time babel plugin

#### Learnings
- Build time (babel) work is mandatory

#### Week 2 - 1/12
#### Achievements
- Identified next steps (In github issue)
- Based on results so far, this is performant enough, will continue to measure and improve as we continue
#### Objectives
- Find differences in react-button and N* button and rename props
- Main goal: makeStyles production ready
    - Test in office
    - Test in N* doc site
    - End of month
#### Learnings
- Cooperation is cool
- Good on API, pattern, and direction
- Build time trasnform may be harder than it looks

### [Menu Convergence](https://github.com/microsoft/fluentui/issues/16371) - Ling

#### Week 4 - 1/26

#### Achievements

* Got feedback on spec and iterated
* Finished a deep dive with a nice set of conclusions
* PR for spec is out of draft and working to get into master
    * Hopefully end of week !

#### Objectives
* Get the spec in
    * does not mean it will be forgotten
    * Still feedback pending
* Start looking into setting up a converged project for menu

#### Learnings
* Protyping spec ideas is good
* Hard to define level of detail in a spec
* A spec needs to be updated

#### Week 3 - 1/19
#### Achievements
- Spec out for review (one concern around popup and positioning)
- Spec is ready for menu itself
- Open UI Pr research out (need to join the org)
#### Objectives
- Working through accessibility learning from past issues
- Finish Menu spec
#### Learnings
- Might need to reorder the spec template


#### Week 2 - 1/12 - 
#### Achievements
- Just got started today
- Project proposal
#### Objectives
- Do open ui investigation
- Update existing menu spec
- Goal: Get review and sign off on menu spec
#### Learnings

### [Separator Convergence](https://github.com/microsoft/fluentui/issues/15759) - Josche
#### Week 3 - 1/19
#### Achievements
- Updates to package creation utilities
    - PR's out
#### Objectives
- Working on convergence starting now
#### Learnings

#### Week 2 - 1/12 - 
#### Achievements
#### Objectives
#### Learnings

### [Avatar convergence](https://github.com/microsoft/fluentui/issues/16373) - Ben

#### Week 4 - 1/26
#### Achievements
* Avatar spec is in review: https://github.com/microsoft/fluentui/pull/16524
  * Thanks for the comments and discussion so far! We'll discuss the spec in tomorrow's spec open hours.
* Working on implementing updates based on spec feedback.

#### Objectives
* Follow up on open questions from the spec review.
* Hope to get the Avatar spec merged this week, pending any remaining feedback/discussion.
* Update the Avatar implementation based on feedback.
* Add support for Avatar colors.


#### Week 3 - 1/19
#### Achievements
* Avatar Spec is out for review
  * https://github.com/microsoft/fluentui/pull/16524
* OpenUI Research for Avatar is out for review
  * https://github.com/WICG/open-ui/pull/250
* Avatar Screener tests are implemented and in PR
  * https://github.com/microsoft/fluentui/pull/16525

#### Objectives
* Have spec reviewed and make updates accordingly
* Do reviews of Menu and other specs
* Attend OpenUI meeting and have Avatar research approved and merged 
* Implement support for Avatar colors per design

#### Learnings
* Coding > Spec writing (but both are important, of course)

#### Week 2 - 1/12 - 
#### Achievements
- Spec almost done, PR out soon
#### Objectives
- Open UI research in progress
- VR Tests 
- Spec reviewed this week
- Goal: Phase 1 and Phase 2 of Avatar complete
#### Learnings

### [Link convergence](https://github.com/microsoft/fluentui/issues/16572) - Mak
#### Week 4 - 1/26
#### Achievements
* Link spec is out for review
    * https://github.com/microsoft/fluentui/pull/16621
* OpenUI Research for Link is out for review
    * https://github.com/WICG/open-ui/pull/253

#### Objectives
* Have spec reviewed and make updates accordingly
* Try to get Link OpenUI research looked at and merged
* Start converged implementation
* Move old non-converged implementations back into `@fluentui/react-internal`

### [Produce set of new Fluent UI icons (svg)](https://github.com/microsoft/fluentui/issues/15758) - Tomi
#### Week 4 - 1/19
#### Achievements
- New icon package released on Wednesday Jan 27
- IconProvider PR in review
    - https://github.com/microsoft/fluentui/pull/16519
- Icon documentation PR in review(both v7 and master)
    - https://github.com/microsoft/fluentui/pull/16580
    - https://github.com/microsoft/fluentui/pull/16593
#### Objectives
- Finish setting up usage examples

#### Week 3 - 1/19
#### Achievements
- Circular dependency in icon overrides with themeprovider
    - Create IconProvider package 
#### Objectives
- Finish IconProvider PR
- Finish Icon Documentation PR
    - Add a list of SVG icons to the public docsite
    - Add info on how to override using `IconProvider` element, or leveraging `registerIcons` to incorporate new SVG icons into application
#### Learnings
- Some issues with iconprops and integrating into existing components

#### Week 2 - 1/12 - 
#### Achievements
- PR out for finalizing Icon overrides using Theme Provider
- PR out for icon documentation
- New Fluent UI icons released
#### Objectives
- Spin up CodePens that show general usage of icons and how to override
- Start on incoporate new SVG icon packages in our V8 components
  - open question what about IconProps?
#### Learnings

### [Memory consumption measurement](https://github.com/microsoft/fluentui/issues/16098) - Xu
#### Week 4 - 1/26
#### Achievements
- Started investigating using chrome developer protocol and pupeteer to retrieve more metrics (e.g. private memory, web cache)
#### Objectives
- Be able to retrieve the additional metrics programtically.
#### Learnings
- This work will continue in next cycle.

#### Week 3 - 1/19
#### Achievements
- No Updates this week
#### Objectives
#### Learnings

#### Week 2 - 1/12 - 
#### Achievements
- Done with manual measurements, shared with Teams
#### Objectives
- Next steps add automations, expand existing tests 
#### Learnings

### [Finish up Version 8 release tasks](https://github.com/microsoft/fluentui/issues/16357) - Elizabeth
#### Week 3 - 1/19
#### Achievements
- No Updates
#### Objectives
- Establish Target Date for Version 8 release
#### Learnings

#### Week 2 - 1/12 - 
#### Achievements
- Catching up on Shield currently
#### Objectives
- Start discussions this week
#### Learnings

### [Version 8 partner upgrade and rollout plan](https://github.com/microsoft/fluentui/issues/16358) - Jon
#### Week 4 - 1/25
#### Achievements
- I Began upgrading odsp-common.
- Setup a local OneJS repo so that I can begin testing the changes there.
#### Objectives
#### Learnings
- Most common problem with upgrading is not changing the code, it's the cost of validating the change across so many components
#### Week 3 - 1/19
#### Achievements
- Reached out to partners
- Connected with OWA and FAST
#### Objectives
#### Learnings
- Learnings each group is very different state
- As we know, biggest problem is having different version of fluent on the page at a different time

#### Week 2 - 1/12 - 
#### Achievements
- Plan identified
#### Objectives
- Reaching out to partners with survey on upgrade
- Jan Goal: concrete plan on what partners should do to begin the upgrade process. Who goes first?
#### Learnings
- Scoping with this problem was really helpful (nebulous problem)

### [Fluent UI Ecosystem](https://github.com/microsoft/fluentui/issues/16445) - JD/Jon
#### Week 4- 1/25
#### Achievements
- Sync with several stakeholders, identify several possible routes forward
    - Design
    - Levi (for Storybook and inner dev loop)
#### Objectives
- Clarified objective - help make first party documentation experience excellent.
#### Learnings
- Design looking for help with fluent website effort, though not 100% clear it's inline with our goal to establish a fluentui ecosystem.
#### Week 3 - 1/19
#### Achievements
- Meeting with Design team on Website - Next monday
- Goal: Feature full fluent ui experience on website
#### Objectives
#### Learnings

### [TS 4.0](https://github.com/microsoft/fluentui/issues/16101) - Jon/Elizabeth
#### Week 4- 1/25
- No updates

#### Week 3 - 1/19
#### Achievements
- Elizabeth made some progress here
- Got API Extractor to release a new version with latest typescript
#### Objectives
- Finish writeup yarn resolution and nohoist settings work
#### Learnings
- Having more than one version of a package in a repo causes a lot of headaches

#### Week 2 - 1/12 - 
#### Achievements
- Good opportunity for ramp up?
- Might be too big
- Martin, Andre, Jakub, Elizabeth, Levi
- Open question: does Web components ugprade at same time
#### Objectives
#### Learnings


### Fluent UI Ecosystem
#### Week 2 - 1/12 - 
#### Achievements
- Design team has ideas on Ecosystem topic
- Primary website design, connect into the development of the website
- Open questions about resourcing and technical details
- Open Issue: What about branding of Fluent UI?
#### Objectives
- Follow up with Design on next steps
#### Learnings

## More links

[Shared OneNote for eng process][onenote]

[Accessibility Issues](https://dev.azure.com/microsoftdesign/fluent-ui/_queries/query/ab37cec7-fd8f-4828-99ac-d56e65396ada/)

[backlog]:  https://dev.azure.com/microsoftdesign/fluent-ui/_backlogs/backlog/fluent-ui%20Team/Epics
[issues]: https://github.com/OfficeDev/office-ui-fabric-react/issues
[onenote]: https://microsoft.sharepoint-df.com/:o:/t/FluentUIInternal/Ev_x5WbQI6tJmn2s87RzRPMBTG3d0gmYJN6QCpQttOFyzw?e=rnbj9H
[sprint53]:  https://dev.azure.com/microsoftdesign/fluent-ui/_sprints/backlog/fluent-ui%20Team/fluent-ui/Sprint%2053
[onelibrary]:  https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/4469
[theming]:  https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/4464
[performance]:  https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/4462
[composition]:  https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/4465
[onerepo]:  https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/4468
[onelib]: https://dev.azure.com/microsoftdesign/fluent-ui/_workitems/edit/4469

