Skip to content

Latest commit

 

History

History
143 lines (115 loc) · 9.67 KB

README.md

File metadata and controls

143 lines (115 loc) · 9.67 KB
Raw

Ecosystem WG

Oversees the projects that make Electron app development easier.

Membership

Avatar Name Role Time Zone
@blackhole1 Black-Hole @blackhole1 Member BJT (Hangzhou)
@caoxiemeihao caoxiemeihao @caoxiemeihao Member BJT (Hangzhou)
@ckerr Charles Kerr @ckerr Member CT (New Orleans)
@dsanders11 David Sanders @dsanders11 Member PT (Santa Barbara)
@erickzhao Erick Zhao @erickzhao Member PT (Vancouver)
@erikian Erik Moura @erikian Member BRT (Francisco Beltrão)
@felixrieseberg Felix Rieseberg @felixrieseberg Member PT (San Francisco)
@georgexu99 George Xu @georgexu99 Member PT (San Francisco)
@kilian Kilian Valkhof @kilian Member CET (Netherlands)
@malept Mark Lee @malept Member PT (Seattle)
@marshallofsound Samuel Attard @MarshallOfSound Member PT (Vancouver)
@Toinane Toinane @toinane Member CET (France)
@VerteDinde Keeley Hammond @VerteDinde Member PT (Portland)
@yangannyx Anny Yang @yangannyx Member PST (San Francisco)

Emeritus Members

Emeritus Members
Avatar Name Role Time Zone
@molant Antón Molleda @molant Chair PT (Seattle)
@sofianguy Sofia Nguy @sofianguy Member PT (San Francisco)
@vhashimotoo Vlad Hashimoto @vhashimotoo Chair CET (Germany, Frankfurt am Main)
@bandantonio Anton Zolotukhin @bandantonio Observer (until December 2020) EET (Kharkov)
@shiftkey Brendan Forster @shiftkey Member AT (Canada)
@miniak Milan Burda @miniak Member CET (Prague)
@nitsakh Nitish Sakhawalkar @nitsakh Member PT (San Francisco)

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/docs in the repo and the website
  • Implementation and design of the Electron website
    • Management of Heroku apps for our repositories
    • Management of the Algolia search tooling
    • Management of translations via Crowdin
  • Tools (Core)
    • Download (@electron/get)
    • Fiddle
    • Forge
    • Notarize
    • osx-sign
    • Packager
    • Quickstart & API Demo repos
    • rcedit
    • Rebuild
    • Typescript Generator
    • Update server (update.electronjs.org)
    • Windows Installer (electron-winstaller)
  • Tools (Userland)
    • electron-installer-*

...and all other third party community based Electron tools.

WG Removal Policy

If a sitting member of the WG has not been active in a meaningful way for at least one month, the WG may vote to remove them from its set of sitting members.

This is done primarily to ensure that there are no open avenues of compromise for the project given that the Ecosystem WG confers notable permissions.

Associated Repositories

These repos are sorted alphabetically, their order does not reflect that any of them are "better" or "more important" than others.

Electron Organization

Electron Userland Organization

...and all other repositories that the community would consider maintained by Electron.

Node.js Upgrade Policy

As a general rule, npm packages under the purview of the Ecosystem WG will support Node.js versions as long as possible, even after a version has reached its End-Of-Life (EOL) date. If too much friction arises from the burden of maintaining EOL versions of Node.js (e.g. trouble upgrading dependencies or CI issues), we will perform a blanket upgrade of supported Node.js versions for all our packages to the latest LTS version. This upgrade process will be revisited annually.

As of July 2024, our current plan is to upgrade all packages to the earliest Node.js version where require() of synchronous ESM graphs will be supported (see nodejs/node#51977 and nodejs/node#53500) some point after that version reaches its LTS date (see Node.js release schedule for more details).

Meeting Schedule

Sync Meeting 1 hour every other Tuesday @ 17:00 UTC

Meeting notes may be viewed in meeting-notes.

Joining the Ecosystem WG

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