chore: update API WG readme (#574)

wg-api/README.md

@@ -14,38 +14,34 @@ Oversees public API design based on project principles.
 | <img src="https://github.com/marshallofsound.png" width=100 alt="@marshallofsound">  | Samuel Attard [@MarshallOfSound](https://github.com/marshallofsound) | Member | PT (Vancouver) |
 | <img src="https://github.com/itsananderson.png" width=100 alt="@itsananderson">  | Will Anderson [@itsananderson](https://github.com/itsananderson) | Member | PT (Seattle) |
 | <img src="https://github.com/zcbenz.png" width=100 alt="@zcbenz">  | Cheng Zhao [@zcbenz](https://github.com/zcbenz) | Member | JST (Nagoya) |
-| <img src="https://github.com/samuelmaddock.png" width=100 alt="@samuelmaddock">  | Sam Maddock [@samuelmaddock](https://github.com/samuelmaddock) | Member | ET (Charlottesville) |
+| <img src="https://github.com/samuelmaddock.png" width=100 alt="@samuelmaddock">  | Sam Maddock [@samuelmaddock](https://github.com/samuelmaddock) | Member | ET (New York City) |
 | <img src="https://github.com/erickzhao.png" width=100 alt="@erickzhao">  | Erick Zhao [@erickzhao](https://github.com/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.
+* Review PRs requesting API WG approval.
+* Review proposed RFCs.
 * Increase participation with web standards groups.
 
 ## Associated Repositories
 
 * [`electron/electron`](https://github.com/electron/electron)
+* [`electron/rfcs`](https://github.com/electron/rfcs)
 * [`electron/zoilist`](https://github.com/electron/zoilist)
 
-## Meeting Schedule
-
-* Biweekly Rotating Times:
-  * 4 PM PT bi-weekly [calendar](https://calendar.google.com/event?action=TEMPLATE&tmeid=N21qcmpibWdiZTgwYmFkb2dwanNsY2Zmb3BfMjAyMDA4MjRUMjMwMDAwWiBlbGVjdHJvbmpzLm9yZ19zbm1qMW4xMmYyNnRqZ3UyZm11NmY0Nm8zOEBn&tmsrc=electronjs.org_snmj1n12f26tjgu2fmu6f46o38%40group.calendar.google.com&scp=ALL)
-
-Meeting notes may be viewed in [meeting-notes](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
-1. be approved by a 2/3rds majority of current WG members (rounded up).
+1. Be actively contributing to the work of the WG, and
+1. 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.
     1. The meeting notes shall contain only the outcome of the vote (approved/not approved), not the individual votes.
     1. 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](#membership) and ask to be invited to the regular meeting and as a guest to the #wg-api channel in Slack.
+If you're interested in joining the API Working Group, reach out to an [existing member](#membership) and ask to be invited as a guest to the #wg-api channel in Slack.
 
 ## WG Removal Policy
 
@@ -55,4 +51,4 @@ This is done primarily to ensure that there are no open avenues of compromise fo
 
 ### 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](#membership) and ask. 🙂
+"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](#membership) and ask. 🙂