{"id":13516076,"url":"https://github.com/graphql/graphql-js-wg","last_synced_at":"2025-05-07T15:21:02.526Z","repository":{"id":38186395,"uuid":"305844562","full_name":"graphql/graphql-js-wg","owner":"graphql","description":"Working group notes for graphql-js","archived":false,"fork":false,"pushed_at":"2025-05-02T18:00:07.000Z","size":186,"stargazers_count":27,"open_issues_count":8,"forks_count":24,"subscribers_count":16,"default_branch":"main","last_synced_at":"2025-05-06T07:09:13.353Z","etag":null,"topics":[],"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}},"created_at":"2020-10-20T22:08:10.000Z","updated_at":"2025-05-02T18:00:11.000Z","dependencies_parsed_at":"2024-02-04T18:03:28.697Z","dependency_job_id":"4c66cb25-aa90-4628-95da-195c1da3e1bd","html_url":"https://github.com/graphql/graphql-js-wg","commit_stats":{"total_commits":128,"total_committers":25,"mean_commits":5.12,"dds":0.7265625,"last_synced_commit":"1891ffe404db8858cc3b3c8e0e36cbc3734a185c"},"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/graphql%2Fgraphql-js-wg","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/graphql%2Fgraphql-js-wg/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/graphql%2Fgraphql-js-wg/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/graphql%2Fgraphql-js-wg/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/graphql","download_url":"https://codeload.github.com/graphql/graphql-js-wg/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":252902717,"owners_count":21822288,"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":[],"created_at":"2024-08-01T05:01:18.862Z","updated_at":"2025-05-07T15:21:02.507Z","avatar_url":"https://github.com/graphql.png","language":"JavaScript","funding_links":[],"categories":["JavaScript","Others"],"sub_categories":[],"readme":"# GraphQL-JS Working Group\n\nGraphQL-JS WG (Working Group) is a monthly virtual meeting of maintainers of\ncommonly used GraphQL libraries and tools and significant contributors in the Javascript ecosystem, operated by the GraphQL Foundation.\n\nThe GraphQL-JS WG's primary purpose is to discuss and agree upon\nproposed changes to the [GraphQL-JS](https://github.com/graphql/graphql-spec)\nlibrary and other related foundation libraries like [express-graphql](https://github.com/graphql/express-graphql) and [graphql-relay-js](https://github.com/graphql/graphql-relay-js).\nAdditionally, the group may discuss and collaborate on other relevant technical topics concerning core Javascript GraphQL projects.\n\nAnyone in the public GraphQL community may attend a GraphQL-JS WG meeting, provided\nthey first sign the [Specification Membership Agreement](https://github.com/graphql/foundation) or belong to an organization which has signed.\n\nThis repository holds **agendas** and **notes** for all meetings past and\nupcoming. Anyone may edit an upcoming event's agenda to _attend_ or _propose\nan agenda item_.\n\nAll meetings occur via video conference, however participating company\noffices are welcome to host guests.\n\nMeetings are typically scheduled for the last Wednesday of each month at 5:00pm\nUTC. Check the [`agendas/`](./agendas) for the exact date and time\nof upcoming meetings.\n\nKeep track of future upcoming meetings by subscribing to the\n[Google Calendar](https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com) or [ical file](https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics). (maintained in UTC because time zones are hard).\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### 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\ninterested in taking notes, sign up for a meeting in [`agendas/`](./agendas) and\nindicate that you'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 [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\nis not relevant to your goals.\n\n### Champion alternatives\n\nSometimes you'll disagree with someone but will find it difficult or\nimpossible to convince them of the problems you see. Instead of spending your\nenergy fighting, commit to developing an alternative proposal so future\ndiscussion can be 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\nit clear.\n\n### Be patient and persistent\n\nThe GraphQL projects evolves slowly, deliberately, and with the consensus\nof the core GraphQL community. The spec [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 ([GraphQL Specification Membership agreement](https://preview-spec-membership.graphql.org) before making a contribution. You only need to do this one time, and it can be signed by [individual contributors](http://individual-spec-membership.graphql.org/) or their [employers](http://corporate-spec-membership.graphql.org/).\n\nTo initiate the signature process please open a PR against this repo. The EasyCLA bot will block the merge if we still need a membership agreement from you.\n\nYou can find [detailed information here](https://github.com/graphql/graphql-wg/tree/main/membership). If you have issues, please email [operations@graphql.org](mailto:operations@graphql.org).\n\nIf your company benefits from GraphQL and you would like to provide essential financial support for the systems and people that power our community, please also consider membership in the [GraphQL Foundation](https://foundation.graphql.org/join).\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fgraphql%2Fgraphql-js-wg","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fgraphql%2Fgraphql-js-wg","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fgraphql%2Fgraphql-js-wg/lists"}