Meeting - 1/8/2020

[iansu]

Agenda

• News/announcements
• Review previous action items
• 4.0:
  • Bundler (@mrmckeb):
    • Is Webpack 5 a contender? At beta 11.
    • Do we want to also empower library creation?
  • A project board for ideas/discussion (@mrmckeb)
    • Maybe "plugins" to get around config questions?
      • "You can build (and support) a plugin to do that"
• Potentials for merchandise stores (@mrmckeb).
  • https://www.spreadshirt.com/, https://cottonbureau.com/, https://www.redbubble.com/
  • https://webpack.threadless.com/ - this is interesting
  • DIY - Gatsby does this, a lot of work. But offers flexibility.
  • Shopify - https://www.shopify.com/blog/start-online-tshirt-business
    • Use with https://www.printful.com/ or https://www.gooten.com/
  • Use on-demand printers (above) with DIY.
• Issues:
  • 3.3.1: https://github.com/facebook/create-react-app/milestone/74
  • Use native ESLint behaviour when extending facebook/create-react-app#8276 - 3.3.1 or 3.4?

Attendees

• @iansu
• @mrmckeb
• @ndelangen

Notes

• Look over merchandise options
• 3.3.1
  • A few minor fixes
  • Add ESLint fix
  • Maybe release next week
• v4
  • webpack 5?
  • Plugins
    • Still scary allowing webpack customization
    • Ties us to webpack forever
  • Libraries
    • Not sure if it should be in the main project or another?
• cra.link
  • Maybe getting set up soon?

Previous Action Items

• Investigate on-demand swag production options (@mrmckeb)
• Set up a place to discuss v4 roadmap (@iansu)
• 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

• Review swag production options
• Set up a place to discuss v4 roadmap (@iansu)
• 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

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

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