-
Notifications
You must be signed in to change notification settings - Fork 228
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implement new WG times + secondary meetings (#1125)
* Implement new WG times + secondary meetings This is an implemented final proposal for [Changed Working Group times](#1051) As a short recap, a couple meetings ago the topic was raised to take a fresh look at our meeting cadence based on a few concerns: - A two hour meeting was a little too long - Timing was late in the day for EU - Timing was middle of the night for APAC - Agendas ran over, without a path for overflow - Significant progress is being made, and a monthly cadence isn't fast enough. This changes timing as follows: - The existing WG meeting is now named "Primary", remains on first Thursdays, but is reduced to 1.5hr and shifted slightly earlier. - Two new "Secondary" WG meetings are added, one at the same time on third Thursdays, and one +5hr on second Wednesdays to be more APAC available. This also revises agenda templates and file system: - Year/Month/ becomes a directory with named meeting agenda files within - Updated intro text describing the meeting purpose - Updated the timeanddate links to use the newer meeting scheduling tool. - List times in Pacific Time instead of UTC, since that is how our calendar entries have been working. Finally, this adds tables of all meetings for WG and subcommittees in the repo README. * Add GraphiQL subcomittee and sort by time
- Loading branch information
Showing
10 changed files
with
782 additions
and
60 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,115 @@ | ||
| <!-- | ||
| Hello! You're welcome to join our working group 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 the graphql-wg repo. | ||
| - As a GitHub discussion in the graphql-wg repo. | ||
| - As an RFC document into the rfcs/ folder of the graphql-wg 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 operations@graphql.org. | ||
| 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 | ||
| --> | ||
|
|
||
| | This is an open meeting: To attend or add agenda, send a Pull Request against this file. | | ||
| | ---------------------------------------------------------------------------------------- | | ||
|
|
||
| # GraphQL WG – October 2022 (Secondary, APAC) | ||
|
|
||
| The GraphQL Working Group meets regularly to discuss changes to the | ||
| [GraphQL Specification][] and other core GraphQL projects. This is an open | ||
| meeting in which anyone in the GraphQL community may attend. | ||
|
|
||
| This is a secondary meeting, timed to be acceptable for those in Asia Pacific | ||
| timezones, which typically meets on the second Wednesday of the month. The | ||
| primary meeting is preferred for new agenda, where this meeting is for overflow | ||
| agenda items, follow ups from the primary meeting, or agenda introduced by those | ||
| who could not make the primary meeting time. | ||
|
|
||
| - **Date & Time**: [October 12th 2022 3:30pm - 5:00pm PT](https://www.timeanddate.com/worldclock/converter.html?iso=20221012T223000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240) | ||
| - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]). | ||
| - _Please Note:_ The date or time may change. Please check this agenda the | ||
| week of the meeting to confirm. While we try to keep all calendars accurate, | ||
| this agenda document is the source of truth. | ||
| - **Video Conference Link**: https://zoom.us/j/593263740 | ||
| - _Password:_ graphqlwg | ||
| - **Live Notes**: [Google Doc]() | ||
|
|
||
| [graphql specification]: https://github.com/graphql/graphql-spec | ||
| [calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com | ||
| [google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t | ||
| [ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics | ||
|
|
||
| ## Attendees | ||
|
|
||
| | Name | GitHub | Organization | Location | | ||
| | :--------------- | :-------- | :----------------- | :-------------------- | | ||
| | Lee Byron (Host) | @leebyron | GraphQL Foundation | San Francisco, CA, US | | ||
|
|
||
| ## Agenda | ||
|
|
||
| 1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Lee) | ||
| - [Specification Membership Agreement](https://github.com/graphql/foundation) | ||
| - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines) | ||
| - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md) | ||
| - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md) | ||
| 1. Introduction of attendees (5m, Lee) | ||
| 1. Determine volunteers for note taking (1m, Lee) | ||
| 1. Review agenda (2m, Lee) | ||
| 1. Review previous meeting's action items (5m, Lee) | ||
| - [Ready for review](https://github.com/graphql/graphql-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) | ||
| - [All open action items (by last update)](https://github.com/graphql/graphql-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Action+item+%3Aclapper%3A%22+sort%3Aupdated-desc) | ||
| - [All open action items (by meeting)](https://github.com/graphql/graphql-wg/projects?query=is%3Aopen+sort%3Aname-asc) |
Oops, something went wrong.