Skip to content

Latest commit

 

History

History
40 lines (34 loc) · 2.95 KB

2019-04-01.md

File metadata and controls

40 lines (34 loc) · 2.95 KB
Raw

Outreach Working Group

April 1, 2019

Attendees

Members

  • Charles
  • Felix
  • Tony
  • Sam
  • Sofia

Visitors

Agenda

  • Onboarding project check-in
    • electron/electron#17456
    • run through of electron build for macOS (sofia), windows (JD), and linux (david)
    • Mentorship
    • suggestion: Slack onboarding doc includes who to reach out to, which channels to join, and what to do when you're bored

Action Items

  • "Get Involved" link on top level README.md in https://github.com/electron/governance (@tonyganch)

  • in the top level README.md in https://github.com/electron/intern-guide add list of channels to use as resources, e.g. #ask-anything (@sofianguy)

  • Suggested changes for build instructions (@ckerr)

    • Tell users how much free disk space they'll need
      • debug takes about 30gb
      • chromium download takes about 12gb
    • At top of "pull request doc" maybe say this doc is for writing new PRs; if you just want to build Electron from scratch, see building-from-gn doc
    • Explain at the beginning of "Cached builds (optional step)" why someone would want to include this step
    • In "Getting the Code" step, document a step of ensuring gclient is in path -- we can probably write in more detail about setting up gclient (depot_tools) under our GN prerequisites section of the doc on setting up the $PATH correctly
    • "To build, run ninja with the electron target: Nota Bene: This will also take a while and probably heat up your lap." suggest saying how long it might take on some example hardware to give a frame of reference
    • In "Building" maybe explain the difference between Debug and Release builds
    • suggestion: we could add explanation excerpts of what things like the gclient step is supposed to be doing – downloading chromium
    • suggestion: edit note that it will take a long time to build electron; longer than the downloading step – go eat dinner
    • screenshot during the downloading chromium step so that you know what it should look like when you’ve successfully started downloading. especially because we note that it will take a while; the user should know when to “go grab a coffee”
    • suggestion: we could do a screen shot of what it looks like when you’ve successfully started building, e.g., “[685/17661] CXX obj/components/keyed_service/core/core/simple_dependency_manager.o” from iterm