governance/wg-api

API WG

Oversees public API design based on project principles.

Membership

Avatar	Name	Role	Time Zone
	Shelley Vohr @codebytere	Member	CET (Berlin)
	Jeremy Rose @nornagon	Member	PT (San Francisco)
	Charles Kerr @ckerr	Member	CT (New Orleans)
	John Kleinschmidt @jkleinsc	Member	ET (Harrisburg)
	Milan Burda @miniak	Member	CET (Prague)
	Samuel Attard @MarshallOfSound	Member	PT (Vancouver)
	Will Anderson @itsananderson	Member	PT (Seattle)
	Sam Maddock @samuelmaddock	Member	ET (New York City)
	Erick Zhao @erickzhao	Member	PT (Vancouver)

Emeritus Members

Emeritus Members

Avatar	Name	Role	Time Zone
	Cheng Zhao @zcbenz	Member	JST (Nagoya)

Areas of Responsibility

• Define the process for which API changes are reviewed and approved.
• Create initiatives to develop/modify/change API implementations.
• Review PRs requesting API WG approval.
• Review proposed RFCs.
• Increase participation with web standards groups.

Associated Repositories

• electron/electron
• electron/rfcs
• electron/zoilist

Joining the API WG

In order to become formal members of the WG, prospective members must:

1. Be actively contributing to the work of the WG, and
2. Be approved by a 2/3rds majority of current WG members (rounded up). A meeting will be scheduled to commence voting.
   1. The prospective member shall leave the meeting during the deliberation and vote.
   2. The meeting notes shall contain only the outcome of the vote (approved/not approved), not the individual votes.
   3. If quorum is unable to be met, an asynchronous vote via Slack can be used as a substitute with the same approval rules.

If you're interested in joining the API Working Group, reach out to an existing member and ask to be invited as a guest to the #wg-api channel in Slack.

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 API WG confers notable permissions.

Actively contributing

"Actively contributing" doesn't necessarily mean writing code. It does mean that you should be in regular communication with the API WG, 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. 🙂