Meeting - 12/18/2019

[iansu]

Agenda

• News/announcements
• Review previous action items
• Consider Microsoft Teams over Discord (@mrmckeb)
  • Threading
  • Free, has integrations to GitHub, etc.
  • We could ask Microsoft to upgrade us if we need more features.
  • I reached out to Slack (about a year ago), they weren't keen on open source.
• Merch (@mrmckeb)
  • Should we set up a store to sell merch?
  • This could help fund the project.
  • Also, I want stickers.
• Spectrum (@mrmckeb)
  • Is it working for us?
• Second meeting proposal (@mrmckeb):
  • 100% optional, every other week.
  • Focussed on present issues and PRs, peer discussion.
  • Should help us close things off faster.
• Templates:
  • Add devDependencies for custom templates facebook/create-react-app#8082
• V4:
  • Do we do an issue/PR cull during or near the end of v4?
  • What's in/out? This might need a longer separate meeting.

Attendees

• @iansu
• @mrmckeb
• @ianschmitz

Notes

• Microsoft Teams
  • Might be nice but will take effort to switch over
  • Discord is good for open source projects
• Swag store
  • If we can find something that works on demand this would be nice
  • Use money to fund project
  • Investigate options (@mrmckeb)
• Spectrum
  • Seems to be working okay
  • We need to spend more time on there
• Templates
  • Allow additional keys to be set in package.json
• v4
  • Set up a place to document the roadmap (@iansu)
• v3.3.1
  • IE/Edge websockets fixes
  • ESLint config not working properly (@mrmckeb)
  • TypeScript template fix
  • gitignore fix with templates

Previous Action Items

• Make PR for TypeScript peer dependency (@iansu)
• Make PR to disable no-unexpected-multiline rule (@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

• 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)

Details

December 18, 2019 10:00am Pacific
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Create+React+App+maintainers+meeting&iso=20191218T18&p1=1440

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