Meeting Notes 2022-07-21

[kelset]

Agenda

• status update Meta side
• status update MSFT side
  • Typescript & Codegen
  • debugging
  • CI & E2E
• next steps: expanding invited folks to have all significant experts, setting goals per each area

Notes

status update Meta side

• main focus is going to be towards new architecture adoption
  • focus on key libraries for the community
  • new documentation coming up
  • focus on build times improvements (both iOS and Android)
• opportunities for "industry-alignment" focus
  • work on the RFC: RFC: React Native as a monorepo discussions-and-proposals#480
    • maybe have a workshop around this at the contributors summit (the one from Callstack)?
  • E2E testing in react-native's OSS repo
    • can be done externally from Meta, should be as close to what is used internally so that it's easy for folks to contribute
• (from Blake) my area of focus is build and tooling
  • we want to reach dev tooling parity between react and RN (ex. transition tracing)
  • metro symlinks

status update MSFT side

• we have folks working across the different streams
  • types & codegen: Zihan has the goal to improve react-native-codegen and make it fully support all types (not just basic ones)
    • Luna will be the contact person from the Meta side
  • debugging: we have Andreas from MSFT, plus a few folks from Sony and Amazon expressed interest
    • main issue there currently is defining northstar and tasks
  • CI & E2E: Lorenzo will focus on this area while he's currently in the release crew
    • we might want to look more closely into Windows on CI
  • Metro: Adam is working on haste and potentially removing it, and it will relate to the symlink work from the Meta team

Next steps

• how do we want to work across the board?
  • we'll keep this sync in a fixed schedule
    • every 2 weeks
  • each workstream will self-manage, probably at least some one-off kickoff meetings of sort
  • we want some document of sort to track the tasks and progress

[afoxman]

Meta also expressed a desire to ease the upstream process and lessen the turn-around time. Some of the solutions for this are tied to the RFC on monorepo. Other areas discussed are CI/CD processes on GitHub to avoid multiple roundtrips from GitHub through Meta's internal systems and back. This usually happens over trivial stuff like styling and formatting.