Skip to content
This repository was archived by the owner on Aug 12, 2022. It is now read-only.
This repository was archived by the owner on Aug 12, 2022. It is now read-only.

Meeting - 6/10/2020 #35

Closed
Closed
@iansu

Description

@iansu

Agenda

Attendees

Notes

  • v4
    • ESLint 7 upgrade
      • Waiting on jsx-ast-utils
    • workbox plugin update
      • Look at config changes suggested
    • Consider doing a beta release if ESLint 7 issues take too long
    • Merge Web Vitals PR
    • Fast Refresh
      • Update the plugin again to 0.4.0
      • Consider disabling our error overlay because the Fast Refresh plugin ships its own
      • Enable by default? Maybe ask Dan.
      • Warn about using React >= 16.10
    • Use new ReactDOM root?
  • Moved from Spectrum to Discussions
    • Lack of notifications for Discussions is a problem
      • Ask GitHub about this (@iansu)
  • Tests
    • Start slowly moving things over to GitHub Actions
      • Set up a new test suite that runs on GitHub Actions (@mrmckeb)
      • Move tests to the new suite over time
    • Use templates more in tests

Previous Action Items

  • Post in Spectrum about moving to GitHub Discussions (@iansu)
  • Update question template to point to GitHub Discussions (@iansu)
  • Create new CLI (@iansu)
  • Review swag production options
  • Try using GitHub Actions for CI (@iansu)
  • Follow up with Google about WebWorker PR (@iansu)
  • Talk to Facebook Open Source about T-shirts and swag (@iansu)
  • Remove Jack from accounts (@iansu)
  • Make sure the team has access to Azure DevOps (@iansu)
  • Give people access to Open Collective (@iansu)
  • Set up Open Collective (@iansu)
  • Add maintainer info to README (@iansu)
  • Find out what other projects are using react-dev-utils/openBrowser (@iansu)
  • Fix and force-push master (@iansu)
  • Don't swallow stack traces on warnings (@gaearon)
  • Investigate how other similar projects handle testing (@ianschmitz)
  • Lock down force pushing to master (@gaearon)
  • Look into enabling canary releases (@ianschmitz)
  • Come up with a list of potential Open Collective donors (@iansu)
  • Talk to Dan about getting access to the eject survey (@iansu)
  • Document triaging process (@iansu)
  • Document PR process (@iansu)
  • Create maintainer onboarding document (@iansu)

Action Items

  • Ask about notifications for GitHub Discussions (@iansu)
  • Build a new test suite that runs on GitHub Actions (@mrmckeb)
  • Create new CLI (@iansu)
  • Review swag production options
  • Try using GitHub Actions for CI (@iansu)
  • Follow up with Google about WebWorker PR (@iansu)
  • Talk to Facebook Open Source about T-shirts and swag (@iansu)
  • Remove Jack from accounts (@iansu)
  • Make sure the team has access to Azure DevOps (@iansu)
  • Give people access to Open Collective (@iansu)
  • Set up Open Collective (@iansu)
  • Add maintainer info to README (@iansu)
  • Find out what other projects are using react-dev-utils/openBrowser (@iansu)
  • Fix and force-push master (@iansu)
  • Don't swallow stack traces on warnings (@gaearon)
  • Investigate how other similar projects handle testing (@ianschmitz)
  • Lock down force pushing to master (@gaearon)
  • Look into enabling canary releases (@ianschmitz)
  • Come up with a list of potential Open Collective donors (@iansu)
  • Talk to Dan about getting access to the eject survey (@iansu)
  • Document triaging process (@iansu)
  • Document PR process (@iansu)
  • Create maintainer onboarding document (@iansu)

Details

June 10, 2020 10:00am Pacific
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Create+React+App+maintainers+meeting&iso=20200610T17&p1=1440

Zoom: https://zoom.us/j/163553316

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions