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. Given our world-wide span over many timezones, we are doing an experiment of attempting to advance the spec with fewer meetings and more asynchronous communication. During this experiment, please reach out over Discord and GitHub.
- Add yourself to
List of Developersbelow. - Find our working group on the GraphQL Foundation Discord community in the #graphql-over-http channel.
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 username.
- @abernix
- Company/Project/Repo: https://github.com/apollographql/apollo-server, https://github.com/apollographql/apollo-client
- Reason: Interested in client/server spec
- @balshor
- Company/Project/Repo: https://github.com/linkedin
- Reason: Interested in a common HTTP spec
- @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
- @enisdenjo
- Company/Project/Repo: https://github.com/domonda, https://github.com/bhidapa, https://github.com/enisdenjo/graphql-ws
- Reason: Interested in a common subscriptions spec
- @erikwittern
- Company/Project/Repo: https://github.com/graphql/libgraphqlparser, https://github.com/IBM/openapi-to-graphql
- Reason: Interested in client/server in JavaScript/C++
- @fredrick
- Company/Project/Repo: https://github.com/atlassian
- Reason: Interested in a common HTTP spec and common subscriptions spec.
- @ghmcadams
- Company/Project/Repo: https://github.com/ghmcadams
- Reason: Interested in a common HTTP spec
- @glennblock
- Company/Project/Report: https://github.com/microsoft
- Reason: Interested in a common HTTP spec, and in adoption of emerging HTTP standards like HTTP SEARCH
- @hemanth
- Company/Project/Repo: PayPal https://github.com/hemanth
- Reason: Interested in a common HTTP spec and common subscriptions spec.
- @jaydenseric
- Company/Project/Repo: https://github.com/jaydenseric/graphql-multipart-request-spec
- Reason: Interested in multipart request spec
- @JoviDeCroock
- Company/Project/Repo: Stellate https://github.com/urql-graphql/urql
- Reason: Interested in a common HTTP/subscriptions spec
- @maraisr
- Company/Project/Repo: https://github.com/maraisr/meros
- Reason: Interested in common incremental delivery 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++
- @shane32
- Company/Project/Repo: https://github.com/graphql-dotnet/server
- Reason: Interested in a common HTTP spec and common subscriptions spec
- @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
- @touchstone117
- Company/Project/Repo: https://github.com/amplience, https://github.com/touchstone117
- Reason: Interested in a common HTTP spec
@abernix @balshor @benjie @deinok @erikwittern @jaydenseric @michaelstaib @mike-marcacci @mmatsa @shane32 @sjparsons @spawnia @sungam3r @touchstone117 @enisdenjo @JoviDeCroock