Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: "Issue club" #1673

Open
martinbonnin opened this issue Feb 28, 2025 · 0 comments
Open

Proposal: "Issue club" #1673

martinbonnin opened this issue Feb 28, 2025 · 0 comments

Comments

@martinbonnin
Copy link
Contributor

martinbonnin commented Feb 28, 2025

As there is more and more activity and topics being discussed in the working groups, it is sometimes hard for the community to catch up with everything that's happening in the GraphQL world.

This is a proposal to run a dedicated "Issue club" meeting to go over the issues, close them, ask for clarification when needed and ensure they are correctly labeled.

The process is a bit tedious but from experience has lots of value in terms of how it allows to nurture a community and make the projects overall look more approachable.

It's also a good way for more active contributors to get a "vibe check" of what's currently happening.

For starters, I would suggest:

  • a 1h quaterly review
  • covering both graphql-wg and graphql-spec.

Individual working groups (nullability, http, incremental delivery, etc...) would stay separate.

We could also decide to run this as part of the monthly meetings (although that may take a good chunk of them).

Thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant