|
…
|
||
|---|---|---|
| .. | ||
| meeting-notes | ||
| policy | ||
| scripts | ||
| README.md | ||
README.md
Infrastructure WG
Oversees all infrastructure, bots, automation, services and systems that support the Electron maintainers group.
Membership
| Avatar | Name | Role | Time Zone |
|---|---|---|---|
 |
Samuel Attard @MarshallOfSound | Member | PT (Vancouver) |
 |
Shelley Vohr @codebytere | Member | CET (Berlin) |
 |
John Kleinschmidt @jkleinsc | Member | ET (Harrisburg) |
 |
Keeley Hammond @VerteDinde | Member | PT (Portland) |
Areas of Responsibility
- Cloud Services
- Heroku
- AWS
- Azure
- GitHub
- Grafana
- Goma
- CircleCI
- Appveyor
- Sentry
- Slack
- 1Password
- NPM (Including CFA)
- Electron Bots - Specifically the hosting systems and deployments, actual bot implementations may be owned by other working groups.
- Permission and Access Controls (Sheriff, etc.)
- Maintainer tooling
Rules for Membership
In order to join the Infrastructure Working Group, an aspiring member must:
- Show a continued interest in the systems this group is responsible for
- Be a long-trusted member of the maintainers community
- 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.