If you're interested in this spec and helping contribute to it, you can get involved with the following steps:
- Read the Roadmap which outlines the planned development of this spec.
- See Agendas for upcoming meetings of the GraphQL-over-HTTP working group.
- Add yourself to
List of Developersbelow.
This list helps us keep track people that are interested in taking decisions of the specification of GraphQL over HTTP.
If you want to be listed here, open a PR with your information, just order yourself by name.
- @benjie
- Company/Project/Repo: https://github.com/graphql/graphiql, https://github.com/graphile/postgraphile
- Reason: Interested in a common HTTP spec
- @deinok
- Company/Project/Repo: https://github.com/graphql-dotnet/graphql-client
- Reason: Interested in client/server on C# stack
- @erikwittern
- Company/Project/Repo: https://github.com/graphql/libgraphqlparser, https://github.com/IBM/openapi-to-graphql
- Reason: Interested in client/server in JavaScript/C++
- @jaydenseric
- Company/Project/Repo: https://github.com/jaydenseric/graphql-multipart-request-spec
- Reason: Interested in multipart request spec
- @michaelstaib
- Company/Project/Repo: https://github.com/ChilliCream/hotchocolate
- Reason: Interested in client/server in JavaScript/C++/C#
- @mike-marcacci
- Company/Project/Repo: https://github.com/boltline
- Reason: Interested in client/server spec
- @mmatsa
- Company/Project/Repo: https://github.com/graphql/libgraphqlparser
- Reason: Interested in client/server in C++
- @sjparsons
- Company/Project/Repo: PayPal & Braintree https://github.com/sjparsons
- Reason: Interested in common spec
- @spawnia
- Company/Project/Repo: https://github.com/nuwave/lighthouse
- Reason: Interested in client/server in PHP
- @sungam3r
- Company/Project/Repo: https://github.com/graphql-dotnet/server
- Reason: Interested in client/server spec
@benjie @deinok @erikwittern @jaydenseric @michaelstaib @mike-marcacci @mmatsa @sjparsons @spawnia @sungam3r