|
| 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) |
0 commit comments