Implement new WG times + secondary meetings #1125
Merged
Conversation
This file contains hidden or 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
leebyron
requested review from
brianwarner and
a team
and removed request for
brianwarner
leebyron
force-pushed
the
new-wg-times
branch
from
96c7e25 to
771b96a
Compare
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.
leebyron
force-pushed
the
new-wg-times
branch
from
771b96a to
413a147
Compare
benjie
requested changes
Sep 14, 2022
| | ---------------- | ----------------------------- | -------------------------------------------------- | ------------------------------------------------------------------------------------------------- | | ||
| | GraphQL.js | 4th Wed, 10:00am - 11:00am PT | [Ivan Goncharov](https://github.com/IvanGoncharov) | [graphql/graphql-js-wg](https://github.com/graphql/graphql-js-wg) | | ||
| | GraphQL HTTP | 3rd Thu, 8:00am - 10:00am PT | [Benjie Gillam](https://github.com/benjie) | [graphql/graphql-over-http](https://github.com/graphql/graphql-over-http/tree/main/working-group) | | ||
| | Composite Schema | 2nd Thu, 8:00am - 10:00am PT | [Benjie Gillam](https://github.com/benjie) | [graphql/composite-schemas-wg](https://github.com/graphql/composite-schemas-wg) | |
There was a problem hiding this comment.
There's also the GraphiQL subcommittee. We had a meeting for metadata, but it seems that may have moved back to the main WG?
|
LGTM! Let's add GraphiQL and then we should be good to go 🙌 |
leebyron
force-pushed
the
new-wg-times
branch
from
8e84928 to
a6912aa
Compare
benjie
approved these changes
Sep 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an implemented final proposal for Changed Working Group times
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:
This changes timing as follows:
This also revises agenda templates and file system:
Finally, this adds tables of all meetings for WG and subcommittees in the repo README.