Skip to content

Commit dac03c6

Browse files
committed
more
1 parent 054b957 commit dac03c6

File tree

2 files changed

+21
-17
lines changed

2 files changed

+21
-17
lines changed

website/src/pages/community/contribute/project-meetings.mdx

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
## Project Meetings
1+
# Project Meetings
22

33
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).
44

@@ -8,19 +8,23 @@ All GraphQL project meetings should appear on the [GraphQL public calendar](http
88

99
- **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.
1010

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._
11+
import { Callout } from 'nextra/components'
12+
13+
<Callout type="warning">
14+
**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.
15+
</Callout>
1216

1317
If you have questions about this process, please ask [[email protected]](mailto:[email protected]).
1418

15-
### GraphQL Working Group / TSC meeting
19+
## GraphQL Working Group / TSC meeting
1620

1721
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.
1822

1923
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.
2024

2125
To join, add yourself to an [upcoming meeting agenda](https://github.com/graphql/graphql-wg/tree/HEAD/agendas).
2226

23-
### GraphQL.js Working Group meeting
27+
## GraphQL.js Working Group meeting
2428

2529
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).
2630

website/src/pages/community/contribute/project-resources.mdx

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,22 @@
1-
## Project Resources
1+
# Project Resources
22

33
The following resources are intended to help official GraphQL projects understand what resources are available to them, and how to correctly run meetings.
44

5-
### Types of GraphQL projects
5+
## Types of GraphQL projects
66

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/).
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).
88

99
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).
1010

1111
We welcome and encourage community members and third-parties to maintain their own implementations.
1212

13-
> #### Making an independent project official
13+
> ### Making an independent project official
1414
>
1515
> 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.
1616
>
1717
> 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])
1818
19-
### Running project meetings
19+
## Running project meetings
2020

2121
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.
2222

@@ -39,33 +39,33 @@ The **person running the call** must:
3939
- Notify all attendees the meeting is being recorded, and record to the cloud.
4040
- Keep minutes, or have a volunteer to write them. Minutes should be published to the project repo.
4141

42-
### Resources for projects
42+
## Resources for projects
4343

44-
#### Zoom
44+
### Zoom
4545

4646
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.
4747

48-
#### GitHub
48+
### GitHub
4949

5050
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.
5151

52-
#### YouTube playlist
52+
### YouTube playlist
5353

5454
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.
5555

56-
#### GraphQL calendar
56+
### GraphQL calendar
5757

5858
Project meetings should be added to the [GraphQL calendar](https://calendar.graphql.org), so that people can easily find them.
5959

60-
#### GraphQL domain registration and DNS management
60+
### GraphQL domain registration and DNS management
6161

6262
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]).
6363

64-
#### Trademark guidance
64+
### Trademark guidance
6565

6666
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]).
6767

68-
#### All other questions
68+
### All other questions
6969

7070
If you have a question not covered here, please reach out to [[email protected]](mailto:[email protected]).
7171

0 commit comments

Comments
 (0)