From 55cd358a0821f192684d443478a687fe46222975 Mon Sep 17 00:00:00 2001 From: Martin Bonnin Date: Thu, 7 May 2026 11:01:54 +0200 Subject: [PATCH 1/6] Add project adoption guidelines --- src/pages/community/contribute/development.mdx | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/src/pages/community/contribute/development.mdx b/src/pages/community/contribute/development.mdx index b98fb1630d..99f2785cf5 100644 --- a/src/pages/community/contribute/development.mdx +++ b/src/pages/community/contribute/development.mdx @@ -71,6 +71,20 @@ The best place to ask a development-related question is in a working group meeti ]} /> +## Project adoption guidelines + +The `graphql` GitHub organization is the home for projects that hold a unique role in the ecosystem: specifications, test suites, reference implementations, documentation sites, etc. + +Except for `graphql-js` as a reference implementation, GraphQL implementations in different languages are encouraged to stay in separate organization. This helps folstering ecosystem diversity. + +General guidelines: + +* The project should be using an opensource license. +* The project should be actively maintained. +* The project should hold a unique role in the ecosystem. + +To request adding a new project, please open [an issue is the `graphql-wg`](https://github.com/graphql/graphql-wg/issues/new) repository. Project adoption is [decided by the TSC](https://github.com/graphql/graphql-wg/blob/main/GraphQL-TSC.md#decision-making-authority). + If you want to get involved in GraphQL, add yourself to the meeting agenda for one of our [working groups or implementations](./project-meetings/#quick-guide-how-to-join), sign the document if you haven't already, and show up! Or, if you prefer, just open a PR against our projects as this will also initiate the spec membership signature process. We welcome your participation! From 8214e51539f441cc584062f0c1b7c3bd2b6a23c6 Mon Sep 17 00:00:00 2001 From: Martin Bonnin Date: Thu, 7 May 2026 11:16:42 +0200 Subject: [PATCH 2/6] typos --- src/pages/community/contribute/development.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/pages/community/contribute/development.mdx b/src/pages/community/contribute/development.mdx index 99f2785cf5..fe43a9b400 100644 --- a/src/pages/community/contribute/development.mdx +++ b/src/pages/community/contribute/development.mdx @@ -75,15 +75,15 @@ The best place to ask a development-related question is in a working group meeti The `graphql` GitHub organization is the home for projects that hold a unique role in the ecosystem: specifications, test suites, reference implementations, documentation sites, etc. -Except for `graphql-js` as a reference implementation, GraphQL implementations in different languages are encouraged to stay in separate organization. This helps folstering ecosystem diversity. +Except for `graphql-js` as a reference implementation, GraphQL implementations in different languages are encouraged to stay in separate organizations. This helps fostering ecosystem diversity. General guidelines: -* The project should be using an opensource license. +* The project should be using an open source license. * The project should be actively maintained. * The project should hold a unique role in the ecosystem. -To request adding a new project, please open [an issue is the `graphql-wg`](https://github.com/graphql/graphql-wg/issues/new) repository. Project adoption is [decided by the TSC](https://github.com/graphql/graphql-wg/blob/main/GraphQL-TSC.md#decision-making-authority). +To request adding a new project, please open [an issue in the `graphql-wg`](https://github.com/graphql/graphql-wg/issues/new) repository. Project adoption is [decided by the TSC](https://github.com/graphql/graphql-wg/blob/main/GraphQL-TSC.md#decision-making-authority). If you want to get involved in GraphQL, add yourself to the meeting agenda for one of our [working groups or implementations](./project-meetings/#quick-guide-how-to-join), sign the document if you haven't already, and show up! Or, if you prefer, just open a PR against our projects as this will also initiate the spec membership signature process. From 227d1fbc23399152ab6343094b69468731c981ea Mon Sep 17 00:00:00 2001 From: Martin Bonnin Date: Thu, 7 May 2026 20:16:21 +0200 Subject: [PATCH 3/6] Update src/pages/community/contribute/development.mdx Co-authored-by: James Bellenger --- src/pages/community/contribute/development.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/community/contribute/development.mdx b/src/pages/community/contribute/development.mdx index fe43a9b400..dc856e9d11 100644 --- a/src/pages/community/contribute/development.mdx +++ b/src/pages/community/contribute/development.mdx @@ -75,7 +75,7 @@ The best place to ask a development-related question is in a working group meeti The `graphql` GitHub organization is the home for projects that hold a unique role in the ecosystem: specifications, test suites, reference implementations, documentation sites, etc. -Except for `graphql-js` as a reference implementation, GraphQL implementations in different languages are encouraged to stay in separate organizations. This helps fostering ecosystem diversity. +Except for `graphql-js` as a reference implementation, GraphQL implementations in different languages are encouraged to stay in separate organizations. This helps foster ecosystem diversity. General guidelines: From 2b83d36587319cfca83e57543725f5687260f3e0 Mon Sep 17 00:00:00 2001 From: Martin Bonnin Date: Thu, 7 May 2026 21:32:18 +0200 Subject: [PATCH 4/6] Update adoption guidelines to characteristics --- .../community/contribute/development.mdx | 31 ++++++++----------- 1 file changed, 13 insertions(+), 18 deletions(-) diff --git a/src/pages/community/contribute/development.mdx b/src/pages/community/contribute/development.mdx index dc856e9d11..d4f9cf6c62 100644 --- a/src/pages/community/contribute/development.mdx +++ b/src/pages/community/contribute/development.mdx @@ -13,7 +13,19 @@ All of our work [happens in the open](https://github.com/graphql). In addition, The best place to ask a development-related question is in a working group meeting, or by opening a GitHub issue. Please note that if you have an implementation question, you may get a faster answer by [asking in one of the channels more geared toward users](/community/resources/official-channels/). -## GraphQL projects and implementations +## GraphQL projects + +The `graphql` GitHub organization is the home for projects that hold a unique role in the ecosystem: specifications, test suites, reference implementations, documentation sites, etc. + +Except for `graphql-js` as a reference implementation, GraphQL implementations in different languages are encouraged to stay in separate organizations. This helps foster ecosystem diversity. + +In general, projects in the `graphql` organization: + +* are open source. +* are actively maintained. +* hold a unique role in the ecosystem. + +Current projects include: -## Project adoption guidelines - -The `graphql` GitHub organization is the home for projects that hold a unique role in the ecosystem: specifications, test suites, reference implementations, documentation sites, etc. - -Except for `graphql-js` as a reference implementation, GraphQL implementations in different languages are encouraged to stay in separate organizations. This helps foster ecosystem diversity. - -General guidelines: - -* The project should be using an open source license. -* The project should be actively maintained. -* The project should hold a unique role in the ecosystem. - -To request adding a new project, please open [an issue in the `graphql-wg`](https://github.com/graphql/graphql-wg/issues/new) repository. Project adoption is [decided by the TSC](https://github.com/graphql/graphql-wg/blob/main/GraphQL-TSC.md#decision-making-authority). - -If you want to get involved in GraphQL, add yourself to the meeting agenda for one of our [working groups or implementations](./project-meetings/#quick-guide-how-to-join), sign the document if you haven't already, and show up! Or, if you prefer, just open a PR against our projects as this will also initiate the spec membership signature process. - -We welcome your participation! From 8b6128d2f2916ad99136ebd476d1f2648ff9dc70 Mon Sep 17 00:00:00 2001 From: Martin Bonnin Date: Thu, 7 May 2026 22:31:36 +0200 Subject: [PATCH 5/6] Update src/pages/community/contribute/development.mdx Co-authored-by: Benjie --- src/pages/community/contribute/development.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/community/contribute/development.mdx b/src/pages/community/contribute/development.mdx index d4f9cf6c62..23f9d12d20 100644 --- a/src/pages/community/contribute/development.mdx +++ b/src/pages/community/contribute/development.mdx @@ -13,7 +13,7 @@ All of our work [happens in the open](https://github.com/graphql). In addition, The best place to ask a development-related question is in a working group meeting, or by opening a GitHub issue. Please note that if you have an implementation question, you may get a faster answer by [asking in one of the channels more geared toward users](/community/resources/official-channels/). -## GraphQL projects +## GraphQL Foundation projects The `graphql` GitHub organization is the home for projects that hold a unique role in the ecosystem: specifications, test suites, reference implementations, documentation sites, etc. From 722994c010e472563aa4a80404be793679b704bb Mon Sep 17 00:00:00 2001 From: Martin Bonnin Date: Thu, 7 May 2026 22:51:07 +0200 Subject: [PATCH 6/6] Restore "get involved" part --- src/pages/community/contribute/development.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/pages/community/contribute/development.mdx b/src/pages/community/contribute/development.mdx index 23f9d12d20..8cf22a0d76 100644 --- a/src/pages/community/contribute/development.mdx +++ b/src/pages/community/contribute/development.mdx @@ -83,3 +83,6 @@ Current projects include: ]} /> +If you want to get involved in GraphQL, add yourself to the meeting agenda for one of our [working groups or implementations](./project-meetings/#quick-guide-how-to-join), sign the document if you haven't already, and show up! Or, if you prefer, just open a PR against our projects as this will also initiate the spec membership signature process. + +We welcome your participation!