How (not) to run a Graphql Stewardship Group
summary
Describes creating a GraphQL stewardship by building a small core contributors team aligned with an enabling team, using a GitHub contributions board and Slack for tracking, and running it experimentally for one quarter to six months to decide if it adds value. Focus is on concrete goals, moderation to surface quiet voices, and prioritizing cross-team reusable fixes over low‑level ticket triage. Outcome: it sustains baseline engagement, produces reusable schema changes, and requires visible leadership buy-in to scale.
AI-written summary · about
chapters (7)
- 0:00GraphQL stewardship intro
- 3:46Why GraphQL stewardship matters
- 7:26Starting a stewardship group
- 12:23Setting stewardship goals
- 15:13Moderation and collaboration
- 18:26Keeping stewardship engaging
- 20:36Leadership support impact
related talks
27mPanel - Championing Your Supergraph After Launch, Now What?
44mPanel - Graph Leadership - Scaling the Graph Across Your Org and Platform
16mKeynote: GraphQL’s Next Chapter: Progress, Proposals, and Participation
35mA Wild GraphQL Rollercoaster Ride a Federated GraphQL Adoption Story
39mScaling an Open Source Sponsorship Program
19mThe secrets to Graph success, from inception to general availability.
21mLeading and Growing an Open Source Comunity
28mBuilding Open Source Communities