Set up wgutils, correct time in README, add February agenda

JoiningAMeeting.md

@@ -0,0 +1,77 @@
+# Joining a meeting
+
+1. Subscribe to our [calendar][] to see upcoming meetings.
+2. Find an upcoming [agenda file][] in the `working-group/agendas/` directory.
+3. Read and follow the steps below to add yourself to an upcoming meeting.
+
+[calendar]:
+  https://calendar.google.com/calendar/u/0/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8@group.calendar.google.com
+[agenda file]:
+  https://github.com/graphql/graphql-over-http/tree/main/working-group/agendas
+
+## How to join
+
+Hello! You're welcome to join our subcommittee meeting and add to the agenda by
+following these three steps:
+
+1.  Add your name to the list of attendees (in alphabetical order).
+
+    - To respect meeting size, attendees should be relevant to the agenda. That
+      means we expect most who join the meeting to participate in discussion. If
+      you'd rather just watch, check out our YouTube[1].
+
+    - Please include the organization (or project) you represent, and the
+      location (including country code[2]) you expect to be located in during
+      the meeting.
+
+    - If you're willing to help take notes, add "✏️" after your name (eg. Ada
+      Lovelace ✏). This is hugely helpful!
+
+2.  If relevant, add your topic to the agenda (sorted by expected time).
+
+    - Every agenda item has four parts: 1) the topic, 2) an expected time
+      constraint, 3) who's leading the discussion, and 4) a list of any relevant
+      links (RFC docs, issues, PRs, presentations, etc). Follow the format of
+      existing agenda items.
+
+    - Know what you want to get out of the agenda topic - what feedback do you
+      need? What questions do you need answered? Are you looking for consensus
+      or just directional feedback?
+
+    - If your topic is a new proposal it's likely an "RFC 0"[3]. The barrier of
+      entry for documenting new proposals is intentionally low, writing a few
+      sentences about the problem you're trying to solve and the rough shape of
+      your proposed solution is normally sufficient.
+
+      You can create a link for this:
+
+      - As an issue against this repo.
+      - As a GitHub discussion in this repo.
+      - As an RFC document into the rfcs/ folder of this repo.
+
+3.  Review our guidelines and agree to our Spec Membership & CLA.
+
+    - Review and understand our Spec Membership Agreement, Participation &
+      Contribution Guidelines, and Code of Conduct. You'll find links to these
+      in the first agenda item of every meeting.
+
+    - If this is your first time, our bot will comment on your Pull Request with
+      a link to our Spec Membership & CLA. Please follow along and agree before
+      your PR is merged.
+
+      Your organization may sign this for all of its members. To set this up,
+      please ask [email protected].
+
+PLEASE TAKE NOTE:
+
+- By joining this meeting you must agree to the Specification Membership
+  Agreement and Code of Conduct.
+
+- Meetings are recorded and made available on YouTube[1], by joining you consent
+  to being recorded.
+
+[1] Youtube: https://www.youtube.com/channel/UCERcwLeheOXp_u61jEXxHMA [2]
+Country codes:
+https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes#Current_ISO_3166_country_codes
+[3] RFC stages:
+https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md#rfc-contribution-stages