Oversees upgrades of upstream dependencies; specifically Chromium and Node.
|John Kleinschmidt @jkleinsc||Chair||EST (Harrisburg)|
|Jeremy Rose @nornagon||Member||PST (San Francisco)|
|Deepak Mohan @deepak1556||Member||PST (Redmond)|
|Shelley Vohr @codebytere||Member||CET (Berlin)|
|Samuel Attard @MarshallOfSound||Member||PST (Vancouver)|
|Charles Kerr @ckerr||Member||CST (New Orleans)|
|Calvin Watford @clavin||Member||MST (Salt Lake City)|
|Keeley Hammond @VerteDinde||Member||PST (Portland)|
Areas of Responsibility
- Ensuring that Chromium and Node upgrades happen in a timely fashion
- Upgrade-related tooling such as patch scripts, roller-bot
- Advising on maintenance burden of feature support for Chromium features
- When an Electron feature depends on or heavily integrates with Chromium, the upgrades working group will be responsible for assessing ongoing maintenance burden.
- Upstreaming patches
- Adding/dropping dependencies
- Sync Meeting 30 min monthly @ 16:00 UTC
Meeting notes may be viewed in meeting-notes.
Joining the Upgrades WG
In order to become formal members of the WG, prospective members must:
- be actively contributing to the work of the Upgrades WG,
- attend 3 out of 6 consecutive meetings, and
- be approved by a 2/3rds majority of current WG members (rounded up).
- The prospective member shall leave the meeting during the deliberation and vote.
- The meeting notes shall contain only the outcome of the vote (approved/not approved), not the individual votes.
- Members not able to attend the meeting at which the vote occurs may submit their vote to the Chair prior to the meeting.
If you're interested in joining the Upgrades Working Group, reach out to an existing member and ask to be invited to the regular meeting and as a guest to the #wg-upgrades channel in Slack.
"Actively contributing" doesn't necessarily mean writing code, and it doesn't mean you have to be full-time on Electron Upgrades. It does mean that you should be in regular communication with the Upgrades WG (including attending meetings), and it does mean that you should be materially contributing to the project in some way. Some examples of actively contributing:
- You maintain a piece of code that integrates with Chromium (possibly including some patches), and it occasionally breaks during major Chromium upgrades. You don't write code every week, but you're available in the Slack channel to field questions about that component.
- You communicate regularly with the team maintaining one of Electron's dependencies, and help to coordinate releases and connect people on those teams to Electron. You don't write any code in Electron, but you help out reviewing the occasional PR.
- You help triage bugs reported on Electron's issue tracker related to Electron's dependencies.
This is not an exhaustive list of ways you could be involved in the Upgrades WG. If you're not sure whether the Upgrades-related work you're doing counts as "actively contributing", reach out to a member and ask.
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 Upgrades WG confers notable permissions.
The Upgrades WG currently meets only at 16:00 UTC because all current members are in timezones compatible with that meeting time. If you are unable to make that meeting time, let someone in the group know and we will switch to an alternating meeting schedule to accommodate all timezones.