Update requirements and wording of the locals page #2166
Conversation
martinbonnin
commented
Oct 3, 2025
martinbonnin
commented
- Move video recording to a soft requirement: photos are ok if video is not possible
- Explain why there is a requirement for a TSC representative to be an organizer
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
For Instead of only TSC representative, to include GraphQL Ambassadors as representative as part of the GraphQL local organisation? |
TSC is more stable IMO (there's a 2 years commitment) and shouldn't go "missing in action". I would stick with that unless we have a hard time recruiting them. |
|
That being said, I'm not sure what the current status. Looks like most of the locals don't have a TSC representative in their org anyways so if adding Ambassadord makes it so that we actually do what we say we should do, then I'm all for it.3 |
|
Ok, I'm convinced ^^, I've added Ambassadors (ping @jemgillam ) |
Every official GraphQL Local has a TSC representative in their org, it's one of the requirements.
We're softening the requirements (e.g. for recordings) to encourage more meetups to become official GraphQL Locals. We expect that many of the people who run Locals will become Ambassadors, but for the continuity of the group it's best if an official TSC member has admin access so they can add new organizers in the case of someone going non-contact. Partly it's to address bus-factor. |
|
Right! This is the GraphQL foundation account, right? What about:
|
|
The official meetup account costs something silly like £30/mo/meetup; for groups using that we cannot offer sponsorship (since the funds are already spent on meetup), so it shouldn’t be the recommended approach. Instead a TSC member should be added to whatever platform they use. |
Clarified requirement for TSC member administrator access.
Ah yes, I remember that discussion now, bummer... I've reverted to just TSC members now. |
- [x] Seeking approval at GraphQL Governing Board. - Fixes graphql#2166 --- Since launching the **GraphQL Local Initiative** last year, communities around the world have been gathering to share knowledge, collaborate, and strengthen their local GraphQL ecosystems. Over the past year, we’ve seen: - **GraphQL London** hosting three or four events a year — with another due in November - **GraphQL Sydney** diving into hot topics like GraphQL nullability - **GraphQL Berlin** meeting the day after GraphQLConf 2025 concluded in Amsterdam, requiring quick travel for Stephen and Michael! - **GraphQL Hyderabad** celebrating a fantastic first meetup - **GraphQL Austin** forming over ramen to plan a new series of events - **GraphQL Paris** and **GraphQL Oslo** preparing to meet later this month We also have local organizers working to bring people together in **Białystok**, **Philadelphia**, **Chennai**, **Belgium**, and more locations! ## We’ve heard you Feedback from organizers and attendees has been clear, so we're launching our 2025 refresh of the Locals program: - **Simpler applications:** Videos are no longer required — photos can substitute where needed - **More flexible events:** Locals can now host more than just talks — discussions, workshops, hackathons, Q&As, live recordings, and more are now eligible for support - **Increased sponsorship:** Support per event has doubled, from **USD $200** to **USD $400**, to help with food, drinks, and venue costs - **Clearer TSC oversight:** Independent meetups often die when the organizer steps down; by appointing a GraphQL TSC member as an admin, we can help ensure the continuity of the community over the long term These updates come directly from your feedback. You’re building something amazing, and we want to support you! ## Get involved Want to attend or start a GraphQL Local in your city? Find your nearest group or apply to start one on the [GraphQL Local Initiative page](/community/foundation/local-initiative). Together, we’re building a global network of local communities — sharing ideas, growing connections, and keeping GraphQL vibrant everywhere. --------- Co-authored-by: Martin Bonnin <[email protected]>
3 participants
