Oversees public API design based on project principles.
| Avatar | Name | Role | Time Zone |
|---|---|---|---|
 |
John Kleinschmidt @jkleinsc | Chair | ET (Harrisburg) |
 |
Shelley Vohr @codebytere | Member | PT (San Francisco) |
 |
Andy Locascio @loc | Member | PT (San Francisco) |
 |
Charles Kerr @ckerr | Member | CT (New Orleans) |
 |
Jeremy Apthorp @nornagon | Member | PT (San Francisco) |
 |
Keeley Hammond @VerteDinde | Member | PT (Portland) |
 |
Milan Burda @miniak | Member | CET (Prague) |
 |
Samuel Attard @MarshallOfSound | Member | PT (Vancouver) |
 |
Will Anderson @itsananderson | Member | PT (Seattle) |
- Define the process for which API changes are reviewed and approved.
- Create initiatives to develop/modify/change API implementations.
- Increase participation with web standards groups.
electron/electron
- Biweekly Rotating Times:
- 4 PM PT bi-weekly calendar
Meeting notes may be viewed in meeting-notes.
In order to become formal members of the WG, prospective members must:
- be actively contributing to the work of the WG,
- attend 2 out of 4 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 API Working Group, reach out to an existing member and ask to be invited to the regular meeting and as a guest to the #wg-api channel in Slack.
"Actively contributing" doesn't necessarily mean writing code. It does mean that you should be in regular communication with the API WG (including attending meetings), and it does mean that you should be materially contributing to the project in some way. If you're not sure whether the work you're doing counts as "materially contributing", reach out to a member and ask. 🙂