Oversees the projects that make Electron app development easier.
|Mark Lee @malept||Chair||PT (Seattle)|
|Charles Kerr @ckerr||Member||CT (New Orleans)|
|Erick Zhao @erickzhao||Member||ET (Montreal)|
|Felix Rieseberg @felixrieseberg||Member||PT (San Francisco)|
|Kilian Valkhof @kilian||Member||CET (Netherlands)|
|Samuel Attard @MarshallOfSound||Member||PT (Vancouver)|
|Vlad Hashimoto @HashimotoYT||Member||???|
|Zeke Sikelianos @zeke||Member||PT|
Current Objective and Key Results
As a newcomer or experienced app developer, you can use Electron’s tooling and documentation to build your app well.
- Increase adoption of Electron-provided tooling.
- Decrease percentage of documented poor-practices
- Increase views on https://electronjs.org/docs
Areas of Responsibility
These projects are sorted alphabetically, their order does not reflect that any of them are "better" or "more important" than others.
- Documentation across all
electron/*repositories, primarily focusing on
electron/electron/docsin the repo and the website
- Implementation and design of the Electron website
- Management of Heroku apps for the site and associated repositories
- Management of the Algolia search tooling
- Management of translations via Crowdin
- Tools (Core)
- Docs Linter
- Download (
- Quickstart & API Demo repos
- Typescript Generator
- Update server (update.electronjs.org)
- Windows Installer (
- Tools (Userland)
...and all other third party community based Electron tools.
These repos are sorted alphabetically, their order does not reflect that any of them are "better" or "more important" than others.
Electron Userland Organization
...and all other repositories that the community would consider maintained by Electron.
Sync Meeting 30min every other Thursday @ 16:00 UTC
Meeting notes may be viewed in meeting-notes.
Prospective new members should reach out to an existing member to ask to be invited to the regular meetings and to be added as a Slack guest to #wg-ecosystem. That person may be added to the working group by a 2/3rds vote of WG members at a WG meeting. The prospective member should leave the meeting while the deliberation & vote is underway, and be informed only of the outcome of the vote (approved/not approved).