├── assets ├── all-assets.sketch ├── ambassador-form.png ├── youtube-banner.png └── twitter-bluesky banner.png ├── agendas ├── 2025 │ ├── 05-May │ │ └── 08-community-working-group-may-2025.md │ ├── 08-Aug │ │ └── 14-community-working-group-august-2025.md │ ├── 12-Dec │ │ ├── 11-community-working-group-december-2025.md │ │ └── 18-community-working-group-december-2025.md │ ├── 07-Jul │ │ └── 10-community-working-group-july-2025.md │ ├── 11-Nov │ │ └── 13-community-working-group-november-2025.md │ ├── 10-Oct │ │ └── 09-community-working-group-october-2025.md │ ├── 09-Sep │ │ └── 25-community-working-group-september-2025.md │ ├── 06-Jun │ │ └── 12-community-working-group-june-2025.md │ ├── 04-Apr │ │ └── 10-community-working-group-april-2025.md │ ├── 02-Feb │ │ └── 13-community-working-group-february-2025.md │ └── 03-Mar │ │ └── 13-community-working-group-march-2025.md ├── 2026 │ ├── 01-Jan │ │ └── 08-community-working-group-january-2026.md │ ├── 03-Mar │ │ └── 12-community-working-group-march-2026.md │ └── 02-Feb │ │ └── 12-community-working-group-february-2026.md └── README.md ├── cheatsheet ├── graphql-cheatsheet.pdf ├── graphql-cheatsheet.sketch └── README.md ├── .gitignore ├── .prettierignore ├── cspell.yml ├── .github ├── ISSUE_TEMPLATE │ ├── action-item.md │ └── event-submission.yml ├── PULL_REQUEST_TEMPLATE │ └── agenda-attendance.md └── workflows │ └── wgutils-automerge.yml ├── package.json ├── rfcs ├── README.md └── ambassador-program │ ├── README.md │ ├── overview-for-ambassadors.md │ ├── standards-of-excellence.md │ └── overview-for-organizers.md ├── notes ├── 2025 │ ├── summary-2025-03-13.md │ ├── 2025-06.md │ ├── summary-2025-10-09.md │ ├── 2025-09.md │ ├── 2025-04.md │ ├── summary-2025-04-10.md │ ├── summary-2025-09-25.md │ ├── 2025-02.md │ └── 2025-03.md └── README.md ├── social-media └── social-media-guide.md ├── wg.config.js └── README.md /assets/all-assets.sketch: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/graphql/community-wg/main/assets/all-assets.sketch -------------------------------------------------------------------------------- /assets/ambassador-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/graphql/community-wg/main/assets/ambassador-form.png -------------------------------------------------------------------------------- /assets/youtube-banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/graphql/community-wg/main/assets/youtube-banner.png -------------------------------------------------------------------------------- /agendas/2025/05-May/08-community-working-group-may-2025.md: -------------------------------------------------------------------------------- 1 | This meeting was cancelled due to lack of agenda 2 | -------------------------------------------------------------------------------- /agendas/2025/08-Aug/14-community-working-group-august-2025.md: -------------------------------------------------------------------------------- 1 | This meeting was cancelled due to lack of agenda 2 | 3 | -------------------------------------------------------------------------------- /assets/twitter-bluesky banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/graphql/community-wg/main/assets/twitter-bluesky banner.png -------------------------------------------------------------------------------- /cheatsheet/graphql-cheatsheet.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/graphql/community-wg/main/cheatsheet/graphql-cheatsheet.pdf -------------------------------------------------------------------------------- /cheatsheet/graphql-cheatsheet.sketch: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/graphql/community-wg/main/cheatsheet/graphql-cheatsheet.sketch -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | *.swp 2 | *~ 3 | .*.haste_cache.* 4 | .DS_Store 5 | npm-debug.log 6 | /build 7 | /public 8 | /gh-pages 9 | /node_modules 10 | yarn.lock 11 | package-lock.json 12 | -------------------------------------------------------------------------------- /.prettierignore: -------------------------------------------------------------------------------- 1 | *.swp 2 | *~ 3 | .*.haste_cache.* 4 | .DS_Store 5 | npm-debug.log 6 | /build 7 | /changelogs 8 | /out 9 | /gh-pages 10 | /node_modules 11 | /package.json 12 | -------------------------------------------------------------------------------- /cspell.yml: -------------------------------------------------------------------------------- 1 | language: en-US 2 | ignoreRegExpList: 3 | # Posessives 4 | - /[a-z]{2,}'s/ 5 | words: 6 | # Terms of art 7 | - endianness 8 | - interoperation 9 | - monospace 10 | - openwebfoundation 11 | - parallelization 12 | - structs 13 | - subselection 14 | # Software 15 | - ical 16 | # Fictional characters / examples 17 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/action-item.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Meeting Action Item 3 | about: Template for action items recommended during subcommittee meetings. 4 | labels: "Action item :clapper:" 5 | --- 6 | 7 | 8 | 9 | - assignee(s): 10 | - source: 11 | 12 | --- 13 | 14 | _Note: Action Item issues are reviewed and closed during Working Group 15 | meetings._ 16 | -------------------------------------------------------------------------------- /cheatsheet/README.md: -------------------------------------------------------------------------------- 1 | # cheatsheets 2 | 3 | A cheat sheet for GraphQL: 4 | 5 | * [pdf](graphql-cheatsheet.pdf) 6 | * [sketch source](graphql-cheatsheet.sketch) 7 | 8 | ## License 9 | 10 | All cheat sheets are licensed as [`CC0`](https://creativecommons.org/public-domain/cc0/). Feel free to share and modify as you see fit. 11 | 12 | ## Contributing 13 | 14 | Contributions are welcome. The files are edited in [Sketch](https://www.sketch.com/). Feel free to modify and open a pull request. If you know of a better tool or workflow for this, please let me know! 15 | 16 | 17 | 18 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "graphql-subcommittee", 3 | "private": true, 4 | "license": "OWFa-1.0", 5 | "scripts": { 6 | "gen-agenda": "wgutils agenda gen", 7 | "test:spellcheck": "cspell \"**/*.md\"", 8 | "format": "prettier --write \"**/*.{md,yml,yaml,json}\"", 9 | "format:check": "prettier --check \"**/*.{md,yml,yaml,json}\"" 10 | }, 11 | "devDependencies": { 12 | "cspell": "5.9.1", 13 | "prettier": "^2.6.2" 14 | }, 15 | "prettier": { 16 | "proseWrap": "always" 17 | }, 18 | "dependencies": { 19 | "wgutils": "^1.3.0" 20 | } 21 | } 22 | -------------------------------------------------------------------------------- /agendas/2025/12-Dec/11-community-working-group-december-2025.md: -------------------------------------------------------------------------------- 1 | | This is an open meeting: To attend, edit and PR this file. (Edit: ✎ above, or press "e") | 2 | | ---------------------------------------------------------------------------------------- | 3 | 4 | # ~~Community Working Group — December 2025~~ CANCELLED 5 | 6 | This meeting was cancelled, the agenda items have been moved to the next meeting. 7 | 8 | - **Date & Time**: ~~[December 11, 2025, 8:00 – 9:00 AM PST](https://www.timeanddate.com/worldclock/converter.html?iso=20251211T160000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240)~~ -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE/agenda-attendance.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Meeting Agenda or Attendance 3 | about: 4 | Template for adding agenda or attendance to an upcoming subcommittee meeting. 5 | labels: "Agenda :hand:" 6 | --- 7 | 8 | 24 | -------------------------------------------------------------------------------- /agendas/README.md: -------------------------------------------------------------------------------- 1 | # Agendas 2 | 3 | An agenda contains details of when a subcommittee meeting occurs, how to access 4 | it, who will be attending and what the topics to be covered are. 5 | 6 | Agendas files are always named in `YYYY-MM-DD.md` format, and should be located 7 | in a folder representing the year. 8 | 9 | To request participation in an upcoming meeting, please send a pull request by 10 | editing the relevant meeting agenda. 11 | 12 | After a meeting, notes should be uploaded to the reciprocal file in 13 | [the notes folder](../notes). 14 | 15 | Meetings are recorded, and they can be viewed on the GraphQL Foundation's 16 | YouTube channel: 17 | 18 | https://www.youtube.com/channel/UCERcwLeheOXp_u61jEXxHMA/videos 19 | 20 | There may or may not be a playlist specifically for this subcommittee; if there 21 | is one it can be found here: 22 | 23 | https://www.youtube.com/channel/UCERcwLeheOXp_u61jEXxHMA/playlists 24 | -------------------------------------------------------------------------------- /rfcs/README.md: -------------------------------------------------------------------------------- 1 | # RFC (request for comments) Working Documents 2 | 3 | The files found here are collaborative notes exploring various proposals for 4 | advancing this subcommittee. Documents included in this directory imply no 5 | specific approval or support nor are any proposals required to create a document 6 | here. 7 | 8 | ## Disclaimers 9 | 10 | - Documents included in this directory imply no specific approval or support for 11 | inclusion in the GraphQL spec or other GraphQL projects. 12 | - Documents here may be historical or out of date. 13 | - An RFC may be active without being documented here; there is no requirement to 14 | add RFCs here. 15 | 16 | ## Contributing 17 | 18 | Pull requests are encouraged. New documents and other non-destructive changes 19 | may be merged with a low degree of scrutiny and minimal review. 20 | 21 | That said, please follow these suggestions: 22 | 23 | - New proposals should be presented in a [working group meeting](../agendas). 24 | Submitting a document here is not sufficient or required to introduce a new 25 | proposal. 26 | - Favor documents which define a problem and explore a solution space rather 27 | than propose a specific change. The intent of documents found here are to help 28 | ask and answer questions to build confidence and advance an RFC. 29 | -------------------------------------------------------------------------------- /notes/2025/summary-2025-03-13.md: -------------------------------------------------------------------------------- 1 | # Meeting Summary for Community WG 2 | 3 | **NOTICE**: This summary was auto-generated by Zoom's "AI". AI-generated 4 | content may be inaccurate or misleading. Always check for accuracy. If in 5 | doubt, please consult the meeting recording at 6 | https://youtube.com/@GraphQLFoundation/playlists 7 | 8 | - Meeting start: 2025-03-13T19:41:06Z 9 | - Meeting end: 2025-03-13T19:43:53Z 10 | - Summary start: 2025-03-13T19:41:52Z 11 | - Summary end: 2025-03-13T19:43:34Z 12 | 13 | Benjie and Jem conducted a meeting to assess the functionality of AI tools, with a focus on the AI companion button and its visibility in the chat. They tested the "raise hand" button and the "react" feature, and confirmed that the AI tools were working as expected. The conversation ended with the understanding that the AI tools were functioning properly. 14 | 15 | ## Next Steps 16 | 17 | _None noted_ 18 | 19 | ## Summary 20 | 21 | ### AI Companion Functionality Assessment Meeting 22 | 23 | Benjie and Jem conducted a quick call to assess the functionality of AI tools. They discussed the presence of an AI companion button and its visibility in the chat. Benjie confirmed that the AI companion was working for them, while Jem had some initial difficulties locating it. They also tested the "raise hand" button and the "react" feature. The conversation ended with the understanding that the AI tools were functioning as expected. 24 | -------------------------------------------------------------------------------- /rfcs/ambassador-program/README.md: -------------------------------------------------------------------------------- 1 | ## Proposed GraphQL Ambassador Program 2 | 3 | This folder contains working documents for the proposed GraphQL Ambassador 4 | Program 5 | 6 | ### Program Aims 7 | 8 | Increase the adoption of GraphQL through brand advocacy, social proof, more 9 | content and learning resources, and greater community visibility; and gain 10 | community feedback on GraphQL initiatives and RFCs 11 | 12 | ### The files in this folder 13 | 14 | - **[Overview for Ambassadors](./overview-for-ambassadors.md)** - an overview of 15 | the proposed GraphQL Ambassador Program for the Ambassadors themselves, this 16 | document will become the basis of the webpage inviting the reader to the 17 | Ambassador application process. 18 | 19 | - **[Overview for Organizers](./overview-for-organizers.md)** - an overview of 20 | the proposed GraphQL Ambassador Program for the organizers (the Foundation, 21 | community working group and other interested parties) outlining the goals, 22 | outcomes and tasks of the program. 23 | 24 | - **[Standards of Excellence](./standards-of-excellence.md)** - the proposed 25 | Standards of Excellence which all Ambassadors will agree to. While the wider 26 | GraphQL community abides by the 27 | [contributor covenant code of conduct](https://graphql.org/codeofconduct/), a 28 | stronger set of standards is used for this program as the Foundation will be 29 | endorsing the Ambassadors as go-to community leaders. 30 | -------------------------------------------------------------------------------- /notes/README.md: -------------------------------------------------------------------------------- 1 | ## Notes for all past subcommittee meetings are kept here. 2 | 3 | Interested in 4 | [taking notes](https://github.com/graphql/graphql-wg#volunteer-to-take-notes) 5 | for a meeting? Sign up for the next session! 6 | 7 | Notes files mirror the file structure of the agendas; namely they should be in 8 | `YYYY/YYYY-MM-DD.md` files to match the date that the meeting took place. 9 | 10 | All notes files should begin with the following format: 11 | 12 | ```md 13 | # GraphQL (NAME) WG Notes - 14 | 15 | **Watch the replay:** 16 | [GraphQL Working Group Meetings on YouTube](https://www.youtube.com/channel/UCERcwLeheOXp_u61jEXxHMA/videos) 17 | 18 | ## Agenda 19 | 20 | 21 | ``` 22 | 23 | When adding notes: use H2 (`##`) to indicate new topics, use bullet points to 24 | track discussion, try and keep track of who said each thing, and keep in mind 25 | this is not a transcription - everything is assumed to be 26 | paraphrased/simplified. When inserting meta-notes (notes on the notes), use 27 | curly braces to avoid conflicts with markdown - e.g. `{inaudible}`, 28 | `{could not keep up with discussion}`, or `{time - 22:03}` 29 | 30 | It's beneficial to insert timestamps periodically throughout the notes as it 31 | allows for easier lookup of the discussion in the video on YouTube. 32 | 33 | Actions should be recorded in the following format: 34 | 35 | ``` 36 | - : **ACTION - **: 37 | ``` 38 | 39 | For example: 40 | 41 | - Lee: **ACTION - Benjie** Write an implementation in GraphQL.js 42 | 43 | Sometimes ACTIONS are inferred rather than explicit, try and write down the 44 | inferred action as best you can - it's okay to omit the speaker, the critical 45 | thing is to have an assignee and a brief description of the assignment. 46 | 47 | Sometimes actions are on everyone; in these cases `**ACTION - everyone**` is 48 | appropriate, but when filing the action item it should be assigned on GitHub to 49 | the champion for that topic. 50 | -------------------------------------------------------------------------------- /.github/workflows/wgutils-automerge.yml: -------------------------------------------------------------------------------- 1 | name: Agenda auto-merge 2 | 3 | on: 4 | pull_request_target: 5 | types: [synchronize, opened, reopened] 6 | 7 | permissions: 8 | contents: write 9 | pull-requests: read 10 | checks: read 11 | 12 | jobs: 13 | validate-and-merge: 14 | if: ${{ github.event.pull_request.base.ref == 'main' }} 15 | runs-on: ubuntu-latest 16 | 17 | steps: 18 | # SECURITY: it's critical we do not check out the source pull request! 19 | - name: Checkout the main branch 20 | uses: actions/checkout@v3 21 | with: 22 | ref: main 23 | 24 | # We need wgutils to be installed 25 | - run: yarn install 26 | 27 | - name: Wait for checks to pass 28 | env: 29 | GH_TOKEN: ${{ github.token }} 30 | run: | 31 | # Give 15 seconds for any checks to register 32 | sleep 15 33 | 34 | # Wait for checks to pass 35 | gh pr checks ${{ github.event.pull_request.number }} --fail-fast --watch --required 2>&1 || true 36 | # Now get the result in JSON 37 | CHECKS_OUTPUT="$(gh pr checks ${{ github.event.pull_request.number }} --required --json bucket --jq 'map(.bucket == "pass") | all' 2>&1 || true)" 38 | 39 | if echo "$CHECKS_OUTPUT" | grep -q "no required checks reported"; then 40 | echo "Not required: $CHECKS_OUTPUT" 41 | elif [[ "$CHECKS_OUTPUT" == "true" ]]; then 42 | echo "$CHECKS_OUTPUT" 43 | else 44 | echo "PR state failed? $CHECKS_OUTPUT" 45 | exit 1 46 | fi 47 | 48 | - name: Automerge if wgutils approves 49 | env: 50 | GH_TOKEN: ${{ github.token }} 51 | run: | 52 | if yarn wgutils can-automerge "${{ github.event.pull_request.number }}" "${{ github.event.pull_request.head.sha }}"; then 53 | gh pr merge "${{ github.event.pull_request.number }}" --squash --auto --match-head-commit "${{ github.event.pull_request.head.sha }}" 54 | fi 55 | -------------------------------------------------------------------------------- /social-media/social-media-guide.md: -------------------------------------------------------------------------------- 1 | # GraphQL Social Media 2 | 3 | GraphQL is present on: 4 | 5 | - [Twitter](https://twitter.com/graphql) 6 | - [BlueSky](https://bsky.app/profile/graphql.org) 7 | - [LinkedIn](https://www.linkedin.com/company/graphql-foundation/) 8 | - [YouTube](https://www.youtube.com/@GraphQLTV) 9 | 10 | The community manages the publications through [Typefully](https://typefully.com/) (with a current experimentation with [Buffer](https://buffer.com/)). 11 | 12 | ## Contributing 13 | 14 | If you want to contribute content, please feel free to share ideas and links in the `#community-wg` channel on the [GraphQL Community Discord](https://discord.graphql.org), or the `#social-media` Slack channel. (The Discord is free to join. To join the Slack channel you must have a paid subscription to Slack, then you can be invited via Slack Connect - please open an issue in this repo and we'll request the relevant details to invite you.) 15 | 16 | If you'd like to help draft content for Bluesky, LinkedIn or Twitter/X, please sign up at Typefully.com and request an invite to the GraphQL Foundation's Typefully account via operations at graphql dot org. 17 | 18 | ## Posting frequency 19 | 20 | There are 4 posting slots every day, 2 for US times, 2 for EU times, based on what we found worked best. Avoid Fridays if possible as the engagement is lower. 21 | 22 | We generally aim to do 3-5 posts/channel/week to keep our audience engaged while not spamming it. That's roughly one post every week day. 23 | 24 | ## Tone of voice 25 | 26 | Our main goal is to create discussions about the GraphQL language and connect users, contributors and the community at large. 27 | 28 | Hot takes are allowed, but trolling and clickbait content are discouraged. 29 | 30 | Boosting other community members' posts or content is encouraged as that increases the network effect. That said, no community member or vendor should receive disproportionate attention; the GraphQL Foundation is a vendor neutral organization and endeavors to promote different organizations and individuals fairly. 31 | 32 | ## Example content 33 | 34 | - New releases: "graphql-js 17 is out with fragment arguments, try it out!" 35 | - Poll: "What GraphQL client are you using?" 36 | - Event: "Grab your ticket for GraphQLConf!" 37 | - Community blog post: "Read from Benjie about error handling in GraphQL." 38 | - etc... 39 | -------------------------------------------------------------------------------- /agendas/2025/07-Jul/10-community-working-group-july-2025.md: -------------------------------------------------------------------------------- 1 | | This is an open meeting: To attend, edit and PR this file. (Edit: ✎ above, or press "e") | 2 | | ---------------------------------------------------------------------------------------- | 3 | 4 | # Community Working Group — July 2025 5 | 6 | - **Date & Time**: [July 10, 2025, 8:00 – 9:00 AM PDT](https://www.timeanddate.com/worldclock/converter.html?iso=20250710T150000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240) 7 | - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]). 8 | - _Please Note:_ The date or time may change. Please check this agenda the 9 | week of the meeting to confirm. While we try to keep all calendars accurate, 10 | this agenda document is the source of truth. 11 | - **Video Conference Link**: https://zoom.us/j/93104287544 12 | - _Password:_ community 13 | - **Live Notes**: [Live Notes][] 14 | 15 | [calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com 16 | [google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t 17 | [ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics 18 | [live notes]: https://docs.google.com/document/d/1Rc7Lku5rQlqFu65PosBXSWWrPXw5zQmYWVWjiTg0qZA/edit?usp=sharing 19 | 20 | ## Attendees 21 | 22 | 23 | | Name | GitHub | Organization | Location | 24 | | :--------------- | :------------ | :----------------- | :-------------------- | 25 | 26 | 27 | ## Agenda 28 | 29 | 1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host) 30 | - [Specification Membership Agreement](https://github.com/graphql/foundation) 31 | - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines) 32 | - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md) 33 | - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md) 34 | - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools 35 | 1. Introduction of attendees (5m, Host) 36 | 1. Determine volunteers for note taking (1m, Host) 37 | 1. Review agenda (2m, Host) 38 | 1. Check for [ready for review agenda items](https://github.com/graphql/community-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host) 39 | -------------------------------------------------------------------------------- /agendas/2026/01-Jan/08-community-working-group-january-2026.md: -------------------------------------------------------------------------------- 1 | | This is an open meeting: To attend, edit and PR this file. (Edit: ✎ above, or press "e") | 2 | | ---------------------------------------------------------------------------------------- | 3 | 4 | # Community Working Group — January 2026 5 | 6 | - **Date & Time**: [January 8, 2026, 8:00 – 9:00 AM PST](https://www.timeanddate.com/worldclock/converter.html?iso=20260108T160000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240) 7 | - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]). 8 | - _Please Note:_ The date or time may change. Please check this agenda the 9 | week of the meeting to confirm. While we try to keep all calendars accurate, 10 | this agenda document is the source of truth. 11 | - **Video Conference Link**: https://zoom.us/j/93104287544 12 | - _Password:_ community 13 | - **Live Notes**: [Live Notes][] 14 | 15 | [calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com 16 | [google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t 17 | [ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics 18 | [live notes]: https://docs.google.com/document/d/1Rc7Lku5rQlqFu65PosBXSWWrPXw5zQmYWVWjiTg0qZA/edit?usp=sharing 19 | 20 | ## Attendees 21 | 22 | 23 | | Name | GitHub | Organization | Location | 24 | | :--------------- | :------------ | :----------------- | :-------------------- | 25 | 26 | 27 | ## Agenda 28 | 29 | 1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host) 30 | - [Specification Membership Agreement](https://github.com/graphql/foundation) 31 | - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines) 32 | - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md) 33 | - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md) 34 | - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools 35 | 1. Introduction of attendees (5m, Host) 36 | 1. Determine volunteers for note taking (1m, Host) 37 | 1. Review agenda (2m, Host) 38 | 1. Check for [ready for review agenda items](https://github.com/graphql/community-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host) 39 | -------------------------------------------------------------------------------- /agendas/2026/03-Mar/12-community-working-group-march-2026.md: -------------------------------------------------------------------------------- 1 | | This is an open meeting: To attend, edit and PR this file. (Edit: ✎ above, or press "e") | 2 | | ---------------------------------------------------------------------------------------- | 3 | 4 | # Community Working Group — March 2026 5 | 6 | - **Date & Time**: [March 12, 2026, 8:00 – 9:00 AM PDT](https://www.timeanddate.com/worldclock/converter.html?iso=20260312T150000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240) 7 | - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]). 8 | - _Please Note:_ The date or time may change. Please check this agenda the 9 | week of the meeting to confirm. While we try to keep all calendars accurate, 10 | this agenda document is the source of truth. 11 | - **Video Conference Link**: https://zoom.us/j/93104287544 12 | - _Password:_ community 13 | - **Live Notes**: [Live Notes][] 14 | 15 | [calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com 16 | [google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t 17 | [ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics 18 | [live notes]: https://docs.google.com/document/d/1Rc7Lku5rQlqFu65PosBXSWWrPXw5zQmYWVWjiTg0qZA/edit?usp=sharing 19 | 20 | ## Attendees 21 | 22 | 23 | | Name | GitHub | Organization | Location | 24 | | :--------------- | :------------ | :----------------- | :-------------------- | 25 | 26 | 27 | ## Agenda 28 | 29 | 1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host) 30 | - [Specification Membership Agreement](https://github.com/graphql/foundation) 31 | - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines) 32 | - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md) 33 | - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md) 34 | - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools 35 | 1. Introduction of attendees (5m, Host) 36 | 1. Determine volunteers for note taking (1m, Host) 37 | 1. Review agenda (2m, Host) 38 | 1. Check for [ready for review agenda items](https://github.com/graphql/community-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host) 39 | 1. Reminder: [grants available for key initiatives](https://graphql.org/community/foundation/community-grant/) (1m, Host) 40 | -------------------------------------------------------------------------------- /agendas/2026/02-Feb/12-community-working-group-february-2026.md: -------------------------------------------------------------------------------- 1 | | This is an open meeting: To attend, edit and PR this file. (Edit: ✎ above, or press "e") | 2 | | ---------------------------------------------------------------------------------------- | 3 | 4 | # Community Working Group — February 2026 5 | 6 | - **Date & Time**: [February 12, 2026, 8:00 – 9:00 AM PST](https://www.timeanddate.com/worldclock/converter.html?iso=20260212T160000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240) 7 | - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]). 8 | - _Please Note:_ The date or time may change. Please check this agenda the 9 | week of the meeting to confirm. While we try to keep all calendars accurate, 10 | this agenda document is the source of truth. 11 | - **Video Conference Link**: https://zoom.us/j/93104287544 12 | - _Password:_ community 13 | - **Live Notes**: [Live Notes][] 14 | 15 | [calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com 16 | [google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t 17 | [ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics 18 | [live notes]: https://docs.google.com/document/d/1Rc7Lku5rQlqFu65PosBXSWWrPXw5zQmYWVWjiTg0qZA/edit?usp=sharing 19 | 20 | ## Attendees 21 | 22 | 23 | | Name | GitHub | Organization | Location | 24 | | :--------------- | :------------ | :----------------- | :-------------------- | 25 | 26 | 27 | ## Agenda 28 | 29 | 1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host) 30 | - [Specification Membership Agreement](https://github.com/graphql/foundation) 31 | - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines) 32 | - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md) 33 | - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md) 34 | - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools 35 | 1. Introduction of attendees (5m, Host) 36 | 1. Determine volunteers for note taking (1m, Host) 37 | 1. Review agenda (2m, Host) 38 | 1. Check for [ready for review agenda items](https://github.com/graphql/community-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host) 39 | 1. Reminder: [grants available for key initiatives](https://graphql.org/community/foundation/community-grant/) (1m, Host) 40 | -------------------------------------------------------------------------------- /agendas/2025/11-Nov/13-community-working-group-november-2025.md: -------------------------------------------------------------------------------- 1 | | This is an open meeting: To attend, edit and PR this file. (Edit: ✎ above, or press "e") | 2 | | ---------------------------------------------------------------------------------------- | 3 | 4 | # Community Working Group — November 2025 5 | 6 | - **Date & Time**: [November 13, 2025, 8:00 – 9:00 AM PST](https://www.timeanddate.com/worldclock/converter.html?iso=20251113T160000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240) 7 | - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]). 8 | - _Please Note:_ The date or time may change. Please check this agenda the 9 | week of the meeting to confirm. While we try to keep all calendars accurate, 10 | this agenda document is the source of truth. 11 | - **Video Conference Link**: https://zoom.us/j/93104287544 12 | - _Password:_ community 13 | - **Live Notes**: [Live Notes][] 14 | 15 | [calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com 16 | [google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t 17 | [ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics 18 | [live notes]: https://docs.google.com/document/d/1Rc7Lku5rQlqFu65PosBXSWWrPXw5zQmYWVWjiTg0qZA/edit?usp=sharing 19 | 20 | ## Attendees 21 | 22 | 23 | | Name | GitHub | Organization | Location | 24 | | :--------------- | :------------ | :----------------- | :-------------------- | 25 | | Martin Bonnin | @martinbonnin | Apollo | Paris, FR | 26 | 27 | 28 | ## Agenda 29 | 30 | 1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host) 31 | - [Specification Membership Agreement](https://github.com/graphql/foundation) 32 | - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines) 33 | - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md) 34 | - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md) 35 | - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools 36 | 1. Introduction of attendees (5m, Host) 37 | 1. Determine volunteers for note taking (1m, Host) 38 | 1. Review agenda (2m, Host) 39 | 1. Check for [ready for review agenda items](https://github.com/graphql/community-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host) 40 | 1. Reminder: [grants available for key initiatives](https://graphql.org/community/foundation/community-grant/) (1m, Host) 41 | 1. apidays NYC (5min, Martin) 42 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/event-submission.yml: -------------------------------------------------------------------------------- 1 | name: Event submission 2 | description: Share a meetup or conference with the GraphQL community 3 | title: "Event submission: " 4 | labels: 5 | - event 6 | assignees: 7 | - jemgillam 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: > 12 | Share your upcoming GraphQL gathering. 13 | These details will be displayed on the Events & Meetups page so more people can find you. 14 | - type: dropdown 15 | id: event_type 16 | attributes: 17 | label: What kind of gathering is it? 18 | options: 19 | - Meetup 20 | - Conference 21 | validations: 22 | required: true 23 | - type: input 24 | id: event_name 25 | attributes: 26 | label: Event name 27 | placeholder: GraphQL YOUR_CITY_HERE 28 | validations: 29 | required: true 30 | - type: textarea 31 | id: event_summary 32 | attributes: 33 | label: What should people expect? 34 | placeholder: A full day of GraphQL deep dives and hallway conversations in Amsterdam. 35 | - type: input 36 | id: event_start 37 | attributes: 38 | label: Start date and time 39 | description: Include the timezone or UTC offset, for example 2025-09-08 09:00 CEST. 40 | placeholder: 2026-01-01 00:00 UTC 41 | validations: 42 | required: true 43 | - type: input 44 | id: event_end 45 | attributes: 46 | label: End date or final session time 47 | description: Useful for multi-day conferences or evening meetups with an end time. 48 | placeholder: 2026-01-01 23:59 UTC 49 | - type: input 50 | id: location 51 | attributes: 52 | label: City and country (or Online) 53 | placeholder: YOUR_CITY, YOUR_COUNTRY 54 | validations: 55 | required: true 56 | - type: input 57 | id: venue 58 | attributes: 59 | label: Venue or neighborhood 60 | description: Optional context that helps locals plan their trip. 61 | placeholder: VENUE INSTRUCTIONS 62 | - type: input 63 | id: event_link 64 | attributes: 65 | label: Primary event or registration link 66 | placeholder: https:// 67 | validations: 68 | required: true 69 | - type: input 70 | id: host_name 71 | attributes: 72 | label: Host organization or meetup group 73 | placeholder: YOUR_MEETUP_GROUP_OR_ORGANIZATION 74 | validations: 75 | required: true 76 | - type: input 77 | id: host_link 78 | attributes: 79 | label: Host link 80 | description: Website, meetup page, or social profile. 81 | placeholder: https:// 82 | - type: input 83 | id: contact 84 | attributes: 85 | label: Contact email or Discord username 86 | placeholder: john.doe@example.com 87 | - type: textarea 88 | id: extras 89 | attributes: 90 | label: Anything else we should know? 91 | description: CFP deadlines, sponsors, accessibility notes, or other context. 92 | -------------------------------------------------------------------------------- /agendas/2025/10-Oct/09-community-working-group-october-2025.md: -------------------------------------------------------------------------------- 1 | | This is an open meeting: To attend, edit and PR this file. (Edit: ✎ above, or press "e") | 2 | | ---------------------------------------------------------------------------------------- | 3 | 4 | # Community Working Group — October 2025 5 | 6 | - **Date & Time**: [October 9, 2025, 8:00 – 9:00 AM PDT](https://www.timeanddate.com/worldclock/converter.html?iso=20251009T150000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240) 7 | - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]). 8 | - _Please Note:_ The date or time may change. Please check this agenda the 9 | week of the meeting to confirm. While we try to keep all calendars accurate, 10 | this agenda document is the source of truth. 11 | - **Video Conference Link**: https://zoom.us/j/93104287544 12 | - _Password:_ community 13 | - **Live Notes**: [Live Notes][] 14 | 15 | [calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com 16 | [google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t 17 | [ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics 18 | [live notes]: https://docs.google.com/document/d/1Rc7Lku5rQlqFu65PosBXSWWrPXw5zQmYWVWjiTg0qZA/edit?usp=sharing 19 | 20 | ## Attendees 21 | 22 | 23 | | Name | GitHub | Organization | Location | 24 | | :--------------- | :------------ | :----------------- | :-------------------- | 25 | | Jem Gillam | @jemgillam | Graphile | Chandlers Ford, UK | 26 | | Martin Bonnin | @martinbonnin | Apollo | Paris, FR | 27 | | Benjie Gillam | @benjie | Graphile | Chandlers Ford, UK | 28 | 29 | 30 | ## Agenda 31 | 32 | 1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host) 33 | - [Specification Membership Agreement](https://github.com/graphql/foundation) 34 | - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines) 35 | - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md) 36 | - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md) 37 | - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools 38 | 1. Introduction of attendees (5m, Host) 39 | 1. Determine volunteers for note taking (1m, Host) 40 | 1. Review agenda (2m, Host) 41 | 1. Check for [ready for review agenda items](https://github.com/graphql/community-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host) 42 | 1. Reminder: [grants available for key initiatives](https://graphql.org/community/foundation/community-grant/) (1m, Host) 43 | 1. Update on apidays Paris (5min, Martin) 44 | 1. Removing the CLA for community contributions (5min, Martin) 45 | -------------------------------------------------------------------------------- /agendas/2025/09-Sep/25-community-working-group-september-2025.md: -------------------------------------------------------------------------------- 1 | 2 | | This is an open meeting: To attend, edit and PR this file. (Edit: ✎ above, or press "e") | 3 | | ---------------------------------------------------------------------------------------- | 4 | 5 | # Community Working Group — September 2025 6 | 7 | - **Date & Time**: [September 25, 2025, 7:00 – 8:00 AM PDT](https://www.timeanddate.com/worldclock/converter.html?iso=20250925T140000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240) 8 | - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]). 9 | - _Please Note:_ The date or time may change. Please check this agenda the 10 | week of the meeting to confirm. While we try to keep all calendars accurate, 11 | this agenda document is the source of truth. 12 | - **Video Conference Link**: https://zoom.us/j/93104287544 13 | - _Password:_ community 14 | - **Live Notes**: [Live Notes][] 15 | 16 | [calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com 17 | [google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t 18 | [ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics 19 | [live notes]: https://docs.google.com/document/d/1Rc7Lku5rQlqFu65PosBXSWWrPXw5zQmYWVWjiTg0qZA/edit?usp=sharing 20 | 21 | ## Attendees 22 | 23 | 24 | | Name | GitHub | Organization | Location | 25 | |:----------------|:---------------|:---------------|:---------| 26 | | Jonathan Rainer | jonathanrainer | Apollo GraphQL | York, UK | 27 | | Martin Bonnin | martinbonnin | Apollo GraphQL | Paris, FR | 28 | | Jem Gillam | jemgillam | Graphile | Chandler's Ford, UK | 29 | | Benjie Gillam | benjie | Graphile | Chandler's Ford, UK | 30 | | Vanessa Johnson | @vanessamj99 | The New York Times | New York City, NY, US | 31 | | Jeff Auriemma | @bignimbus | Apollo GraphQL | Monroe, CT, US | 32 | | Uri Goldshtein | @urigo | The Guild | Tel Aviv, IL | 33 | 34 | ## Agenda 35 | 36 | 1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host) 37 | - [Specification Membership Agreement](https://github.com/graphql/foundation) 38 | - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines) 39 | - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md) 40 | - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md) 41 | - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools 42 | 1. Introduction of attendees (5m, Host) 43 | 1. Determine volunteers for note taking (1m, Host) 44 | 1. Review agenda (2m, Host) 45 | 1. Check for [ready for review agenda items](https://github.com/graphql/community-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host) 46 | 1. GraphQL day at apidays Paris 2025 (Martin) 47 | 1. https://graphql.day/ 48 | 1. CFP closes Oct 12th! 49 | 1. GraphQL at FOSDEM 2026 (10m, Jem) 50 | 1. GraphQL Ambassadors update (5m, Jem) 51 | 1. GSoC 2026 Participation Idea 52 | -------------------------------------------------------------------------------- /agendas/2025/12-Dec/18-community-working-group-december-2025.md: -------------------------------------------------------------------------------- 1 | | This is an open meeting: To attend, edit and PR this file. (Edit: ✎ above, or press "e") | 2 | | ---------------------------------------------------------------------------------------- | 3 | 4 | # Community Working Group — December 2025 5 | 6 | - **Date & Time**: [December 18, 2025, 8:00 – 9:00 AM PST](https://www.timeanddate.com/worldclock/converter.html?iso=20251218T150000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240) 7 | - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]). 8 | - _Please Note:_ The date or time may change. Please check this agenda the 9 | week of the meeting to confirm. While we try to keep all calendars accurate, 10 | this agenda document is the source of truth. 11 | - **Video Conference Link**: https://zoom.us/j/93104287544 12 | - _Password:_ community 13 | - **Live Notes**: [Live Notes][] 14 | 15 | [calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com 16 | [google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t 17 | [ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics 18 | [live notes]: https://docs.google.com/document/d/1Rc7Lku5rQlqFu65PosBXSWWrPXw5zQmYWVWjiTg0qZA/edit?usp=sharing 19 | 20 | ## Attendees 21 | 22 | 23 | | Name | GitHub | Organization | Location | 24 | |:--------------|:-------------|:-------------|:----------| 25 | | Martin Bonnin | @martinbonnin | Apollo | Paris, FR | 26 | | Stefan Avram | - | WunderGraph | Miami, US | 27 | | Dev Parsons | - | WunderGraph | Saint Petersburgh, US | 28 | | Viola Marku | - | WunderGraph | London, UK | 29 | | Piotr Monwid-Olechnowicz | haspaus | The Guild | Wrocław, PL | 30 | | Michael Staib | @michaelstaib | ChilliCream | Zurich, CH | 31 | | Pascal Senn | @pascalsenn | ChilliCream | Zurich, CH | 32 | | Jem Gillam | @jemgillam | Graphile | Chandlers Ford, UK | 33 | 34 | 35 | ## Agenda 36 | 37 | 1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host) 38 | - [Specification Membership Agreement](https://github.com/graphql/foundation) 39 | - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines) 40 | - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md) 41 | - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md) 42 | - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools 43 | 1. Introduction of attendees (5m, Host) 44 | 1. Determine volunteers for note taking (1m, Host) 45 | 1. Review agenda (2m, Host) 46 | 1. Check for [ready for review agenda items](https://github.com/graphql/community-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host) 47 | 1. Reminder: [grants available for key initiatives](https://graphql.org/community/foundation/community-grant/) (1m, Host) 48 | 1. Social media guide (2m, Martin) 49 | - https://github.com/graphql/community-wg/pull/137 50 | 1. Feedbacks from GraphQL Day Paris (10m, Martin) 51 | 1. New GraphQL.org [Resource Hub page](https://fabulous-isomorphism-git-resources-hub-hasparus-projects.vercel.app/resources/) (10m, Piotr) 52 | -------------------------------------------------------------------------------- /notes/2025/2025-06.md: -------------------------------------------------------------------------------- 1 | # Community WG Notes - June 2025 2 | 3 | **Watch the replays:** 4 | [GraphQL Working Group Meetings on YouTube](https://www.youtube.com/playlist?list=PLP1igyLx8foHhWZk2u1SthsW1weH3VA7l) 5 | 6 | Agenda: 7 | 8 | [https://github.com/graphql/community-wg/blob/main/agendas/2025/06-Jun/12-community-working-group-june-2025.md](https://github.com/graphql/community-wg/blob/main/agendas/2025/06-Jun/12-community-working-group-june-2025.md) 9 | 10 | ## Attendees 11 | 12 | - Uri 13 | - Martin 14 | - Jem 15 | - Benjie 16 | - Erik 17 | 18 | ## Review agenda 19 | 20 | - AI notes: working well, some autocorrections needed. 21 | - AI in zoom: great way to catch up with missed parts (especially when joining 22 | late). 23 | - Main focus today is the Ambassador program. 24 | 25 | ## Ambassador Program 26 | 27 | - RFC was opened in April. 28 | - How do we get this launched? 29 | - Plan: present what we've written to the foundation. 30 | - You're all highly engaged: 31 | 1. Are we missing anything from the program that you'd want as an ambassador? 32 | 2. What groups of people should we be asking to join? 33 | - Who should be our first set of ambassadors? 34 | - Erik: happy with what we have, doesn't feel like anything is missing. 35 | - Jem: main selling points are 15m quarterly meeting with foundation reps 36 | - Uri: excited about this! Very well thought out. Feels ready to show the 37 | foundation. Would be great to launch at GraphQLConf. 38 | - Jem: ideally we want to launch there; either opening applications there, or if 39 | we can do it in time - announcing the first few ambassadors! 40 | - Uri: I've sent a few names through 41 | - Jem: we've collected a few names too. Regular WG members, speakers at various 42 | conferences, people running meetups. Another idea: OSS maintainers of critical 43 | tooling/implementations. 44 | - How does the application process work? 45 | - Application email goes to TSC and Foundation members. Someone should say yes. 46 | Any objections would need to be investigated. 47 | - Erik: We should make it really encouraging. Wait times can be discouraging. 48 | Respond rapidly, notify of review period later. 49 | - Should Community WG be involved in reviewing applications? 50 | - Shouldn't be public. Maybe mailinglist? 51 | - Maybe via the community leaders channel. 52 | - Not sure what the process of other foundations are, but seem to be internal. 53 | - Nominations **and** applications? 54 | - Need a GraphQL Ambassador t-shirt. 55 | - Martin: Would rather have a small set of engaged ambassadors. 56 | - Uri: Don't need a cap, but we should focus on engaged people. Also make sure 57 | that people are finding it useful. Google has a page for GDEs, there's tonnes 58 | of them, but it's helpful. You can see who's local, and contact them. 59 | - **A couple of local experts in each city would be ideal.** 60 | - There's a lot of opportunities for GraphQL Experts! 61 | - Erik: is the goal to send more people to conferences? Or to send to local 62 | communities and be in every firm? We should focus on the former as it's easier 63 | to target, smaller and more focussed; but expand to the latter later. 64 | - Jem: ideally I'd like to have a first cohort to announce at GraphQLConf. We'll 65 | raise this at the foundation, prepare an article to launch the program, and 66 | keep the issue updated. 67 | 68 | ## GraphQL.org design 69 | 70 | - [https://github.com/graphql/community-wg/issues/21](https://github.com/graphql/community-wg/issues/21) 71 | - Conf website is up based on the new design! 72 | -------------------------------------------------------------------------------- /agendas/2025/06-Jun/12-community-working-group-june-2025.md: -------------------------------------------------------------------------------- 1 | | This is an open meeting: To attend, edit and PR this file. (Edit: ✎ above, or press "e") | 2 | | ---------------------------------------------------------------------------------------- | 3 | 4 | # Community Working Group — June 2025 5 | 6 | - **Date & Time**: [June 12, 2025, 8:00 – 9:00 AM PDT](https://www.timeanddate.com/worldclock/converter.html?iso=20250612T150000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240) 7 | - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]). 8 | - _Please Note:_ The date or time may change. Please check this agenda the 9 | week of the meeting to confirm. While we try to keep all calendars accurate, 10 | this agenda document is the source of truth. 11 | - **Video Conference Link**: https://zoom.us/j/93104287544 12 | - _Password:_ community 13 | - **Live Notes**: [Live Notes][] 14 | 15 | [calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com 16 | [google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t 17 | [ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics 18 | [live notes]: https://docs.google.com/document/d/1Rc7Lku5rQlqFu65PosBXSWWrPXw5zQmYWVWjiTg0qZA/edit?usp=sharing 19 | 20 | ## Attendees 21 | 22 | 23 | | Name | GitHub | Organization | Location | 24 | | :--------------- | :------------ | :----------------- | :-------------------- | 25 | | Jem G | @jemgillam | Graphile | Chandlers Ford, UK | 26 | | Erik | @erikwrede | Self | Germany | 27 | | Benjie Gillam | @benjie | Graphile | Chandler's Ford, UK | 28 | | Uri Goldshtein | @urigo | The Guild | Tel Aviv, IL | 29 | | Martin Bonnin | @martinbonnin | Apollo | Paris, FR | 30 | 31 | ## Agenda 32 | 33 | 1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host) 34 | - [Specification Membership Agreement](https://github.com/graphql/foundation) 35 | - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines) 36 | - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md) 37 | - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md) 38 | - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools 39 | 1. Introduction of attendees (5m, Host) 40 | 1. Determine volunteers for note taking (1m, Host) 41 | 1. Review agenda (2m, Host) 42 | 1. Check for [ready for review agenda items](https://github.com/graphql/community-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) (5m, Host) 43 | 1. Guidance sought: What are the next steps to launch the Ambassadors Program? (15m, Jem) 44 | 1. Latest updates on the new graphql.org design and GraphQL Conf website (10m, Uri) 45 | 1. 2025 designs: [GraphQL stars](https://github.com/graphql/community-wg/issues/82) and [slide deck](https://github.com/graphql/community-wg/issues/67) (10m, Benjie) 46 | 1. Some callouts for feedback (graphql-js docs, AI content, GraphiQL latest versions) (5m, Uri) 47 | 1. Thoughts about collaborating with API Days Paris (10m, Uri) 48 | -------------------------------------------------------------------------------- /agendas/2025/04-Apr/10-community-working-group-april-2025.md: -------------------------------------------------------------------------------- 1 | | This is an open meeting: To attend, edit and PR this file. (Edit: ✎ above, or press "e") | 2 | | ---------------------------------------------------------------------------------------- | 3 | 4 | # Community Working Group — April 2025 5 | 6 | - **Date & Time**: [April 10, 2025, 8:00 – 9:00 AM PDT](https://www.timeanddate.com/worldclock/converter.html?iso=20250410T150000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240) 7 | - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]). 8 | - _Please Note:_ The date or time may change. Please check this agenda the 9 | week of the meeting to confirm. While we try to keep all calendars accurate, 10 | this agenda document is the source of truth. 11 | - **Video Conference Link**: https://zoom.us/j/93104287544 12 | - _Password:_ community 13 | - **Live Notes**: [Live Notes][] 14 | 15 | [calendar]: https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com 16 | [google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t 17 | [ical file]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics 18 | [live notes]: https://docs.google.com/document/d/1Rc7Lku5rQlqFu65PosBXSWWrPXw5zQmYWVWjiTg0qZA/edit?usp=sharing 19 | 20 | ## Attendees 21 | 22 | 23 | | Name | GitHub | Organization | Location | 24 | | :--------------- | :------------ | :----------------- | :-------------------- | 25 | | Lavan J V | @jvlavan | Self | Chennai, IN | 26 | | Doc Jones | @doc-jones | Cyberspace | Raleigh, NC, USA | 27 | | Jem Gillam | @jemgillam | Graphile | Chandler's Ford, UK | 28 | | Uri Goldshtein | @urigo | The Guild | Tel Aviv, IL | 29 | | Saihajpreet Singh | @saihaj | The Guild | India | 30 | | Benjie | @benjie | Graphile | Chandler's Ford, UK | 31 | | Jeff Auriemma | @bignimbus | Apollo | Monroe, CT, USA | 32 | 33 | 34 | ## Agenda 35 | 36 | 1. Introductions (All) 37 | 1. Agree to Membership Agreement, Participation & Contribution Guidelines and Code of Conduct (1m, Host) 38 | - [Specification Membership Agreement](https://github.com/graphql/foundation) 39 | - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines) 40 | - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md) 41 | - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md) 42 | - Meetings are [published to YouTube](https://www.youtube.com/@GraphQLFoundation/videos) and we may use LLM/AI summary tools 43 | 1. Introduction of attendees (5m, Host) 44 | 1. Determine volunteers for note taking (1m, Host) 45 | 1. Review agenda (2m, Host) 46 | 1. Check for [ready for review agenda items](https://github.com/graphql/community-wg/issues?q=is:issue%20is:open%20label:%22Ready%20for%20review%22%20sort:updated-desc%20) (5m, Host) 47 | 1. "Empowering the community" defined (Uri - 5 mins) requested by Doc 48 | 1. Survey (Doc and Martin) 49 | 1. Update for [issue 22](https://github.com/graphql/community-wg/issues/22) (Jem - 5 mins) 50 | 1. Calls for comments on the Ambassador scheme [PR 64](https://github.com/graphql/community-wg/pull/64) [issue 1](https://github.com/graphql/community-wg/issues/1) (Jem - 10 mins?) 51 | 1. Short update on the [new graphql.org design initative](https://github.com/graphql/community-wg/issues/21) (Uri - 10 mins) 52 | -------------------------------------------------------------------------------- /agendas/2025/02-Feb/13-community-working-group-february-2025.md: -------------------------------------------------------------------------------- 1 | | This is an open meeting: To attend, edit and PR this file. (Edit: ✎ above, or press "e") | 2 | | ---------------------------------------------------------------------------------------- | 3 | 4 | # Community Working Group — February 2025 5 | 6 | - **Date & Time**: 7 | [February 13, 2025, 8:00 – 9:00 AM PST](https://www.timeanddate.com/worldclock/converter.html?iso=20250213T160000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240) 8 | - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]). 9 | - _Please Note:_ The date or time may change. Please check this agenda the 10 | week of the meeting to confirm. While we try to keep all calendars accurate, 11 | this agenda document is the source of truth. 12 | - **Video Conference Link**: https://zoom.us/j/93104287544 13 | - _Password:_ community 14 | - **Live Notes**: [Live Notes][] 15 | 16 | [calendar]: 17 | https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com 18 | [google calendar]: 19 | https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t 20 | [ical file]: 21 | https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics 22 | [live notes]: 23 | https://docs.google.com/document/d/1Rc7Lku5rQlqFu65PosBXSWWrPXw5zQmYWVWjiTg0qZA/edit?usp=sharing 24 | 25 | ## Attendees 26 | 27 | 28 | | Name | GitHub | Organization | Location | 29 | | :----------------- | :------------ | :----------------- | :-------------------- | 30 | | Saihajpreet Singh | @saihaj | The Guild | India | 31 | | Benjie Gillam | @benjie | Graphile | Chandler's Ford, UK | 32 | | Uri Goldshtein | @urigo | The Guild | Tel Aviv, IL | 33 | | Martin Bonnin | @martinbonnin | Apollo | Paris, FR | 34 | | Jem Gillam | @jemgillam | Graphile | Chandler's Ford, UK | 35 | | Jeff Auriemma | @bignimbus | Apollo | Monroe, CT, USA | 36 | | Michael Staib | @michaelstaib | ChilliCream | Zurich, CH | 37 | | Pascal Senn | @pascalsenn | ChilliCream | Zurich, CH | 38 | | Erik Wrede | @erikwrede | Strawberry | Aachen, DE | 39 | | Doc Jones | @doc-jones | TBD | Raleigh, NC, USA | 40 | | Robert Balicki | @rbalicki2 | Pinterest | New York, NY, USA | 41 | 42 | ## Agenda 43 | 44 | 1. Agree to Membership Agreement, Participation & Contribution Guidelines and 45 | Code of Conduct (1m, Host) 46 | - [Specification Membership Agreement](https://github.com/graphql/foundation) 47 | - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines) 48 | - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md) 49 | - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md) 50 | 1. Introduction of attendees (5m, Host) 51 | 1. Determine volunteers for note taking (1m, Host) 52 | 1. Review agenda (2m, Host) 53 | 1. Check for 54 | [ready for review agenda items](https://github.com/graphql/community-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) 55 | (5m, Host) 56 | 1. Discussing goals for the working group (15m, All) 57 | 1. Roadmap for the working group (15m, All) 58 | 1. Meeting cadence (5m, All) 59 | -------------------------------------------------------------------------------- /notes/2025/summary-2025-10-09.md: -------------------------------------------------------------------------------- 1 | # Meeting Summary for Community WG 2 | 3 | **NOTICE**: This summary was auto-generated by Zoom's "AI". AI-generated 4 | content may be inaccurate or misleading. Always check for accuracy. If in 5 | doubt, please consult the meeting recording at 6 | https://youtube.com/@GraphQLFoundation/playlists 7 | 8 | - Meeting start: 2025-10-09T14:59:32Z 9 | - Meeting end: 2025-10-09T15:22:09Z 10 | - Summary start: 2025-10-09T15:01:23Z 11 | - Summary end: 2025-10-09T15:22:08Z 12 | 13 | The meeting covered discussions about community contribution requirements, with a focus on whether to remove the CLA for certain working groups and the need to consult with the Foundation Board and technical steering committee. The team reviewed website improvements for new contributors and discussed plans for upcoming events including API Days Paris and FOSDEM 2025, with specific attention to gathering talk proposals and managing sponsorships. Various administrative matters were addressed, including CLA bot deployment issues and website updates related to TSC member access and video requirements. 14 | 15 | ## Next Steps 16 | 17 | - Martin to ask Jeff about bringing up the CLA removal for community working group to the next board meeting. 18 | - Martin to check the GraphQL All Hands video for the list of board representatives. 19 | - Martin to meet with API Days Paris organizers to fix the CFP submission process. 20 | - Martin to create a GitHub issue on community working group repo about API Days Paris CFP. 21 | - Jem to finalize the pull request for the website guide on joining working groups. 22 | - Benjie to check if TSC members can be added to the Ambassador mailing list. 23 | - Benjie to get approval from the Conference Committee for the website update regarding meetup admin group and video requirements. 24 | 25 | ## Summary 26 | 27 | ### CLA Removal and API Days Paris 28 | 29 | The meeting focused on two main agenda items: API Days Paris and removing the CLA for community contributions. Martin proposed removing the CLA for community working groups, but Benjie explained that the CLA is a requirement for contributions related to GraphQL Foundation deliverables, such as specifications and reference implementations. Benjie suggested that this issue should be discussed with the Foundation Board and the technical steering committee to determine if community working group discussions fall outside the scope of protected deliverables. 30 | 31 | ### Community Board and API Updates 32 | 33 | Benjie suggested bringing a community recommendation to the board meeting, but noted that Jeff's involvement as a board member would be stronger. Martin agreed to check the list of board representatives, which was shared during the GraphQL All Hands meeting. Jem mentioned a pull request for the website to improve navigation for new contributors, and Martin praised its clarity and useful screenshots. Martin provided an update on API Days Paris, awaiting sponsorship confirmation and a process to handle CFP applications, with potential deadline adjustments. 34 | 35 | ### FOSDEM 2025 Planning and Logistics 36 | 37 | The team discussed plans for FOSDEM 2025, agreeing to use a blog post on the foundation website to gather talk proposals, with Jem and Martin planning to share this information with ambassadors through face-to-face meetings and communication channels. Benjie mentioned that TSC members should be added to the Ambassador mailing list, and Martin confirmed he has access to the Ambassadors Discord channel. The team also addressed an issue with the CLA bot deployment, which was raised with the IT team, and discussed a pull request for website updates regarding TSC member meetup admin access and video requirements, which needs approval from the Foundation's conference committee. 38 | -------------------------------------------------------------------------------- /wg.config.js: -------------------------------------------------------------------------------- 1 | // @ts-check 2 | 3 | /** @type {import('wgutils').Config} */ 4 | const config = { 5 | name: "Community Working Group", 6 | repoUrl: "https://github.com/graphql/community-wg", 7 | videoConferenceDetails: `https://zoom.us/j/93104287544 8 | - _Password:_ community`, 9 | liveNotesUrl: 10 | "https://docs.google.com/document/d/1Rc7Lku5rQlqFu65PosBXSWWrPXw5zQmYWVWjiTg0qZA/edit?usp=sharing", 11 | timezone: "US/Pacific", 12 | frequency: "monthly", 13 | // For "last" set nth to -1 14 | nth: 2, 15 | weekday: "Th", // M, Tu, W, Th, F, Sa, Su 16 | time: "08:00-09:00", // 24-hour clock, range 17 | attendeesTemplate: `\ 18 | | Name | GitHub | Organization | Location | 19 | | :--------------- | :------------ | :----------------- | :-------------------- | 20 | `, 21 | /* 22 | // Additional configuration (optional): 23 | 24 | agendasFolder: "agendas", 25 | dateAndTimeLocations: 'p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240', 26 | joiningAMeetingFile: "JoiningAMeeting.md", 27 | filenameFragment: "wg-primary", 28 | description: `\ 29 | The GraphQL Working Group meets regularly to discuss changes to the 30 | [GraphQL Specification][] and other core GraphQL projects. This is an open 31 | meeting in which anyone in the GraphQL community may attend. 32 | 33 | This is the primary monthly meeting, which typically meets on the first Thursday 34 | of the month. In the case we have additional agenda items or follow ups, we also 35 | hold additional secondary meetings later in the month.`, 36 | links: { 37 | "graphql specification": "https://github.com/graphql/graphql-spec", 38 | calendar: "https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com", 39 | "google calendar": "https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t", 40 | "ical file": "https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics", 41 | }, 42 | secondaryMeetings: [ 43 | { 44 | // Wednesday, not Thursday 45 | dayOffset: -1, 46 | nth: 2, 47 | time: "16:00-17:00", 48 | name: "Secondary, APAC", 49 | // filenameFragment: "wg-secondary-apac", 50 | description: `\ 51 | The GraphQL Working Group meets regularly to discuss changes to the 52 | [GraphQL Specification][] and other core GraphQL projects. This is an open 53 | meeting in which anyone in the GraphQL community may attend. 54 | 55 | This is a secondary meeting, timed to be acceptable for those in Asia Pacific 56 | timezones, which typically meets on the second Wednesday of the month. The 57 | primary meeting is preferred for new agenda, where this meeting is for overflow 58 | agenda items, follow ups from the primary meeting, or agenda introduced by those 59 | who could not make the primary meeting time.`, 60 | }, 61 | { 62 | nth: 3, 63 | time: "10:30-12:00", 64 | name: "Secondary, EU", 65 | filenameFragment: "wg-secondary-eu", 66 | description: `\ 67 | The GraphQL Working Group meets regularly to discuss changes to the 68 | [GraphQL Specification][] and other core GraphQL projects. This is an open 69 | meeting in which anyone in the GraphQL community may attend. 70 | 71 | This is a secondary meeting, timed to be acceptable for those in European 72 | timezones, which typically meets on the third Thursday of the month. The 73 | primary meeting is preferred for new agenda, where this meeting is for overflow 74 | agenda items, follow ups from the primary meeting, or agenda introduced by those 75 | who could not make the primary meeting time.`, 76 | }, 77 | ], 78 | */ 79 | }; 80 | 81 | module.exports = config; 82 | -------------------------------------------------------------------------------- /notes/2025/2025-09.md: -------------------------------------------------------------------------------- 1 | # Community WG Notes - February 2025 2 | 3 | **Watch the replays:** 4 | [GraphQL Working Group Meetings on YouTube](https://www.youtube.com/watch?v=TXe95DBsNiE&list=PLP1igyLx8foHhWZk2u1SthsW1weH3VA7l) 5 | 6 | Agenda: 7 | [https://github.com/graphql/community-wg/blob/main/agendas/2025/09-Sep/25-community-working-group-september-2025.md](https://github.com/graphql/community-wg/blob/main/agendas/2025/09-Sep/25-community-working-group-september-2025.md) 8 | 9 | Attendees 10 | 11 | - Benjie 12 | - Jem 13 | - Martin 14 | - Jeff 15 | - Vanessa 16 | - Uri 17 | - Taz 18 | - Apologies: Jonathan 19 | 20 | ### API Days 21 | 22 | [https://www.apidays.global/events/paris](https://www.apidays.global/events/paris) 23 | 24 | [https://graphql.day](https://graphql.day) 25 | 26 | GraphQL Day on 11th December, 100-150 attendees 27 | 28 | CfP is centralized with API Days, closes on 12th October 29 | 30 | Martin will be attending 31 | 32 | Speaking sessions: lightning talks and regular 40 minutes; 33 | 34 | Attendees: at the moment will buy a ticket for all three days 35 | 36 | Staff: CfP & booth staff get free tickets 37 | 38 | Seeking volunteers for CfP team 39 | 40 | ## FOSDEM 41 | 42 | Closing date for devroom application is 12 october 43 | 44 | More information: 45 | [https://github.com/graphql/community-wg/issues/109](https://github.com/graphql/community-wg/issues/109) 46 | 47 | [https://fosdem.org/2026/](https://fosdem.org/2026/) 48 | 49 | ## Ambassador Scheme update 50 | 51 | Launched on stage at GraphQL Conf 52 | 53 | We have 19 enthusiastic ambassadors, with 10 further applications to be reviewed 54 | in November 55 | 56 | 1st set of onboarding calls has happened with lots of new ideas already emerging 57 | 58 | ## Google Summer of Code 59 | 60 | [https://summerofcode.withgoogle.com/archive/2020/organizations/6354766843609088](https://summerofcode.withgoogle.com/archive/2020/organizations/6354766843609088) 61 | 62 | Should we incorporate a project for Google Summer of Code? \ 63 | Vanessa’s project was about embedding accessibility into GraphQL 64 | 65 | A yearly cycle, projects are announced in Spring 66 | 67 | Contributors to the project are students or anyone new to open source 68 | 69 | One of the aspects is regular mentoring sessions 70 | 71 | We should see if we can get some commitment from potential mentors and go from 72 | there 73 | 74 | Vanessa & Martin as potential mentors 75 | 76 | Jeff can liaise with the GraphQL Board for legal matters 77 | 78 | Draft email to board: 79 | 80 | _In the September 2025 meeting of the Community WG, Vanessa Johnson (New York 81 | Times, GraphQLConf speaker) suggested that GraphQL participate in Google Summer 82 | of Code (GSoC) 2026. Apparently we did this in 2020 and there's been some 83 | discussion about doing it again here. With the Board's approval, we'd like to 84 | put out a call for volunteers to mentor GSoC participants and put together 85 | projects. Vanessa has already raised her hand to serve in this capacity. It 86 | seems highly aligned with the Foundation’s mission but if anyone has any 87 | concerns please feel free to reply! We expect that there will need to be 88 | sign-off from the Foundation at some point in the process. We can add this as a 89 | discussion item in the next Board meeting._ 90 | 91 | ## Other Business 92 | 93 | - For feedback on the Guild platform you can Slack Taz questions, or email 94 | - The landing page of the website is done, but designs on other pages are being 95 | worked on eg the Learn pages, Community pages, etc 96 | - How do we want to organize the conference videos on the website? As at the 97 | moment it is all just under the conference schedule 98 | - Guild platform APIs - Taz is happy to work with the Foundation to build an API 99 | for Guild events to expose to the website. This can also mirror Meetup events. 100 | - [GraphQL.org](GraphQL.org) events page - Benjie & Jem updated it for the 101 | Conference, removing outdated events etc, but being able to synchronise events 102 | in the future would be great; along with showing videos and photos 103 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # GraphQL Community Working Group 2 | 3 | This working group is a subcommittee of the 4 | [GraphQL Working Group](https://github.com/graphql/graphql-wg) with the 5 | following primary purpose: 6 | 7 | > Serve as the steward of GraphQL's global narrative and market positioning in the 8 | > technology ecosystem. We develop and execute strategic initiatives that 9 | > reinforce GraphQL's value proposition while fostering an engaged, educated, and 10 | > expanding community. 11 | 12 | Anyone in the public GraphQL community may attend a meeting of this 13 | subcommittee, provided they first sign the 14 | [Specification Membership Agreement](https://github.com/graphql/graphql-wg/tree/main/membership) 15 | or belong to an organization which has signed. 16 | 17 | This repository holds [agendas](./agendas) and [notes](./notes) for all meetings 18 | past and upcoming as well as [shared RFC documents](./rfcs). Anyone may edit an 19 | upcoming event's agenda to _attend_ or _propose an agenda item_. 20 | 21 | All meetings occur via video conference, however participating company offices 22 | are welcome to host guests. 23 | 24 | Meetings are typically scheduled (DETAILS OF MEETING SCHEDULE). Check the 25 | [agendas](./agendas) for the exact date and time of upcoming meetings. 26 | 27 | Keep track of future upcoming meetings by subscribing to the 28 | [Google Calendar](https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t) 29 | or 30 | [ical file](https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics). 31 | (maintained in UTC because time zones are hard). 32 | 33 | ### Joining a meeting? 34 | 35 | To request participation in an upcoming meeting, please send a pull request by 36 | editing the relevant [meeting agenda](./agendas). 37 | 38 | ### Want to help us keep up? 39 | 40 | We're always looking for volunteers to help take notes from the meetings, the 41 | results of which are shared in [`notes/`](./notes). If you're interested in 42 | taking notes, sign up for a meeting in [`agendas/`](./agendas) and indicate that 43 | you're willing to be a note taker. 44 | 45 | ## Participation guidelines 46 | 47 | Meetings with many participants, especially over video, can easily get hard to 48 | follow or run off course. When we talk about issues we care about, it's easy to 49 | get into heated debate. In order to respect everyone's time, and arrive to 50 | worthwhile outcomes, this subcommittee follows the 51 | ["Participation guidelines" in the GraphQL Working Group](https://github.com/graphql/graphql-wg/blob/main/README.md#participation-guidelines); 52 | a summary of which is: 53 | 54 | - Participate 55 | - Don't talk too much 56 | - Volunteer to take notes 57 | - Have an outcome in mind 58 | - Contribute 59 | - Choose your battles 60 | - Champion alternatives 61 | - Block progress as a last resort 62 | - Be patient and persistent 63 | 64 | ## Contributing to this repo 65 | 66 | This repository is managed by EasyCLA. Project participants must sign the free 67 | ([GraphQL Specification Membership agreement](https://preview-spec-membership.graphql.org) 68 | before making a contribution. You only need to do this one time, and it can be 69 | signed by 70 | [individual contributors](http://individual-spec-membership.graphql.org/) or 71 | their [employers](http://corporate-spec-membership.graphql.org/). 72 | 73 | To initiate the signature process please open a PR against this repo. The 74 | EasyCLA bot will block the merge if we still need a membership agreement from 75 | you. 76 | 77 | You can find 78 | [detailed information here](https://github.com/graphql/graphql-wg/tree/main/membership). 79 | If you have issues, please email 80 | [operations@graphql.org](mailto:operations@graphql.org). 81 | 82 | ### Commit access 83 | 84 | Commit access is granted to this repo to members of the 85 | [GraphQL TSC](./GraphQL-TSC.md) and some regular attendees of subcommittee 86 | meetings. To request commit access, please reach out to a TSC member. 87 | 88 | ## Generating agendas 89 | 90 | To create the agenda files for a given month YYYY/MM, run the following command: 91 | 92 | ``` 93 | yarn && yarn gen-agenda YYYY MM 94 | ``` 95 | -------------------------------------------------------------------------------- /agendas/2025/03-Mar/13-community-working-group-march-2025.md: -------------------------------------------------------------------------------- 1 | | This is an open meeting: To attend, edit and PR this file. (Edit: ✎ above, or press "e") | 2 | | ---------------------------------------------------------------------------------------- | 3 | 4 | # Community Working Group — March 2025 5 | 6 | - **Date & Time**: 7 | [March 13, 2025, 8:00 – 9:00 AM PDT](https://www.timeanddate.com/worldclock/converter.html?iso=20250313T150000&p1=224&p2=179&p3=136&p4=268&p5=367&p6=438&p7=248&p8=240) 8 | - View the [calendar][], or subscribe ([Google Calendar][], [ical file][]). 9 | - _Please Note:_ The date or time may change. Please check this agenda the 10 | week of the meeting to confirm. While we try to keep all calendars accurate, 11 | this agenda document is the source of truth. 12 | - **Video Conference Link**: https://zoom.us/j/93104287544 13 | - _Password:_ community 14 | - **Live Notes**: [Live Notes][] 15 | 16 | [calendar]: 17 | https://calendar.google.com/calendar/embed?src=linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com 18 | [google calendar]: 19 | https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t 20 | [ical file]: 21 | https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics 22 | [live notes]: 23 | https://docs.google.com/document/d/1Rc7Lku5rQlqFu65PosBXSWWrPXw5zQmYWVWjiTg0qZA/edit?usp=sharing 24 | 25 | ## Attendees 26 | 27 | 28 | | Name | GitHub | Organization | Location | 29 | |:------------------|:-------------- |:-------------|:----------| 30 | | Saihajpreet Singh | @saihaj | The Guild | India | 31 | | Martin Bonnin | @martinbonnin | apollo | Paris, FR | 32 | | Jem Gillam | @jemgillam | Graphile | Chandler's Ford UK | 33 | | Doc Jones | @doc-jones | Self | Raleigh, NC, USA | 34 | | Meenakshi Dhanani | @meenakshi-dhanani | Postman | India | 35 | | An Ngo | @vliegveld5 | Bol | The Netherlands | 36 | | Erik Wrede | @erikwrede | Self | Aachen, Germany | 37 | | Benjie Gillam | @benjie | Graphile | Chandler's Ford, UK | 38 | | Jeff Auriemma | @bignimbus | Apollo | Monroe, CT, USA | 39 | | Uri Goldshtein | @urigo | The Guild | Tel Aviv, IL | 40 | | Dan Starns | @danstarns | Rconnect | London, UK | 41 | 42 | 43 | 44 | 45 | ## Agenda 46 | 47 | 1. Agree to Membership Agreement, Participation & Contribution Guidelines and 48 | Code of Conduct (1m, Host) 49 | - [Specification Membership Agreement](https://github.com/graphql/foundation) 50 | - [Participation Guidelines](https://github.com/graphql/graphql-wg#participation-guidelines) 51 | - [Contribution Guide](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md) 52 | - [Code of Conduct](https://github.com/graphql/foundation/blob/master/CODE-OF-CONDUCT.md) 53 | 1. Introduction of attendees (5m, Host) 54 | 1. Determine volunteers for note taking (1m, Host) 55 | 1. Review agenda (2m, Host) 56 | 1. Check for 57 | [ready for review agenda items](https://github.com/graphql/community-wg/issues?q=is%3Aissue+is%3Aopen+label%3A%22Ready+for+review+%F0%9F%99%8C%22+sort%3Aupdated-desc) 58 | (5m, Host) 59 | 1. Make the Discord channel public? (5m, All) 60 | - https://github.com/graphql/community-wg/issues/44 61 | 1. [Align on main goals for the working group]([https://github.com/graphql/community-wg/issues/28](https://github.com/graphql/community-wg/issues/28#issuecomment-2718221158)) (15m, Urigo) 62 | 1. [Align on how to manage intiatives (ideas, actions, champions, stages and tracking progress)]([https://github.com/graphql/community-wg/issues/28](https://github.com/graphql/community-wg/issues/28#issuecomment-2718221158)) (10m, Urigo) 63 | 1. [Making progress on the website redesign](https://github.com/graphql/community-wg/issues/21) (5m, Urigo) 64 | 1. How to involve the community in GraphQL conf organization? (15m, Martin, All) 65 | 1. Where is help needed? 66 | 1. Host monthly wg meetings as a live stream. (Use foundation's YouTube channel) (5 to 10m, Doc, All) 67 | -------------------------------------------------------------------------------- /notes/2025/2025-04.md: -------------------------------------------------------------------------------- 1 | # Community WG Notes - April 2025 2 | 3 | **Watch the replays:** 4 | [GraphQL Working Group Meetings on YouTube](https://www.youtube.com/playlist?list=PLP1igyLx8foHhWZk2u1SthsW1weH3VA7l) 5 | 6 | Agenda: 7 | 8 | [https://github.com/graphql/community-wg/blob/main/agendas/2025/04-Apr/10-community-working-group-april-2025.md](https://github.com/graphql/community-wg/blob/main/agendas/2025/04-Apr/10-community-working-group-april-2025.md) 9 | 10 | ## Determine volunteers for note taking (1m, Host) 11 | 12 | - Benjie 13 | - Jeff 14 | 15 | ## Check for [ready for review agenda items](https://github.com/graphql/community-wg/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen+label%3A%22Ready+for+review%22+sort%3Aupdated-desc) (5m, Host) 16 | 17 | - Will be covered by agenda. 18 | 19 | ## "Empowering the community" defined (Uri - 5 mins) requested by Doc 20 | 21 | - Unblock and empower community initiatives 22 | - "To support the people who are already doing stuff in any way we can" 23 | - i.e. rather than incentivising inactive people to become active, and rather 24 | than assuming we know what people want, let's find out from the people who are 25 | doing things what they actually need/want. 26 | - Benjie: sometimes individuals, sometimes group based - defining what it 27 | means - spec, docs, site, reference implementation, dev tooling; w/in 28 | Foundation projects 29 | - Then ppl doing tools like servers, clients, atc 30 | - Then ppl who like to share the word of GraphQL, empower others, do talks, 31 | attend events 32 | - Sometimes more specific - one person needs support vs. a category or community 33 | - Jeff: can we provide some guidance eg to those who submit a talk proposal; can 34 | we tell people’s stories, help giving them some structure or helping them to 35 | “pitch in”; 36 | - “We’re here, we’re not scary, and we will help you!” 37 | - Doc: Mentorship programs - ppl volunteer to mentor, can pair maintainers 38 | looking for help w newcomers who want to figure out how to contribute 39 | - “Getting from 0 to 1 is the hardest part” 40 | 41 | ## Survey (Doc and Martin) 42 | 43 | - Gartner/etc do "State of X, Y, Z" which may imply it's vendor focussed 44 | - Sacha runs "State of …" which are all developer surveys, which was the case 45 | for State of GraphQL 46 | - Sacha's codebase is OSS, but isn't well documented and he's offering to do a 47 | walk through (and maybe accept some contributions) 48 | - Issue: no-one has stepped up to accept this walk-through; he's offered to do 49 | it now, he may not be available in future 50 | - How might we find TS developers? 51 | - The Guild have already done some PRs against that codebase, but alas they 52 | don't have any availability. 53 | - Uri: We can support people who are already doing things, but we struggle to 54 | find people to do things to start with 55 | - Benjie: It took quite a while to find new maintainers for GraphQL.js, though 56 | we have a few now. 57 | - Doc is going to try and find some TS developers to do the walk-through 58 | 59 | ## Update for [issue 22](https://github.com/graphql/community-wg/issues/22) (making content selection more transparent) (Jem - 5 mins) 60 | 61 | - Jem: how to make content selection and conf planning more transparent - fit 62 | nicely to what Benjie and I worked on w committee - launch an initiative 63 | called Subject Matter Experts (SMEs) - Netherlands, Amsterdam companies, 64 | trying to get them involved in the talk selection process 65 | - Last year talks were rated by TSC - focused on talk quality, speaker 66 | reputation, their opinion of GraphQL on the stage 67 | - This year, more focus on excitement, what might be different 68 | - Updated a section on GraphQL website explaining the “how” (not the “who”) - 69 | public info where none was there before 70 | - Please help to share the initiative, get people to sign up! 71 | - What’s the sweetener? Tee shirt? Bowtie? Level of effort? Time commitment 72 | 73 | ## Calls for comments on the Ambassador scheme [PR 64 issue 1](https://github.com/graphql/community-wg/pull/64) (Jem - 10 mins?) 74 | 75 | - Nominations on rolling schedule 76 | - Perhaps first before or during the conf? 77 | - Benjie: levels of community - this is the “broader” side - tutorials, video 78 | content, articles w/ technical writing 79 | - Jeff: zero to one - let’s remain flexible and get someone interested, work 80 | with them 81 | - Doc: different goals - some want to speak, some want to do social media, video 82 | - Jamie Barton for example 83 | 84 | ## Short update on the [new graphql.org design initiative](https://github.com/graphql/community-wg/issues/21) (Uri - 10 mins) 85 | 86 | - (no notes taken, but lots of conversation) 87 | -------------------------------------------------------------------------------- /notes/2025/summary-2025-04-10.md: -------------------------------------------------------------------------------- 1 | # Meeting Summary for Community WG 2 | 3 | **NOTICE**: This summary was auto-generated by Zoom's "AI". AI-generated 4 | content may be inaccurate or misleading. Always check for accuracy. If in 5 | doubt, please consult the meeting recording at 6 | https://youtube.com/@GraphQLFoundation/playlists 7 | 8 | - Meeting start: 2025-04-10T15:00:02Z 9 | - Meeting end: 2025-04-10T16:00:51Z 10 | - Summary start: 2025-04-10T15:00:36Z 11 | - Summary end: 2025-04-10T16:00:46Z 12 | 13 | The meeting covered introductions, discussions on community empowerment, and updates on various GraphQL initiatives. Participants explored ways to support and engage community members, including mentorship programs and an ambassador scheme. The group also addressed challenges with AI note-taking, reviewed the GraphQL website redesign, and discussed the organization's structure and target audiences. 14 | 15 | ## Next Steps 16 | 17 | - Doc to reach out to his network to find TypeScript developers for the State of GraphQL survey code walkthrough with Sasha. 18 | - All members to share the GraphQL Ambassador program proposal with potential candidates and provide feedback. 19 | - Uri to open an issue to discuss and document where the Community Working Group fits with other working groups and committees. 20 | - All members to share the new website design with others who might have valuable opinions on it. 21 | - Uri to start working on designs for additional pages of the website (learn section, community section, etc.). 22 | - Doc to submit detailed questions and feedback on the website design process in the relevant GitHub issue. 23 | 24 | ## Summary 25 | 26 | ### Introductions and AI Note-Taking Discussion 27 | 28 | In the meeting, Doc, Lavan, Uri, Benjie, Jem, and Jeff introduced themselves and their organizations. Lavan expressed interest in contributing to the GraphQL project and was encouraged to reach out to Uri or Benjie for guidance. The group also discussed the use of AI note-taking, with Jeff offering a bookmarklet to extract meeting information. The conversation ended with a discussion about the meeting's notes, with Benjie mentioning that he had set up AI note-taking but was struggling to extract the information from Zoom's interface. 29 | 30 | ### Empowering Community Through Support and Motivation 31 | 32 | In the meeting, Benjie discussed the challenges of syncing AI notes and the value of human note takers. Doc outlined the agenda, which included a review of the website and a discussion on empowering the community. Uri shared his opinion on supporting community initiatives and empowering volunteers. Jeff emphasized the importance of empowering motivated community members and supporting them in their contributions. Benjie highlighted the need to define what empowering the community means and how to support different communities. Jeff suggested broadening the community's reach by encouraging participation from those who submit abstracts to conferences. 33 | 34 | ### Mentorship and Survey Challenges Discussed 35 | 36 | Doc discussed the importance of mentorship in open-source projects, citing his experiences with Python and Rust. He suggested incorporating mentorship into the community's empowerment strategy. Jem agreed with Doc's points and added that getting from 0 to 1 is the hardest part of a process. The team then discussed the State of GraphQL survey, with Doc expressing concern about the lack of response and the need for a code walkthrough. Uri and Benjie suggested that the team may not have the necessary expertise to handle the survey, and Doc decided to reach out to his network for help. Jem then updated the team on the progress of the content selection and planning for the conference, including the launch of an initiative to involve project owners and maintainers in the talk selection process. 37 | 38 | ### Increasing Transparency in Upcoming Conference 39 | 40 | Jem proposed the idea of increasing transparency in the upcoming conference, which Doc and Benjie agreed was a great idea. Jem also discussed the ambassador program, which aims to support and recognize community members who actively contribute to the GraphQL community. Doc suggested a conversation in the future to clarify the structure and roles of different committees within the foundation. 41 | 42 | ### Ambassador Program Flexibility Discussed 43 | 44 | Jeff expressed excitement about the ambassador scheme and suggested being flexible in accommodating different needs and contributions. Doc offered to assist with the program and suggested considering various skill sets and goals for ambassadors. Benjie agreed to gather names of potential ambassadors and encouraged reaching out to them to understand their needs. The team discussed the importance of flexibility in the ambassador program to accommodate different contributions. 45 | 46 | ### GraphQL Organization and Website Redesign 47 | 48 | The group discusses the structure of the GraphQL organization, including the foundation and technical project aspects. Benjie explains that the foundation handles non-technical matters while the Technical Steering Committee oversees public working groups. Uri suggests documenting this information and starting discussions through issues. The conversation then shifts to the GraphQL website redesign, with Uri seeking feedback and encouraging sharing the design for more input. Doc raises concerns about defining target audiences and value propositions for different user groups, to which Uri responds that they have already identified enterprise companies and full-stack TypeScript developers as primary targets. 49 | -------------------------------------------------------------------------------- /notes/2025/summary-2025-09-25.md: -------------------------------------------------------------------------------- 1 | # Meeting Summary for Community WG 2 | 3 | **NOTICE**: This summary was auto-generated by Zoom's "AI". AI-generated 4 | content may be inaccurate or misleading. Always check for accuracy. If in 5 | doubt, please consult the meeting recording at 6 | https://youtube.com/@GraphQLFoundation/playlists 7 | 8 | - Meeting start: 2025-09-25T14:00:21Z 9 | - Meeting end: 2025-09-25T14:41:49Z 10 | - Summary start: 2025-09-25T14:01:11Z 11 | - Summary end: 2025-09-25T14:41:42Z 12 | 13 | The September Community Working Group meeting began with introductions and updates on upcoming GraphQL events, including API Days Paris and potential participation in FOSDEM 2024. The team discussed organizing community events and initiatives, including a GraphQL day at API Days Paris and a possible Dev Room track at FOSDEM, while also exploring opportunities for Google Summer of Code participation. Website improvements and event management were addressed, with plans to reorganize the GraphQL website's learning and community sections, and discussions about upcoming scheduling features for conferences. 14 | 15 | ## Next Steps 16 | 17 | - Martin to open an issue on the community working group GitHub for volunteers to help with the GraphQL Day at API Days Paris CFP. 18 | - Martin to lead the organization of GraphQL Day at API Days Paris . 19 | - Community members to submit talks for GraphQL Day at API Days Paris before the CFP closes on October 12th. 20 | - Jeff to email the GraphQL Foundation board about Google Summer of Code participation. 21 | - Vanessa to look into more details about Google Summer of Code organization requirements. 22 | - Benjie to raise issues across working groups to find mentor volunteers for Google Summer of Code after board approval. 23 | - Uri to share website redesign updates and create specific issues for each type of page/content early next week. 24 | - Uri to follow up with Taz about Guild.host APIs for automating event content on the GraphQL website. 25 | - Community members to review Jeff's draft email to the governing board about Google Summer of Code. 26 | 27 | ## Summary 28 | 29 | ### GraphQL Day at API Days Paris 30 | 31 | The September Community Working Group meeting began with introductions from Benjie, Martin, Jem, Vanessa, and Uri. Martin confirmed that Jonathan Rayner and Janet would not be attending. The group discussed the GraphQL Day at API Days Paris, which Martin presented as a three-day event in Paris on December 9-11, with GraphQL content scheduled for December 11. Martin noted that the GraphQL room would be smaller and more intimate than in previous years, with a capacity of 100-150 people. 32 | 33 | ### GraphQL Day Event Planning Discussion 34 | 35 | The team discussed organizing a GraphQL day event hosted by API Day, with Martin explaining that the community event will take place in a room provided by API Day and offering free tickets to contributors. They discussed the CFP process, with Martin noting that a team of volunteers is needed to review submissions, and Benjie emphasizing the importance of a streamlined process to finalize talks within a few weeks. Jem introduced the topic of FOSDEM, a major open-source conference in Brussels, and asked if the team wants to organize another Dev Room track focused on GraphQL and related technologies, with a submission deadline in October. 36 | 37 | ### FOSDEM Event Application Planning 38 | 39 | The team discussed organizing an event application for FOSDEM, a community-oriented open-source conference, with a deadline on October 12th. Jem highlighted the importance of having a strong team to champion the application process, noting that previous experiences at the event have increased awareness of GraphQL. Benjie described FOSDEM as a unique event with a large number of attendees, emphasizing its interactive format with classroom-style talks and booths for project representation. The team agreed on the need to submit an application soon to participate in the event. 40 | 41 | ### FOSDEM 2024 Planning and Ambassadors 42 | 43 | The group discussed plans for FOSDEM 2024, with Benjie proposing a minimal-effort booth option versus a more resource-intensive dev room or combined booth/table setup. Jem reported on the successful launch of the ambassador program, which now has 19 ambassadors and is receiving new applications for December review. Vanessa presented an idea for a Google Summer of Code project focused on embedding accessibility information into GraphQL, building on her own previous experience with the program. 44 | 45 | ### Google Summer of Code Planning 46 | 47 | The group discussed applying for Google Summer of Code, with Vanessa providing details about the application process and mentor requirements. Jeff volunteered to present the initiative to the board, while Vanessa and Martin expressed interest in mentoring. Benjie suggested raising the topic at working group meetings to find more mentors and project ideas. The team agreed to start with an email to the board for authorization and to create a community working group issue for further discussion. 48 | 49 | ### GraphQL Website Redesign Updates 50 | 51 | The meeting covered updates on the GraphQL website redesign, with Uri discussing plans to reorganize the learning and community sections, including a new content organization approach. Taz explained that while event reordering isn't currently possible in grill.host, new scheduling features are being developed for conferences. The team discussed the events page improvements, with Benjie noting they had recently removed outdated events and updated the list of known GraphQL meetups. Jeff introduced a draft email about potentially participating in Google Summer of Code 2026, which the group agreed to review. 52 | -------------------------------------------------------------------------------- /rfcs/ambassador-program/overview-for-ambassadors.md: -------------------------------------------------------------------------------- 1 | ## GraphQL Ambassador Program 2 | 3 | The following is an overview of the proposed GraphQL Ambassador Program for the 4 | Ambassadors themselves, with the intention that this becomes the page on the 5 | website outlining the goals, outcomes and tasks of the program; similar to other 6 | initiatives like 7 | [Community Grants](https://graphql.org/community/foundation/community-grant/) 8 | and the 9 | [Local Initiative](https://graphql.org/community/foundation/local-initiative/). 10 | 11 | ### Become a GraphQL Ambassador 12 | 13 | GraphQL Ambassadors are trusted go-to community leaders driven by a passion for 14 | GraphQL projects and strive to nurture the growing GraphQL community through 15 | collaboration, education and outreach. 16 | 17 | As an Ambassador, you also gain the following: 18 | 19 | - Professional recognition for expertise and contributions to the GraphQL 20 | community 21 | - Opportunities to network with other GraphQL leaders, both in your local 22 | community and online 23 | - A closer relationship with the GraphQL Foundation & project, including 24 | up-to-date news and insights on upcoming Specification edits and working group 25 | topics 26 | - Support, funding and mentoring from the GraphQL Foundation for hosting events, 27 | speaking and creating content 28 | - Exclusive benefits and swag 29 | 30 | ### Ambassador Requirements 31 | 32 | - Knowledgeable about GraphQL and readily able to articulate those ideas 33 | - A model community member: adhering to the Standards of Excellence especially 34 | when critical of GraphQL or defending it against others' criticism; remaining 35 | respectful, constructive and fair 36 | - Do not come across to other community members as selling another product, 37 | service or agenda when acting as an Ambassador 38 | - Agree to have your face, name, chosen socials and other relevant information 39 | displayed on the "people"/"Ambassadors" webpage 40 | - Already participate in one or more of the Ambassador tasks outlined below 41 | 42 | ### Ambassador Tasks 43 | 44 | GraphQL Ambassadors are an important touchstone for people interested in GraphQL 45 | to learn more about it in a friendly and constructive way. 46 | 47 | As an Ambassador, you will do four or more Ambassador tasks throughout your one 48 | year term. Your can do the same task four times, or a mixture of tasks. 49 | 50 | Ambassador tasks include: 51 | 52 | 1. **Community Leadership** 53 | - Local Gathering organizer 54 | - Organizer/program planner for a GraphQL focused event, conference track, 55 | or similar 56 | - Mentorship hours 57 | - GraphQL Foundation community Discord moderation 58 | 1. **Public Speaking** 59 | - Speaking at industry, community or GraphQL Foundation events about GraphQL or GraphQL 60 | projects 61 | 1. **GraphQL Focused Content Creation** 62 | - Producing written content, both on GraphQL Foundation platforms and 63 | elsewhere 64 | - Have written a GraphQL focused book 65 | - Producing video and/or audio content, either on GraphQL Foundation 66 | platforms or elsewhere 67 | - Building demo apps 68 | 1. **Active Contribution to a GraphQL Foundation Project or Specification** 69 | - Have held a formal role in a GraphQL Foundation project 70 | - Shared valuable insights or feedback at the GraphQL working group or 71 | sub-working groups 72 | 1. **Maintainer or A Main Contributor of a Key Open-Source GraphQL Related 73 | Project** 74 | - For example, GraphQL clients, servers, tooling or implementations 75 | 1. **Outreach for GraphQL Foundation initiatives** 76 | - Discussion and guidance helping a non-Foundation project to adopt, test 77 | and provide feedback on a GraphQL Specification proposal 78 | - Organizing a venue for a GraphQL Local 79 | - Media outreach with a measurable impact e.g. publication in a major tech 80 | outlet or mainstream media 81 | 82 | _Note: content should align with open-source principles and not be behind 83 | paywalls_ 84 | 85 | ### What the Foundation offers 86 | 87 | - Quarterly online meeting with Foundation / TSC representatives: 88 | - 15 minute presentation from the Foundation on current projects, 89 | Specification edits and working group topics 90 | - followed by Q&A 91 | - time for Ambassadors to give feedback on the current directions of the 92 | GraphQL project, be that technical (eg Specification RFCs), or community 93 | initiative focused 94 | - Promotion of the Ambassador as a go-to GraphQL community leader: 95 | - Website profile 96 | - Biographies / interviews with each Ambassador 97 | - Credly badge for social media profiles 98 | - An Ambassador role on the community Discord and an associated private channel 99 | for networking and discussions with Foundation / TSC / community reps 100 | - Promotion of Ambassador material - conference talk videos and created content 101 | - Exclusive GraphQL swag eg Ambassador hoodie 102 | - Free GraphQL Foundation Conference ticket 103 | - Ambassadors may apply for travel funding to approved conference & meetup 104 | talks, applications to be evaluated on a case-by-case basis 105 | - An honorarium available for content creation on a case-by-case basis 106 | 107 | ### Ambassador Code of Conduct 108 | 109 | While the wider GraphQL community abides by the 110 | [contributor covenant code of conduct](https://graphql.org/codeofconduct/), a 111 | stronger set of standards is used for the Ambassador Program. This is because 112 | the Foundation endorses Ambassadors as representatives and leaders; the 113 | Standards of Excellence are designed to provide a set of guidelines and best 114 | practices for engaging with the GraphQL Foundation and broader community. This 115 | makes it easier for Ambassadors to contribute to a positive culture by providing 116 | clarity around what and how we create a safe and collaborative environment. See 117 | [standards-of-excellence.md](./standards-of-excellence.md) 118 | 119 | ### Application Process 120 | 121 | Applications are open year-round and are received by a small panel of Foundation 122 | and TSC members. Once the Ambassadors program is fully up-and-running, 123 | Ambassadors will also have the option to review applications. The Ambassador 124 | term is a year long, Ambassadors who continue to meet the expectations will be 125 | invited to join again at the end of their term. 126 | 127 | Applications can be from the applicant themselves, or a nomination from another 128 | community member. 129 | 130 | A new wave of Ambassadors will be announced quarterly; we are aiming for the 131 | first announcement to coincide with the GraphQL Conference in September 2025. 132 | 133 | ### Apply 134 | 135 | Are you interested in becoming an official GraphQL Ambassador? 136 | 137 | [Submit your application button] 138 | 139 | Have a question? [Contact details] 140 | -------------------------------------------------------------------------------- /notes/2025/2025-02.md: -------------------------------------------------------------------------------- 1 | # Community WG Notes - February 2025 2 | 3 | **Watch the replays:** 4 | [GraphQL Working Group Meetings on YouTube](https://www.youtube.com/watch?v=TXe95DBsNiE&list=PLP1igyLx8foHhWZk2u1SthsW1weH3VA7l) 5 | 6 | 7 | 8 | Agenda: 9 | [https://github.com/graphql/community-wg/blob/main/agendas/2025/02-Feb/13-community-working-group-february-2025.md](https://github.com/graphql/community-wg/blob/main/agendas/2025/02-Feb/13-community-working-group-february-2025.md) 10 | 11 | ## Determine volunteers for note taking (1m, Host) 12 | 13 | - Benjie 14 | 15 | ## Review agenda (2m, Host) 16 | 17 | - This is the first meeting, so the agenda is quite open ended today. 18 | 19 | ## Individual goals 20 | 21 | - Erik: GraphQL in Python; FOSDEM API meetup; local meetups. I'm curious on how 22 | I can help and how we can shape future GraphQL initiatives as a whole. 23 | - Rob: hoping to start a GraphQL NY meetup; 8 people in the Discord so far 24 | - Doc: put a lot of effort into organizing the first GraphQL Conf as an OSS 25 | project; currently working with LF and contributing to OSS. Hoping to get back 26 | into GraphQL. I really like the content creation and community aspects around 27 | GraphQL. Like to see more engagement through content creation. 28 | - Pascal: work at ChilliCream; run community groups in Zurich and attend others 29 | too. Want an easier way to organize these - it's quite challenging to find 30 | talks. The best way to reach people is to stand in front of them and speak. 31 | - Michael: I hope that the Conference planning will be more transparent. "What 32 | does the conference expect from talks?" Let's engage with the community 33 | directly because it's a community conference. 34 | - Jeff: GraphQL has an identity crisis - it's getting used in more and more 35 | places, and we're uniquely positioned to define its identity. 36 | - Jem: I've ended up being a community builder at Graphile and want to learn 37 | from other community leaders; I also help organize GraphQL London and am 38 | looking to formalize and document this process and help people access the 39 | support that the GraphQL Foundation has. 40 | - Martin: I work with Jeff in the Apollo client team. I organize the Paris 41 | Android meetup and love building communities. I think we can do a lot more on 42 | the GraphQL front - would love to see GraphQL Paris grow. Hoping to get 43 | Stroopwafels for GraphQLConf in Amsterdam this year! 44 | - Uri: To add transparency and to empower the community. You should be able to 45 | just join and help. It's also great fun to talk with GraphQL folks! Valuable 46 | to hear the different opinions and perspectives. Hopefully bring more energy 47 | to our community and GraphQL. Discuss channels and meetups. Discussing other 48 | projects that GraphQL is working on - not just the technical parts. Also 49 | communicating with other communities: REST, gRPC, OpenAPI, etc. Great way to 50 | put out content on case-studies - how GraphQL was successful in companies. 51 | Almost every popular app is using GraphQL, and yet people aren't aware of 52 | that. 53 | - Doc: especially communicating with other communities. There's a vast 54 | community of people who aren't software engineers, they're strictly from 55 | data. E.g. ocean health; lots of datasets, metadata, APIs. These folks might 56 | end up using GraphQL without any idea what's going on on the technology 57 | side. E.g. there's an example of in-memory GraphQL used for managing 58 | metadata - really fascinating! Cryptocurrency community also use GraphQL a 59 | lot, but we don't have much of a connection there. Lots of opportunities. 60 | Helping people be aware of all of the use-cases for GraphQL out there. AI 61 | and knowledge graphs also has a lot of opportunities for GraphQL. 62 | - Pascal: connecting with AI communities; GraphQL is really useful for them. 63 | - Benjie: There was a great talk at GraphQL London about AI. Good callout 64 | - Benjie: Grease the wheels of collaboration. Champion using GraphQL for the 65 | smaller use cases. I love to see GraphQL used in lots of different ways. I 66 | want to especially represent the smaller companies. GraphQL is broadly useful 67 | from small startups up to big enterprises. Inform people: counter the 68 | misinformation that exists. 69 | - Doc: Like this a lot. A lot of places do start small and it doesnt get to 70 | the size like netflix 71 | - Pascal: in the .NET ecosystem the misinformation about GraphQL is one of the 72 | main problems. Most of our customers come from the backend, and we feel it 73 | should be driven more by the frontend. There's a lot of people who deny that 74 | GraphQL is useful and often have arguments that don't make sense because 75 | they don't know the technology - often consulting with companies leads to 76 | realisations that it doesn't have to be hard. You don't need all the various 77 | complexities like federation/etc - you can just start with basic GraphQL, 78 | how it was originally intended. 79 | - Saihaj: most of my thoughts have already been covered. We need transparency. 80 | We need to counter misinformation. 81 | 82 | ## Check for ready for review agenda items (5m, Host) 83 | 84 | - Uri: we don't need to decide all the goals on this call; we can keep 85 | brainstorming and even discuss asynchronously. We can put tasks/issues on the 86 | GitHub for the WG, and then during the meetings we can look over the topics 87 | discussed asynchronously. 88 | 89 | ## General discussion 90 | 91 | - Doc: To Uri, Saihaj, Michael: on the topic of openness. Do you have ideas on 92 | what this openness would look like? 93 | - Uri: this group is part of making it more transparent. You and I used to 94 | discuss things in the context of the foundation which means that many people 95 | didn't have access to it. Letting anyone join the meetings is a big step 96 | towards openness. 97 | - Saihaj: I'll summarise this and then put out bullets on things that we could 98 | vote on to see what we care about. 99 | - Martin: will be using this to organize GraphQLConf? 100 | - Uri: the Foundation has dedicated meeting for that already that already has 101 | a good structure. 102 | - Benjie: 103 | - Community can help with content, ideas… Keynote speaker suggestions. Topics 104 | we'd like to see. Bringing agreed suggestions to the GraphQL Foundation. 105 | - Jem: GraphQL stars were a good example of something where the community could 106 | help 107 | - Uri: Anyone can open issues on the GitHub repo. Monthly + extra meeting works 108 | great. 109 | - Erik: chat channel? Make a discord channel? 110 | - Doc: When adding yourself to an agenda, can you also add an agenda item? 111 | - Uri: Yes, this is how the other working groups work 112 | - Doc: How do we collaborate across groups? 113 | - Uri: You can go on GraphQL github and see all the other working groups there 114 | - Uri: there is no specific working group for the website, perhaps this group 115 | should be a good place for that, and we can spin it off later if needed 116 | - Doc: is there a budget for the GraphQL foundation? 117 | - Uri: let’s discuss in a GitHub issue 118 | -------------------------------------------------------------------------------- /notes/2025/2025-03.md: -------------------------------------------------------------------------------- 1 | # Community WG Notes - March 2025 2 | 3 | **Watch the replays:** 4 | [GraphQL Working Group Meetings on YouTube](https://www.youtube.com/playlist?list=PLP1igyLx8foHhWZk2u1SthsW1weH3VA7l) 5 | 6 | Agenda: 7 | [https://github.com/graphql/community-wg/blob/main/agendas/2025/03-Mar/13-community-working-group-march-2025.md](https://github.com/graphql/community-wg/blob/main/agendas/2025/03-Mar/13-community-working-group-march-2025.md) 8 | 9 | ## Review agenda (2m, Host) 10 | 11 | - A lot of communication has happened offline, this is good 👍! 12 | - Benjie is working on getting Zoom AI note taking in the meetings 13 | - We are not using “ready for review” yet but we probably should. 14 | - Doc has done a summary of the issues: 15 | - https://github.com/graphql/community-wg/issues/50 16 | - Moved Discord topic to end 17 | - Plan to circle back to agenda summary 18 | 19 | ## Align on main goals for the working group (15m, Urigo) 20 | 21 | - Uri: 22 | [https://github.com/graphql/community-wg/issues/28](https://github.com/graphql/community-wg/issues/28) 23 | - 1. Broaden GraphQL's appeal and adoption (Doc: "Awareness and Adoption") 24 | - Growth isn't where we want it to be 25 | - People aren't aware of how GraphQL could benefit them 26 | - 2. Unblock and empower community initiatives 27 | - 3. Foster a transparent community 28 | - From Doc's summary: 29 | - Ambassador program 30 | - How to announce/invite people 31 | - Doing a survey 32 | - Grouping: 33 | - Growing community 34 | - Communication 35 | - e.g. pilot with Slack 36 | - Support activities 37 | - How to support GraphQLConf 2025 38 | - Building local meetups 39 | - Uri: meetups fits under broadening community, and unblocking/empowering 40 | community initiatives 41 | - Benjie: suggest renaming point 3 to "Fostering transparency with the 42 | community" for clarity 43 | - Doc: a survey would help with this, ensuring we're hitting the right targets 44 | - Martin: they look good; do we need to commit to these, or can we change them 45 | as we discover new things. 46 | - Uri: these are our "modest principles for start" 47 | - An: Is the objective more: "To lower the barrier to join an inclusive GraphQL 48 | community"? 49 | - Doc: How did you find this meeting? 50 | - An: Uri contacted me. 51 | - Erik: It can be intimidating, some people might be afraid by our agendas and 52 | leave it to “the experts” 53 | - Erik: Would be cool to have folks attend more casually if they want to. 54 | - Benjie (in chat): we need to define what we mean by community (is it 55 | contributors, ambassadors, meetups, …) 56 | - Jeff: we've dozens of people who attend the working groups. We have a 57 | significant proportion of the internet users who use GraphQL via apps, 58 | billions. We've the community of people who write frontend apps, actually 59 | writing GraphQL queries. We've the community of people writing GraphQL clients 60 | that these developers user. 61 | - We want more spec writers. We want more people talking about GraphQL. These 62 | are all goals, huge goals, depending on which level we zoom in at. Maybe we 63 | need to zoom in on "personas" - who are the people that we're serving. This 64 | may help us speak to the needs of those folks - is it the spec? is it the 65 | tools? best practices? 66 | - Erik: personas are crucial to any technology you're trying to get out there. 67 | Asking maintainers if they've heard of the new spec features or not yet. We'd 68 | benefit from pulling more people under the common mission; fostering 69 | connections for feedback. 70 | - Doc: some personas mentioned include enterprise users vs developers. We need 71 | consensus at the top level, then we can bear down into more detail into how to 72 | execute. With community, you generally have 20% active, 80% lurking - they 73 | want to be informed, but don't want to or can't engage. The more activities we 74 | do to support these objectives (surveys, local groups), first we should grow 75 | _this_ group. 76 | - {General consensus is reached regarding the three objectives} 77 | - (Daniel) We have a few thousand developers across Asia, at GQL Taipei, GQL 78 | BKK, GQL Singapore & GQL Indonesia GQL Hong Kong, would love to see these 79 | communities grow. In all cities we have willing host offices. 80 | 81 | ## Align on how to manage initiatives (ideas, actions, champions, stages and tracking progress) (10m, Urigo) 82 | 83 | - This is more a topic of _how_ we work. 84 | - More meetings is an option. 85 | - Can we focus our discussions on things that are ready for discussion? 86 | - A lot of discussions and progress happen on the issues themselves. 87 | - Then we bring it to the WG for discussion. 88 | - A champion brings it because they're either blocked (need more input, need a 89 | decision, etc) or to give a status update. 90 | - If no-one's working on something, taking responsibility for it/championing 91 | it - we can talk for hours about how awesome it would be, but if no-one's 92 | doing it, there's no point. 93 | 94 | ## Making progress on the website redesign (5m, Urigo) 95 | 96 | - [https://github.com/graphql/community-wg/issues/21](https://github.com/graphql/community-wg/issues/21) 97 | - For many years we've wanted a redesign of the website. 98 | - There's many reasons it hasn't happened; but we now have the chance to do it. 99 | The main blocker was defining what we want the main page to say. 100 | - I've summarised what we might want here: 101 | [https://github.com/graphql/community-wg/issues/21](https://github.com/graphql/community-wg/issues/21) 102 | - I want a message that is better than what we have today (doesn't need to be 103 | perfect). The Guild maintains the website (but welcomes contribution and tries 104 | to make it as easy as possible!). We suggest that we hire a designer based on 105 | this input, and then The Guild will implement the design. 106 | - Doc: Meena and I have submitted PRs to the website. I hope it remains as 107 | flexible as it is now. If we go out to the community with meetups/etc we'll 108 | get more information about what the community _needs_ the website to do. Doing 109 | it in stages gives us a chance to receive and react to feedback. We can be 110 | guided by analytics. The 2023 conference site was beautiful and amazing. The 111 | LF tool for the conf schedule in 2024 was not amazing. I'm hoping you do the 112 | 2025 conference site! 113 | - Uri: getting info from the community will improve the community, agree. Many 114 | of us interact with the community and have a sense of what is needed. 115 | - (chat) Saihaj: Nothing in the infra or how you contribute will change. This is 116 | just content/messaging + design 117 | - Uri: we'll continue to continuously change based on feedback. The new design 118 | is just a point in time that expresses the improvements we want to make now, 119 | but we can change it the very next day. We need data on growth, usage, 120 | - Doc: automating/publishing the metrics from the website would be very helpful 121 | - Uri: the LF team sometimes send links out to their tool 122 | - Erik: recommend that we do a prototype without design first, apply them to the 123 | personas, and once we're happy then get the design done. Content strategy 124 | first. 125 | - Uri: I'm happy to work on this, any feedback or any help is welcome. 126 | 127 | ## How to involve the community in GraphQL conf organization? (15m, Martin, All) 128 | 129 | - Where is help needed? 130 | - Can community members be involved in T Shirt design? 131 | - Can the conference committee invite Martin? 132 | - Doc and Martin both very excited to be able to attend a local EU conference 133 | rather than in the US 134 | 135 | ## Host monthly wg meetings as a live stream. (Use foundation's YouTube channel) (5 to 10m, Doc, All) 136 | 137 | - A GitHub issue is going to be opened to discuss this further 138 | - The monthly community working groups can become more of a status update 139 | livestreamed, rather than in depth conversations 140 | 141 | ## Make the Discord channel public? (5m, All) 142 | 143 | - #44 144 | -------------------------------------------------------------------------------- /rfcs/ambassador-program/standards-of-excellence.md: -------------------------------------------------------------------------------- 1 | ## GraphQL Ambassador Program Standards of Excellence 2 | 3 | While the wider GraphQL community abides by the 4 | [contributor covenant code of conduct](https://graphql.org/codeofconduct/), a 5 | stronger set of standards is used for the Ambassador Program. This is because 6 | the Foundation endorses Ambassadors as representatives and leaders; the 7 | Standards of Excellence are designed to provide a set of guidelines and best 8 | practices for engaging with the GraphQL Foundation and broader community. This 9 | makes it easier for Ambassadors to contribute to a positive culture by providing 10 | clarity around what and how we create a safe and collaborative environment. 11 | 12 | ### Scope 13 | 14 | If you are a GraphQL Ambassador, these Standards apply to you. This means they 15 | apply to your statements and actions in your capacity as a GraphQL Foundation 16 | representative, whether they occur online or offline, and whether they occur 17 | within community spaces or outside of community spaces. 18 | 19 | In addition to complying with these Standards of Excellence, GraphQL Ambassadors 20 | are also required to comply with the GraphQL Code of Conduct and the Linux 21 | Foundation Events Code of Conduct, and all other applicable GraphQL Foundation 22 | policies, rules, or guidelines. 23 | 24 | ### Be Kind, Welcoming, and Inclusive 25 | 26 | - Be kind to others. 27 | - Promote a friendly atmosphere where people feel comfortable asking questions, 28 | participating in discussions, and making contributions. 29 | - Show gratitude and appreciation for others. Look for opportunities to say 30 | “thank you” and recognize people when they are being helpful or making 31 | contributions. 32 | - Make a conscious effort to welcome and be inclusive of newcomers and people 33 | who are different from you. 34 | - Show empathy, care, and concern for others’ feelings, perspectives, and 35 | experiences. 36 | 37 | ### Be Respectful and Professional 38 | 39 | - At all times, conduct yourself in a manner that is appropriate for a 40 | professional environment. 41 | - Always treat others with courtesy and respect. Rude, insulting, offensive, 42 | disparaging, or threatening statements or behaviors are not permitted. 43 | 44 | ### Handle Disagreements Respectfully 45 | 46 | We want to encourage the candid exchange of ideas and feedback and foster an 47 | environment in which people can openly agree or disagree with each other, so 48 | long as they do so respectfully. Disagreements are not an excuse for bad 49 | behavior. As a GraphQL Ambassador, you are expected to: 50 | 51 | - Respond to differences of opinion in a respectful manner. 52 | - Make a conscious effort to understand other people’s perspectives and learn 53 | the facts before you publicly take a stand on any highly controversial issue. 54 | - Seek to resolve conflict and disagreement in a respectful and collaborative 55 | manner and encourage others to do the same. 56 | 57 | ### Promote and Enhance the GraphQL Brand 58 | 59 | As a GraphQL Ambassador, part of your role is to promote and enhance the GraphQL 60 | brand and contribute to goodwill and positive relations among the Foundation and 61 | others in GraphQL ecosystem. Nonetheless, you can be honest and candid with 62 | constructive criticism, holding others accountable, identifying opportunities 63 | for improvement, and discussing potential challenges. However, always express 64 | yourself in a manner that is respectful and professional, and strive to also be 65 | tactful and sensitive to how your words may impact others. See the “Be Graceful 66 | With Feedback” section below for suggestions on how to deliver feedback 67 | constructively and kindly. 68 | 69 | As a GraphQL Ambassador, your actions can reflect either positively or poorly on 70 | the GraphQL community, Foundation, and brand. Therefore, engaging in activity 71 | that is illegal, immoral, fraudulent, deceptive, or is otherwise likely to 72 | damage the reputation of the GraphQL community, Foundation, or Ambassador 73 | Program, is grounds for immediate suspension or removal from the GraphQL 74 | Ambassador Program. 75 | 76 | ### Don’t use GraphQL community spaces or your role as an Ambassador to promote political causes 77 | 78 | Your role as a GraphQL Ambassador is to be used for the purpose of evangelizing 79 | GraphQL and otherwise contributing to the GraphQL community and ecosystem. Both 80 | the GraphQL Code of Conduct and these Standards of Excellence prohibit use of 81 | GraphQL community spaces for political campaigning or promotion of political 82 | causes that are unrelated to the advancement of GraphQL technology. 83 | 84 | Outside of GraphQL community spaces, you are free to engage in political 85 | activities and support causes you choose. However, when you discuss political 86 | causes that are unrelated to GraphQL, please keep those discussions separate 87 | from your engagement in GraphQL and separate from your role as a GraphQL 88 | Ambassador. For example, if you choose to promote a political cause unrelated to 89 | technology on X or LinkedIn in your personal time, please do so in posts and 90 | discussion threads that are separate from GraphQL-related discussions. 91 | 92 | ### Be Graceful With Feedback 93 | 94 | - Giving others kudos and recognition is a great way to contribute to a positive 95 | environment. Therefore, feel free to share positive feedback in both public 96 | and private forums. 97 | - When it comes to negative feedback or criticism, remember that none of us are 98 | perfect. We all make mistakes. Most people are good people who are trying to 99 | do good things. Therefore, when others make mistakes, strive to be 100 | understanding. When you make a mistake, take responsibility and do your best 101 | to learn and improve. 102 | - Always share feedback or criticism in a respectful, courteous, and 103 | professional manner. Additionally, always strive to present negative feedback 104 | or criticism in a constructive manner (e.g. as suggestions for improvement) 105 | rather than a destructive manner (e.g. insults or degrading language). 106 | - When you have negative feedback or criticism about an individual (other than a 107 | public figure), please share it privately to help the individual learn and 108 | grow. Please avoid sharing negative feedback or criticism about an individual 109 | (other than a public figure) publicly, because this could cause unnecessary 110 | shame, embarrassment, or humiliation. 111 | - When you have negative feedback or criticism about an organization or public 112 | figure, you may share it publicly or privately, so long as you do so in a 113 | respectful, courteous, and professional manner. 114 | 115 | ### Consequences for Violation 116 | 117 | If the GraphQL Foundation determines that a GraphQL Ambassador has violated 118 | these Standards of Excellence, or if a GraphQL Ambassador has been found in 119 | violation of the GraphQL Code of Conduct or the Linux Foundation Events Code of 120 | Conduct, the GraphQL Foundation, at its sole discretion, may take any action 121 | that it deems appropriate under the circumstances, including asking the GraphQL 122 | Ambassador to remove offending content from community spaces or public spaces, 123 | or suspending or removing the individual from the GraphQL Ambassador Program. 124 | 125 | ### Questions and Reporting 126 | 127 | If you have questions about these Standards of Excellence, or if you would like 128 | to report a potential violation, please send an email to [insert email address] 129 | and the current community manager will contact you. We will respond promptly to 130 | all questions and reports. 131 | 132 | ### Updates 133 | 134 | The GraphQL Foundation reserves the right to modify these Standards of 135 | Excellence at any time, at its sole discretion. The GraphQL Foundation will 136 | notify GraphQL Ambassadors of major changes to the guidelines by email [and via 137 | the GraphQL Ambassador Discord channel]. However, any changes to these 138 | guidelines will not apply retroactively. If these guidelines are updated and a 139 | GraphQL Ambassador does not wish to agree, their participation in the GraphQL 140 | Ambassador Program will cease until such time as they do agree. 141 | -------------------------------------------------------------------------------- /rfcs/ambassador-program/overview-for-organizers.md: -------------------------------------------------------------------------------- 1 | ## GraphQL Ambassador Program 2 | 3 | The following is an overview of the proposed GraphQL Ambassador Program for the 4 | organizers (the Foundation, community working group and other interested 5 | parties) outlining the goals, outcomes and tasks of the program. 6 | 7 | ### Ambassador Initiative Goals 8 | 9 | The overarching goal is to increase GraphQL adoption. The Ambassador Program 10 | aims to accomplish this through: 11 | 12 | - Brand advocacy - developers organically vouch for and promote GraphQL 13 | - Social proof - named individuals with high visibility (and a proportion from 14 | known corporate brands) as Ambassadors 15 | - Increased GraphQL content online and off 16 | - Community building - increasing the number of “known faces” within GraphQL, 17 | increased approachability and a welcoming environment to spread knowledge 18 | about GraphQL 19 | 20 | There are also benefits to the Ambassador: 21 | 22 | - Professional recognition as a GraphQL expert 23 | - Access to other GraphQL experts, both in their local community and online 24 | - Closer relationship with the GraphQL Foundation & project, including 25 | up-to-date news and insights on upcoming Specification edits and working group 26 | topics 27 | 28 | ### Ambassador Requirements 29 | 30 | - Highly knowledgeable about GraphQL and readily able to articulate those ideas 31 | - Be a model community member: Adhering to the standards of excellence 32 | especially when critical of GraphQL or defending it to others criticism, 33 | remaining respectful, constructive and fair 34 | - Do not come across to other community members as selling another product, 35 | service or agenda when acting as an ambassador 36 | - Already participating in one or more of the Ambassador Tasks outlined below 37 | - Agree to have their face, name, chosen socials and other relevant information 38 | displayed on the "people"/"ambassadors" page 39 | 40 | ### Ambassador Tasks 41 | 42 | GraphQL Ambassadors will be an important touchstone for people interested in 43 | GraphQL to learn more about it in a friendly and constructive way. 44 | 45 | They will do four or more ambassador tasks throughout their one year term. They 46 | can do the same task four times, or a mixture of tasks. 47 | 48 | Ambassador tasks include: 49 | 50 | 1. **Community Leadership** 51 | - Local Gathering organizer 52 | - Program committee member for a GraphQL focused event 53 | - Organize GraphQL related events 54 | - Mentorship hours 55 | - GraphQL Foundation community Discord moderation 56 | 1. **Public Speaking** 57 | - Speaking at industry or GraphQL Foundation events about GraphQL or GraphQL 58 | projects 59 | 1. **GraphQL Focused Content Creation** 60 | - Producing written content, both on GraphQL Foundation platforms and in 61 | other places 62 | - Have written a GraphQL focused book 63 | - Producing video and/or audio content, either on GraphQL Foundation 64 | platforms or in other places 65 | - Building demo apps 66 | 1. **Active Contribution to a GraphQL Foundation Project or Specification** 67 | - Have served on the Technical Steering Committee 68 | - Have actively maintained a GraphQL project or reference implementation 69 | - Attendance at the GraphQL working group or sub-working groups 70 | 1. **Maintainer or A Main Contributor of a Key Open-Source GraphQL Related 71 | Project** 72 | - For example, GraphQL implementations 73 | 1. **Outreach for GraphQL Foundation initiatives** 74 | - Discussion and guidance helping a non-Foundation project to adopt, test 75 | and provide feedback on a GraphQL Specification proposal 76 | - Organizing a venue for a GraphQL Local 77 | - Media outreach with a measurable impact eg publication in a major tech 78 | outlet or mainstream media 79 | 80 | ### What the Foundation offers 81 | 82 | - Quarterly meeting with Foundation / TSC reps to give updates about the general 83 | direction of the project and an opportunity for Q&A 84 | - 15 minute presentation-style 85 | - followed by Q&A 86 | - time also allowed for the Foundation / TSC reps to ask for the Ambassadors' 87 | feedback on the current directions of the GraphQL project, be that technical 88 | (eg Specification RFCs), or community initiative focused 89 | - Promotion of the Ambassador as a go-to GraphQL community leader 90 | - Website profile 91 | - Biographies / interviews with each Ambassador 92 | - Credly badge 93 | - An Ambassador role on the community Discord and an associated private channel 94 | for networking and discussions with Foundation / TSC / community reps 95 | - Promotion of Ambassador material - conference talk videos and created content 96 | - Exclusive GraphQL swag eg Ambassador hoodie 97 | - Free GraphQL Foundation Conference ticket 98 | - Ambassadors may apply for travel funding to approved conference & meetup 99 | talks, applications to be evaluated on a case-by-case basis 100 | - An honorarium available for content creation on a case-by-case basis 101 | 102 | ### Ambassador Standards of Excellence 103 | 104 | While the wider GraphQL community abides by the 105 | [contributor covenant code of conduct](https://graphql.org/codeofconduct/), 106 | stronger set of standards is needed for the Ambassador Program. This is because 107 | the Foundation will be endorsing these people as representatives and experts. We 108 | can look to the 109 | [CNCF Ambassador Program Standards of Excellence](https://www.cncf.io/people/ambassadors/program-standards/) 110 | as a good indicator of what this should be. The beginnings of a document is 111 | here, see [standards-of-excellence.md](./standards-of-excellence.md) 112 | 113 | ### Process 114 | 115 | #### Application Process 116 | 117 | Yearly program 118 | 119 | - 1 year term 120 | 121 | - Applications open year round 122 | - Applications received by a group email address and should be acknowledged 123 | swiftly 124 | - Applications to be considered by TSC members, select Foundation members and 125 | select community working group members. Once we have the first cohort of 126 | Ambassadors accepted, Ambassadors themselves can also consider the 127 | applications. 128 | - Applicants need at least one approval, any objections are to be 129 | investigated. 130 | - A new wave of Ambassadors announced quarterly. The first announcement we are 131 | hoping can coincide with the GraphQL Conference in September 2025. 132 | 133 | - Applications can be from the prospective Ambassador or a nomination from a 134 | community member. 135 | - Foundation members will be asked to nominate an Ambassador from within their 136 | organization, and to nominate a second Ambassador from outside their 137 | organization 138 | - TSC members will be invited to apply when they are welcomed to the TSC 139 | - The Ambassador term is a year long, Ambassadors who continue to meet the 140 | expectations will be invited to join again at the end of their term 141 | 142 | #### Removal of an Ambassador 143 | 144 | - The Ambassador term is a year long, this gives a natural end to a person's 145 | Ambassador role 146 | - If the Ambassador is found to be breaking the 147 | [standards-of-excellence.md](./standards-of-excellence.md), the GraphQL Code 148 | of Conduct or the Linux Foundation Events Code of Conduct, the Ambassador role 149 | may be removed before the end of their term. The Ambassador Program organizers 150 | will engage with the Linux Foundation for this process as needed. 151 | 152 | #### Travel expenses 153 | 154 | - Wait for the talk to be accepted through the meetup CfP process 155 | - Review the talk proposal to ensure alignment with the Program 156 | - Can the payment be made beforehand rather than in arrears? 157 | 158 | #### Honorarium for content creation 159 | 160 | - Ambassador applies for an honorarium each time, in a process similar to the 161 | Community Grant 162 | - There will be a maximum yearly amount available, paid from the Marketing 163 | budget 164 | - We should publish a guide to the amounts available (once this is agreed) 165 | - A revision process is expected 166 | 167 | ### Offboarding and Alumni Network 168 | 169 | Upon completing a successful term, Ambassadors join our Alumni Network: 170 | 171 | - Continued Ambassador Discord channel to answer questions from new Ambassadors. 172 | - Priority CFP notifications for GraphQL Foundation events 173 | - Annual Alumni spotlight blog series 174 | - What else to include here? 175 | --------------------------------------------------------------------------------