You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/src/pages/community/contribute.mdx
-97Lines changed: 0 additions & 97 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,101 +3,4 @@ title: Contribute to GraphQL
3
3
description: The following resources describe how GraphQL development processes work, how to get involved, and where to get help.
4
4
---
5
5
6
-
## Project resources
7
6
8
-
The following resources are intended to help official GraphQL projects understand what resources are available to them, and how to correctly run meetings.
9
-
10
-
### Types of GraphQL projects
11
-
12
-
The GraphQL community is incredibly broad, with a large number of reference implementations which are developed and evolving in parallel to the GraphQL project. Many of them are listed [here](/code/).
13
-
14
-
The primary distinction between official GraphQL projects and other implementations is that GraphQL projects are managed under the [GraphQL technical charter](https://technical-charter.graphql.org) and [GraphQL Code of Conduct](https://code-of-conduct.graphql.org).
15
-
16
-
We welcome and encourage community members and third-parties to maintain their own implementations.
17
-
18
-
> #### Making an independent project official
19
-
>
20
-
> If you maintain a tool or reference implementation that you'd like to transfer to the [GraphQL GitHub org](https://github.com/graphql), or if you are planning to start a new workgroup or implementation within the official GraphQL project, please add your name to the agenda of an upcoming [GraphQL Working Group meeting](https://github.com/graphql/graphql-wg/tree/HEAD/agendas) to introduce your idea.
21
-
>
22
-
> Should your proposal meet with approval, a few things will then need to happen. For example, we will work with you to adopt our policies and neutral governance, and help you transfer the project and its assets (generally the domain name and any trademarks) so that they are neutrally held at the Linux Foundation. If you'd like to explore the idea before making a proposal, please reach out to [[email protected]](mailto:[email protected])
23
-
24
-
### Running project meetings
25
-
26
-
Because GraphQL is a [Joint Development Foundation](https://www.jointdevelopment.org/) project, all meeting participants and contributors must complete the GraphQL specification membership agreement prior to participating.
27
-
28
-
Each **technical meeting** must:
29
-
30
-
- Have an agenda Markdown document in the project repo published at least a week before the call.
31
-
- Have an "Attendees" section where people can open a PR and add their own names in advance.
32
-
- Optional, but encouraged: Use the GraphQL Zoom account so that we can easily post the meeting recording to [YouTube](https://youtube.graphql.org).
33
-
34
-
Each **attendee** must:
35
-
36
-
- Add their name to the agenda prior to the meeting.
37
-
- Pass the EasyCLA check by signing the agreement as an individual, or asking their company to add them to the list.
38
-
39
-
The **person running the call** must:
40
-
41
-
- Merge all appropriate attendance and agenda PRs with passing checks prior to the meeting.
42
-
- Verify that everyone who connects to the meeting appears on the list.
43
-
- If someone joins who is not on the list, they need to disconnect until they can PR themselves onto the attendee list with all checks passing.
44
-
- Notify all attendees the meeting is being recorded, and record to the cloud.
45
-
- Keep minutes, or have a volunteer to write them. Minutes should be published to the project repo.
46
-
47
-
### Resources for projects
48
-
49
-
#### Zoom
50
-
51
-
Official GraphQL projects and workgroups are welcome and encouraged to use the GraphQL zoom. Please contact [[email protected]](mailto:[email protected]) to get the credentials.
52
-
53
-
#### GitHub
54
-
55
-
Official GraphQL projects can host their repos in the [graphql organization](https://github.com/graphql). This includes code repos, spec repos, and workgroup coordination repos. Please contact [[email protected]](mailto:[email protected]) for details.
56
-
57
-
#### YouTube playlist
58
-
59
-
Wherever possible, we record meetings and post them to a playlist on the [GraphQL YouTube channel](https://youtube.graphql.org). If your project does not have a playlist, please contact [[email protected]](mailto:[email protected]) and we can set you up.
60
-
61
-
#### GraphQL calendar
62
-
63
-
Project meetings should be added to the [GraphQL calendar](https://calendar.graphql.org), so that people can easily find them.
64
-
65
-
#### GraphQL domain registration and DNS management
66
-
67
-
The Linux Foundation holds the top-level graphql.org domain, and a number of others. If you need to register a domain for your project (particularly if it includes the word "graphql") or need to manage DNS for a registered domain, please contact [[email protected]](mailto:[email protected]).
68
-
69
-
#### Trademark guidance
70
-
71
-
The GraphQL trademark is managed by LF Projects. GraphQL projects are able to use the GraphQL name and marks in accordance with the [trademark policy](https://lfprojects.org/policies/trademark-policy/). If your project has questions about how you or others can use the mark, please contact [[email protected]](mailto:[email protected]).
All GraphQL technical meetings are open to anyone who is interested, so long as they first complete the [GraphQL Specification Membership agreement](https://github.com/graphql/graphql-wg/tree/HEAD/membership).
80
-
81
-
All GraphQL project meetings should appear on the [GraphQL public calendar](https://calendar.graphql.org). If a project's meeting isn't on the calendar or is incorrect, please email [email protected].
82
-
83
-
-**Who can join GraphQL project meetings:** Anyone who has signed the free [GraphQL Specification Membership agreement](https://github.com/graphql/graphql-wg/tree/HEAD/membership).
84
-
85
-
-**How to join:** Each GraphQL project must maintain an agenda document for each meeting, and each attendee must add themselves to it prior to attending. To join, open a PR to add your name to the attendee list on an upcoming meeting's agenda (for example, the [GraphQL Working Group](https://github.com/graphql/graphql-wg/tree/HEAD/agendas) or [GraphQL.js](https://github.com/graphql/graphql-js-wg/tree/main/agendas)). The agenda document will have the date, time and Zoom links.
86
-
87
-
_IMPORTANT: Your PR against the agenda_**_must_**_be merged before you can attend. If the EasyCLA bot says you are not covered, you need to follow the links in the bot's comment to sign the [GraphQL Specification Membership agreement](https://github.com/graphql/graphql-wg/tree/HEAD/membership) before you can attend._
The [GraphQL Working Group](https://github.com/graphql/graphql-wg) meets on the first Thursday of each month. When there are topics to address, the [GraphQL Technical Steering Committee (TSC)](https://github.com/graphql/graphql-wg/blob/HEAD/GraphQL-TSC.md) may meet briefly prior to the start of the Working Group meeting.
94
-
95
-
The goal of the working group meeting is to discuss current work and future plans for the GraphQL specification. The Working Group meeting is also the place to coordinate between other GraphQL working groups and reference implementations.
96
-
97
-
To join, add yourself to an [upcoming meeting agenda](https://github.com/graphql/graphql-wg/tree/HEAD/agendas).
98
-
99
-
### GraphQL.js Working Group meeting
100
-
101
-
The [GraphQL.js working group](https://github.com/graphql/graphql-js-wg) meets the second Tuesday of each month. The goal is to plan development work and resolve issues with [GraphQL.js](https://github.com/graphql/graphql-js).
102
-
103
-
To join, add yourself to an [upcoming meeting agenda](https://github.com/graphql/graphql-js-wg/tree/HEAD/agendas).
All GraphQL technical meetings are open to anyone who is interested, so long as they first complete the [GraphQL Specification Membership agreement](https://github.com/graphql/graphql-wg/tree/HEAD/membership).
4
+
5
+
All GraphQL project meetings should appear on the [GraphQL public calendar](https://calendar.graphql.org). If a project's meeting isn't on the calendar or is incorrect, please email [email protected].
6
+
7
+
-**Who can join GraphQL project meetings:** Anyone who has signed the free [GraphQL Specification Membership agreement](https://github.com/graphql/graphql-wg/tree/HEAD/membership).
8
+
9
+
-**How to join:** Each GraphQL project must maintain an agenda document for each meeting, and each attendee must add themselves to it prior to attending. To join, open a PR to add your name to the attendee list on an upcoming meeting's agenda (for example, the [GraphQL Working Group](https://github.com/graphql/graphql-wg/tree/HEAD/agendas) or [GraphQL.js](https://github.com/graphql/graphql-js-wg/tree/main/agendas)). The agenda document will have the date, time and Zoom links.
10
+
11
+
_IMPORTANT: Your PR against the agenda_**_must_**_be merged before you can attend. If the EasyCLA bot says you are not covered, you need to follow the links in the bot's comment to sign the [GraphQL Specification Membership agreement](https://github.com/graphql/graphql-wg/tree/HEAD/membership) before you can attend._
The [GraphQL Working Group](https://github.com/graphql/graphql-wg) meets on the first Thursday of each month. When there are topics to address, the [GraphQL Technical Steering Committee (TSC)](https://github.com/graphql/graphql-wg/blob/HEAD/GraphQL-TSC.md) may meet briefly prior to the start of the Working Group meeting.
18
+
19
+
The goal of the working group meeting is to discuss current work and future plans for the GraphQL specification. The Working Group meeting is also the place to coordinate between other GraphQL working groups and reference implementations.
20
+
21
+
To join, add yourself to an [upcoming meeting agenda](https://github.com/graphql/graphql-wg/tree/HEAD/agendas).
22
+
23
+
### GraphQL.js Working Group meeting
24
+
25
+
The [GraphQL.js working group](https://github.com/graphql/graphql-js-wg) meets the second Tuesday of each month. The goal is to plan development work and resolve issues with [GraphQL.js](https://github.com/graphql/graphql-js).
26
+
27
+
To join, add yourself to an [upcoming meeting agenda](https://github.com/graphql/graphql-js-wg/tree/HEAD/agendas).
The following resources are intended to help official GraphQL projects understand what resources are available to them, and how to correctly run meetings.
4
+
5
+
### Types of GraphQL projects
6
+
7
+
The GraphQL community is incredibly broad, with a large number of reference implementations which are developed and evolving in parallel to the GraphQL project. Many of them are listed [here](/code/).
8
+
9
+
The primary distinction between official GraphQL projects and other implementations is that GraphQL projects are managed under the [GraphQL technical charter](https://technical-charter.graphql.org) and [GraphQL Code of Conduct](https://code-of-conduct.graphql.org).
10
+
11
+
We welcome and encourage community members and third-parties to maintain their own implementations.
12
+
13
+
> #### Making an independent project official
14
+
>
15
+
> If you maintain a tool or reference implementation that you'd like to transfer to the [GraphQL GitHub org](https://github.com/graphql), or if you are planning to start a new workgroup or implementation within the official GraphQL project, please add your name to the agenda of an upcoming [GraphQL Working Group meeting](https://github.com/graphql/graphql-wg/tree/HEAD/agendas) to introduce your idea.
16
+
>
17
+
> Should your proposal meet with approval, a few things will then need to happen. For example, we will work with you to adopt our policies and neutral governance, and help you transfer the project and its assets (generally the domain name and any trademarks) so that they are neutrally held at the Linux Foundation. If you'd like to explore the idea before making a proposal, please reach out to [[email protected]](mailto:[email protected])
18
+
19
+
### Running project meetings
20
+
21
+
Because GraphQL is a [Joint Development Foundation](https://www.jointdevelopment.org/) project, all meeting participants and contributors must complete the GraphQL specification membership agreement prior to participating.
22
+
23
+
Each **technical meeting** must:
24
+
25
+
- Have an agenda Markdown document in the project repo published at least a week before the call.
26
+
- Have an "Attendees" section where people can open a PR and add their own names in advance.
27
+
- Optional, but encouraged: Use the GraphQL Zoom account so that we can easily post the meeting recording to [YouTube](https://youtube.graphql.org).
28
+
29
+
Each **attendee** must:
30
+
31
+
- Add their name to the agenda prior to the meeting.
32
+
- Pass the EasyCLA check by signing the agreement as an individual, or asking their company to add them to the list.
33
+
34
+
The **person running the call** must:
35
+
36
+
- Merge all appropriate attendance and agenda PRs with passing checks prior to the meeting.
37
+
- Verify that everyone who connects to the meeting appears on the list.
38
+
- If someone joins who is not on the list, they need to disconnect until they can PR themselves onto the attendee list with all checks passing.
39
+
- Notify all attendees the meeting is being recorded, and record to the cloud.
40
+
- Keep minutes, or have a volunteer to write them. Minutes should be published to the project repo.
41
+
42
+
### Resources for projects
43
+
44
+
#### Zoom
45
+
46
+
Official GraphQL projects and workgroups are welcome and encouraged to use the GraphQL zoom. Please contact [[email protected]](mailto:[email protected]) to get the credentials.
47
+
48
+
#### GitHub
49
+
50
+
Official GraphQL projects can host their repos in the [graphql organization](https://github.com/graphql). This includes code repos, spec repos, and workgroup coordination repos. Please contact [[email protected]](mailto:[email protected]) for details.
51
+
52
+
#### YouTube playlist
53
+
54
+
Wherever possible, we record meetings and post them to a playlist on the [GraphQL YouTube channel](https://youtube.graphql.org). If your project does not have a playlist, please contact [[email protected]](mailto:[email protected]) and we can set you up.
55
+
56
+
#### GraphQL calendar
57
+
58
+
Project meetings should be added to the [GraphQL calendar](https://calendar.graphql.org), so that people can easily find them.
59
+
60
+
#### GraphQL domain registration and DNS management
61
+
62
+
The Linux Foundation holds the top-level graphql.org domain, and a number of others. If you need to register a domain for your project (particularly if it includes the word "graphql") or need to manage DNS for a registered domain, please contact [[email protected]](mailto:[email protected]).
63
+
64
+
#### Trademark guidance
65
+
66
+
The GraphQL trademark is managed by LF Projects. GraphQL projects are able to use the GraphQL name and marks in accordance with the [trademark policy](https://lfprojects.org/policies/trademark-policy/). If your project has questions about how you or others can use the mark, please contact [[email protected]](mailto:[email protected]).
0 commit comments