Electron - A Community Story
summary
A concrete origin story: Electron starts as atom-shell after forking node-webkit, wins a first major user — Light Table — and then gains traction through rapid releases and hands-on community work. Community channels use GitHub issues and a mailing list early then migrate to Slack; maintainers insist on fast issue triage, timely PR reviews, contributor permissions, a bootstrap script and documentation. Big corporate users (Facebook, Microsoft, Slack) arrive, contributions scale, and a formal team replaces the solo maintainer.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:42introduction
- 1:02a brief history of Electron
- 2:28early days of node-webkit
- 3:35set a target
- 5:15built a simple community
- 5:47promotion
- 8:48kept early users
- 9:47what to do next usually
- 11:39first year of Electron
- 12:34open sourced after one year
- 13:56community channels
- 14:58answer every issue
- 16:44respect pull requests
- 18:48make contribution easy
- 20:33company users are good
- 21:43they can be bad
- 23:47grew to a team
related talks
25mBuilding Up the Electron Project: Team and Community Engineering
23mKeynote: Welcome New Projects
34mReal world Electron: Building Cross-platform desktop apps with JavaScript
36mUsing Electron in the Development of a Corporate Message-Video-Phone Platform
07mJacob Groundwater, Github | Node Summit 2017
48mGetting Started with Electron
22mBuilding Desktop Applications with Node and Electron
40mPanel Discussion: Build a Community, Not a Framework