Skip to content

Latest commit

 

History

History
58 lines (39 loc) · 4.04 KB

README.md

File metadata and controls

58 lines (39 loc) · 4.04 KB

API WG

Oversees public API design based on project principles.

Membership

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

Areas of Responsibility

  • 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.

Associated Repositories

Meeting Schedule

  • Biweekly Rotating Times:

Meeting notes may be viewed in meeting-notes.

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).
    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. 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.

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 (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. 🙂