governance/wg-infra
Samuel Attard deea2f2274
docs: document the current state of npm access (#581)
2024-09-09 16:30:21 -04:00
..
meeting-notes build: lint Markdown (#535) 2023-05-09 09:09:00 -07:00
policy docs: document the current state of npm access (#581) 2024-09-09 16:30:21 -04:00
scripts fix: update wg-infra npm script for npm v10 (#560) 2023-10-27 19:32:19 -04:00
README.md chore: add @VerteDinde to Infra WG (#548) 2023-08-01 19:18:15 +02:00

README.md

Infrastructure WG

Oversees all infrastructure, bots, automation, services and systems that support the Electron maintainers group.

Membership

Avatar Name Role Time Zone
@marshallofsound Samuel Attard @MarshallOfSound Member PT (Vancouver)
@codebytere Shelley Vohr @codebytere Member CET (Berlin)
@jkleinsc John Kleinschmidt @jkleinsc Member ET (Harrisburg)
@VerteDinde Keeley Hammond @VerteDinde Member PT (Portland)

Areas of Responsibility

Rules for Membership

In order to join the Infrastructure Working Group, an aspiring member must:

  1. Show a continued interest in the systems this group is responsible for
  2. Be a long-trusted member of the maintainers community
  3. TBD, this group is still forming primarily in an organizational capacity, when the initial storm is over this list will be updated with a more accurate set of requirements

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. The vote must pass with a majority (>50% of sitting members excluding the subject of the vote).

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