{"id":13516663,"url":"https://github.com/graphql/graphql-wg","last_synced_at":"2025-05-14T23:08:00.942Z","repository":{"id":38008874,"uuid":"99282819","full_name":"graphql/graphql-wg","owner":"graphql","description":"Working group notes for GraphQL","archived":false,"fork":false,"pushed_at":"2025-05-01T12:10:10.000Z","size":3395,"stargazers_count":550,"open_issues_count":23,"forks_count":231,"subscribers_count":100,"default_branch":"main","last_synced_at":"2025-05-01T13:24:22.924Z","etag":null,"topics":["agenda","graphql","meeting","meeting-notes"],"latest_commit_sha":null,"homepage":null,"language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/graphql.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2017-08-03T23:21:22.000Z","updated_at":"2025-05-01T12:10:12.000Z","dependencies_parsed_at":"2023-10-16T22:17:42.365Z","dependency_job_id":"93199911-d0ec-423c-9be5-1018e6dabc5c","html_url":"https://github.com/graphql/graphql-wg","commit_stats":{"total_commits":1724,"total_committers":228,"mean_commits":7.56140350877193,"dds":0.8254060324825986,"last_synced_commit":"a00fbae5f789261b6e932b0334c2cdf141568c16"},"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/graphql%2Fgraphql-wg","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/graphql%2Fgraphql-wg/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/graphql%2Fgraphql-wg/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/graphql%2Fgraphql-wg/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/graphql","download_url":"https://codeload.github.com/graphql/graphql-wg/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254243362,"owners_count":22038046,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["agenda","graphql","meeting","meeting-notes"],"created_at":"2024-08-01T05:01:24.639Z","updated_at":"2025-05-14T23:07:55.926Z","avatar_url":"https://github.com/graphql.png","language":"JavaScript","funding_links":[],"categories":["JavaScript","Others"],"sub_categories":[],"readme":"# GraphQL Working Group\n\nGraphQL WG (Working Group) is a set of recurring virtual meetings of maintainers\nof commonly used GraphQL libraries and tools and significant contributors to the\nGraphQL community hosted by the [GraphQL TSC][] as part of the [GraphQL\nFoundation][].\n\n[graphql tsc]: ./GraphQL-TSC.md\n[graphql foundation]: https://graphql.org/foundation/\n\nThe GraphQL WG's primary purpose is to discuss and agree upon proposed additions\nto the [GraphQL Specification](https://github.com/graphql/graphql-spec) via the\n[RFC process](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md).\nAdditionally, the group may discuss and collaborate on other relevant technical\ntopics concerning core GraphQL projects.\n\nAnyone in the public GraphQL community may attend a GraphQL WG meeting, provided\nthey first sign the [Specification Membership Agreement](./membership) or belong\nto an organization which has signed.\n\nThis repository holds [agendas](./agendas) and [notes](./notes) for all meetings\npast and upcoming as well as [shared rfc documents](./rfcs). Anyone may edit an\nupcoming event's agenda to _attend_ or _propose an agenda item_.\n\nAll meetings occur via video conference, however participating company offices\nare welcome to host guests.\n\nTo learn more, read our guide on how to [join a meeting](./JoiningAMeeting.md).\n\n# Upcoming meetings\n\n| Meeting              | Time                            | Host                                     |\n| -------------------- | ------------------------------- | ---------------------------------------- |\n| WG (Primary)         | 1st Thu, 10:30am - 12:00noon PT | [Lee Byron](https://github.com/leebyron) |\n| WG (Secondary, APAC) | 2nd Wed, 3:30pm - 5:00pm PT     | [Lee Byron](https://github.com/leebyron) |\n| WG (Secondary, EU)   | 3rd Thu, 10:30am - 12:00noon PT | [Lee Byron](https://github.com/leebyron) |\n\nThe primary monthly meeting is preferred for new agenda. The secondary meetings\nare for overflow agenda items, follow ups from the primary meeting, or agenda\nintroduced by those who could not make the primary meeting time. There are two\nsecondary meetings, each timed to be acceptable for those in either an Asia\nPacific or European timezone.\n\nMeetings are typically scheduled at the times listed, however always check the\n[agenda](./agendas) for the exact date and time of an upcoming meeting. Keep\ntrack of future upcoming meetings by subscribing to the [Google Calendar][] or\n[ical][].\n\n[google calendar]:\n  https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t\n[ical]:\n  https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics\n\nTo create the agenda files for a given month YYYY/MM, run the following command:\n\n```\nyarn \u0026\u0026 yarn gen-agenda YYYY MM\n```\n\n### Subcommittee meetings\n\nThe GraphQL WG has subcomittees who focus on the development of specific\nprojects beyond the GraphQL Spec. These subcomittees make progress within their\nown meetings and report back progress and decisions to GraphQL WG meetings.\n\n| Subcommittee         | Time                           | Host                                               | Agenda Repo                                                                                                     |\n| -------------------- | ------------------------------ | -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |\n| GraphiQL             | 2nd Tue, 9:00am - 11:00am PT   | [Tim Suchanek](https://github.com/timsuchanek)     | [graphql/graphiql/working-group](https://github.com/graphql/graphiql/tree/main/working-group)                   |\n| GraphQL-over-HTTP    | 4th Thu, 17:30 - 18:30 UTC     | [Benjie Gillam](https://github.com/benjie)         | [graphql/graphql-over-http/working-group](https://github.com/graphql/graphql-over-http/tree/main/working-group) |\n| Incremental Delivery | 2nd Mon, 10:00am - 11:00am EST | [Rob Richard](https://github.com/robrichard)       | [robrichard/defer-stream-wg](https://github.com/robrichard/defer-stream-wg)                                     |\n| Nullability          | 4th Wed, 19:00 - 20:00 UTC     | [Stephen Spalding](https://github.com/fotoetienne) | [graphql/client-controlled-nullability-wg](https://github.com/graphql/client-controlled-nullability-wg)         |\n| Composite Schema     | 2nd Thu, 16:00am - 17:00am UTC | [Benjie Gillam](https://github.com/benjie)         | [graphql/composite-schemas-wg](https://github.com/graphql/composite-schemas-wg)                                 |\n| GraphQL.js           | 4th Wed, 10:00am - 11:00am PT  | [Jovi DeCroock](https://github.com/JoviDeCroock)   | [graphql/graphql-js-wg](https://github.com/graphql/graphql-js-wg)                                               |\n\n#### Subcommittees on hiatus\n\nThese subcommittees are currently not meeting, typically due to lack of agenda\ntopics. Should you have a topic to discuss that applies to a subcommittee that\nis on hiatus, please raise an issue in the WG repository and mention the host.\n\n\u003c!-- prettier-ignore --\u003e\n| Subcommittee         | Time                           | Host                                               | Agenda Repo                                                                                                     |\n| -------------------- | ------------------------------ | -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |\n\n### Joining a meeting?\n\nTo request participation in an upcoming meeting, please send a pull request by\nediting the relevant [meeting agenda](./agendas).\n\n### Want to help us keep up?\n\nWe're always looking for volunteers to help take notes from the meetings, the\nresults of which are shared in [`notes/`](./notes). If you're interested in\ntaking notes, sign up for a meeting in [`agendas/`](./agendas) and indicate that\nyou're willing to be a note taker.\n\n# Participation guidelines\n\nMeetings with many participants, especially over video, can easily get hard to\nfollow or run off course. When we talk about issues we care about, it's easy to\nget into heated debate. In order to respect everyone's time, and arrive to\nworthwhile outcomes, consider a few guidelines:\n\n_These guidelines are heavily inspired by\n[Allen Wirfs-Brock](http://wirfs-brock.com/allen/files/papers/standpats-asianplop2016.pdf)._\n\n### Participate\n\nBeing in the room when decisions are being made is exciting, but meetings with\nlarge groups of people are much more difficult to follow. Only attend if an\nagenda item directly concerns you and your work, and you expect to participate.\n\n### Don't talk too much\n\nThe biggest distraction with many people on a video call is interruption, and\ninterruptions are frequent when someone is talking for too long. Only speak up\nif you have something important to add to the discussion and be courteous of\nothers and avoid interruption.\n\n### Volunteer to take notes\n\nThe rest of the community follows along with the group's discussion by reading\nthe meeting notes. Volunteering to take notes is a great service to that\ncommunity and a great way to participate if you don't have an agenda item.\n\n### Have an outcome in mind\n\nKnow what you and your organization wish to accomplish from the meeting and make\nthat clear to the group to keep discussion focused on what's valuable to your\nagenda item. Complex or challenging outcomes might take intermediate goals\nacross multiple meetings.\n\n### Contribute\n\nProjects like GraphQL succeed when their leaders are active contributors more\nthan passive participants. Follow up on your discussion with pull requests to\nprojects, or planned events.\n\n### Choose your battles\n\nWe're all passionate about GraphQL and it's easy to get mired with an opinion in\nevery agenda item. There are many ways to solve a problem and you won't always\nagree with all of them. Express your views but don't argue about a topic that is\nnot relevant to your goals.\n\n### Champion alternatives\n\nSometimes you'll disagree with someone but will find it difficult or impossible\nto convince them of the problems you see. Instead of spending your energy\nfighting, commit to developing an alternative proposal so future discussion can\nbe about substance.\n\n### Block progress as a last resort\n\nThis working group is only effective when consensus can be reached, even though\nthere may be disagreements along the way. You should avoid blocking progress if\npossible, otherwise you may be seen as hostile to the group. However, if you\nhave a serious issue with a proposed agenda item outcome, you must make it\nclear.\n\n### Be patient and persistent\n\nThe GraphQL specification evolves slowly, deliberately, and with the consensus\nof the core GraphQL community. The spec\n[contribution process](https://github.com/graphql/graphql-spec/blob/master/CONTRIBUTING.md)\nrequires considerable investment through multiple stages while meeting a\ndemanding set of guiding principles. This can take a long time, and progress in\neach meeting can feel small. Don't give up!\n\n# Contributing to this repo\n\nThis repository is managed by EasyCLA. Project participants must sign the free\n([GraphQL Specification Membership agreement](https://preview-spec-membership.graphql.org)\nbefore making a contribution. You only need to do this one time, and it can be\nsigned by\n[individual contributors](http://individual-spec-membership.graphql.org/) or\ntheir [employers](http://corporate-spec-membership.graphql.org/).\n\nTo initiate the signature process please open a PR against this repo. The\nEasyCLA bot will block the merge if we still need a membership agreement from\nyou.\n\nYou can find\n[detailed information here](https://github.com/graphql/graphql-wg/tree/main/membership).\nIf you have issues, please email\n[operations@graphql.org](mailto:operations@graphql.org).\n\n## Commit access\n\nCommit access is granted to this repo to members of the\n[GraphQL TSC](./GraphQL-TSC.md) and some regular attendees of working group\nmeetings. To request commit access, please reach out to a TSC member.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fgraphql%2Fgraphql-wg","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fgraphql%2Fgraphql-wg","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fgraphql%2Fgraphql-wg/lists"}