Meeting - 5/1/2019

[iansu]

Agenda

• News/announcements
  • v3: we did it! Good work everyone! 🎉
• Review previous action items
• Customization of ESLint config? New Typescript linting overriding user config and causing build failure facebook/create-react-app#6871 (@ianschmitz)
• Feedback from Akryum of Vue CLI core team regarding templates - https://gist.github.com/ianschmitz/be22317e5c6f4c8784d644021a59db6d (@ianschmitz)
• v3.1
  • Templates update
  • SSR?
  • Monorepo support?
    • Are there any non-breaking changes we can make to improve life for people using monorepos?
  • Console clearing
    • I think Jack looked into this a bit? (@bugzpodder)
  • Anything else important?
  • Let's start putting everything we can think of in the 3.1 project
• Force pushing master
  • I've been having a hard time trying to fix this (@iansu)
• Project
  • Need to resume working on Open Collective

Attendees

• @iansu
• @mrmckeb
• @ianschmitz

Notes

• v3.1
  • Add issues to project and milestone
  • SSR
    • We have historically resisted this
    • Official stance has been "use Next.js"
    • Maybe this can be a template?
    • Need to include something like React Router to make this work
      • Starts to make us more of a framework
  • Improve bundle size and size warnings to account for multiple entrypoints
  • Monorepo support
    • We get many more issues related to this than SSR or other things
    • What little things can we do to improve monorepo support?
  • Console clearing
    • Maybe we can just document using concurrently or similar to run multiple processes without clearing the console
    • Find a way to not wipe out the screen buffer and restore it after quitting the app
  • ESLint config
    • Do we want to make this configurable in some way?
    • Allow them to extend our config?
    • Investigate how we can control TypeScript overrides
    • Maybe just let them disable TypeScript rules?
• What do we want Create React App to be?
  • Primary and secondary audiences
    • Primary: people learning React and in some cases programming/web development
    • Secondary: experienced devs doing quick experiments, prototyping, etc.
  • Should people be running Create React App in production?
  • Nothing in the React world like Vue CLI or Angular CLI
    • Should Create React App be the React version of that?
    • We would need a lot more support from Facebook/Dan to do something like that
      • Do they even want that? It doesn't seem like it.
      • Do we even want that?
  • Talk to the maintainers and see what they think about the direction of the project
  • We should be more clear with the community about what the goal(s) of this project are
• CI
  • Azure is mostly ready to go
    • Make a PR back to Create React App
    • Set up Azure DevOps account
• Project
  • Open Collective
    • Talk to FB Open Source to make this happen
  • Add list of maintainers to README (so people know we don't work at Facebook)
  • Logo
    • Pick this up again the next couple of weeks

Previous Action Items

• Relax ESLint version check (@ianschmitz)
• Fix and force-push master (@iansu)
• Don't swallow stack traces on warnings (@gaearon)
• Investigate how other similar projects handle testing (@ianschmitz)
• Upgrade to Docusaurus v2 (@amyrlam)
• Lock down force pushing to master (@gaearon)
• Bring in changes Microsoft made to our test suite (@ianschmitz)
• Look into enabling canary releases (@ianschmitz)
• Come up with a list of potential Open Collective donors (@iansu)
• Investigate console clearing differences with npm-run-all and concurrently (@bugzpodder)
• Get workbox config PR updated (@iansu)
• Talk to Dan about getting access to the eject survey (@iansu)
• Come up with new ideas for logo design
• Document triaging process (@iansu)
• Document PR process (@iansu)
• Create maintainer onboarding document (@iansu)
• Look into new GitHub issue templates (@iansu)
• Update deploy instructions (@iansu)

Action Items

• Investigate ESLint customization (@mrmckeb)
• Make a PR to switch us to Azure DevOps (@ianschmitz)
• Set up an Azure DevOps account (@ianschmitz)
• Talk to Facebook Open Source about creating an Open Collective (@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)
• Come up with new ideas for logo design
• Document triaging process (@iansu)
• Document PR process (@iansu)
• Create maintainer onboarding document (@iansu)
• Look into new GitHub issue templates (@iansu)
• Update deploy instructions (@iansu)

Details

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

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