Prettier

Author: benjie

README.md

@@ -2,25 +2,28 @@
 
 GraphQL WG (Working Group) is a set of recurring virtual meetings of maintainers
 of commonly used GraphQL libraries and tools and significant contributors to the
-GraphQL community hosted by the [GraphQL TSC][] as part of the [GraphQL Foundation][].
+GraphQL community hosted by the [GraphQL TSC][] as part of the [GraphQL
+Foundation][].
 
 [graphql tsc]: ./GraphQL-TSC.md
 [graphql foundation]: https://graphql.org/foundation/
 
-The GraphQL WG's primary purpose is to discuss and agree upon
-proposed additions to the [GraphQL Specification](https://github.com/graphql/graphql-spec)
-via the [RFC process](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md). Additionally, the group may discuss and collaborate on other
-relevant technical topics concerning core GraphQL projects.
+The GraphQL WG's primary purpose is to discuss and agree upon proposed additions
+to the [GraphQL Specification](https://github.com/graphql/graphql-spec) via the
+[RFC process](https://github.com/graphql/graphql-spec/blob/main/CONTRIBUTING.md).
+Additionally, the group may discuss and collaborate on other relevant technical
+topics concerning core GraphQL projects.
 
 Anyone in the public GraphQL community may attend a GraphQL WG meeting, provided
-they first sign the [Specification Membership Agreement](./membership) or belong to an organization which has signed.
+they first sign the [Specification Membership Agreement](./membership) or belong
+to an organization which has signed.
 
 This repository holds [agendas](./agendas) and [notes](./notes) for all meetings
 past and upcoming as well as [shared rfc documents](./rfcs). Anyone may edit an
 upcoming event's agenda to _attend_ or _propose an agenda item_.
 
-All meetings occur via video conference, however participating company
-offices are welcome to host guests.
+All meetings occur via video conference, however participating company offices
+are welcome to host guests.
 
 To learn more, read our guide on how to [join a meeting](./JoiningAMeeting.md).
 
@@ -38,12 +41,15 @@ introduced by those who could not make the primary meeting time. There are two
 secondary meetings, each timed to be acceptable for those in either an Asia
 Pacific or European timezone.
 
-Meetings are typically scheduled at the times listed, however always check
-the [agenda](./agendas) for the exact date and time of an upcoming meeting. Keep
-track of future upcoming meetings by subscribing to the [Google Calendar][] or [ical][].
+Meetings are typically scheduled at the times listed, however always check the
+[agenda](./agendas) for the exact date and time of an upcoming meeting. Keep
+track of future upcoming meetings by subscribing to the [Google Calendar][] or
+[ical][].
 
-[google calendar]: https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t
-[ical]: https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics
+[google calendar]:
+  https://calendar.google.com/calendar?cid=bGludXhmb3VuZGF0aW9uLm9yZ19pazc5dDl1dWoycDMyaTNyMjAzZGd2NW1vOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t
+[ical]:
+  https://calendar.google.com/calendar/ical/linuxfoundation.org_ik79t9uuj2p32i3r203dgv5mo8%40group.calendar.google.com/public/basic.ics
 
 ### Subcommittee meetings
 
@@ -66,9 +72,9 @@ editing the relevant [meeting agenda](./agendas).
 ### Want to help us keep up?
 
 We're always looking for volunteers to help take notes from the meetings, the
-results of which are shared in [`notes/`](./notes). If you're
-interested in taking notes, sign up for a meeting in [`agendas/`](./agendas) and
-indicate that you're willing to be a note taker.
+results of which are shared in [`notes/`](./notes). If you're interested in
+taking notes, sign up for a meeting in [`agendas/`](./agendas) and indicate that
+you're willing to be a note taker.
 
 # Participation guidelines
 
@@ -77,7 +83,8 @@ follow or run off course. When we talk about issues we care about, it's easy to
 get into heated debate. In order to respect everyone's time, and arrive to
 worthwhile outcomes, consider a few guidelines:
 
-_These guidelines are heavily inspired by [Allen Wirfs-Brock](http://wirfs-brock.com/allen/files/papers/standpats-asianplop2016.pdf)._
+_These guidelines are heavily inspired by
+[Allen Wirfs-Brock](http://wirfs-brock.com/allen/files/papers/standpats-asianplop2016.pdf)._
 
 ### Participate
 
@@ -115,40 +122,53 @@ projects, or planned events.
 
 We're all passionate about GraphQL and it's easy to get mired with an opinion in
 every agenda item. There are many ways to solve a problem and you won't always
-agree with all of them. Express your views but don't argue about a topic that
-is not relevant to your goals.
+agree with all of them. Express your views but don't argue about a topic that is
+not relevant to your goals.
 
 ### Champion alternatives
 
-Sometimes you'll disagree with someone but will find it difficult or
-impossible to convince them of the problems you see. Instead of spending your
-energy fighting, commit to developing an alternative proposal so future
-discussion can be about substance.
+Sometimes you'll disagree with someone but will find it difficult or impossible
+to convince them of the problems you see. Instead of spending your energy
+fighting, commit to developing an alternative proposal so future discussion can
+be about substance.
 
 ### Block progress as a last resort
 
 This working group is only effective when consensus can be reached, even though
 there may be disagreements along the way. You should avoid blocking progress if
 possible, otherwise you may be seen as hostile to the group. However, if you
-have a serious issue with a proposed agenda item outcome, you must make
-it clear.
+have a serious issue with a proposed agenda item outcome, you must make it
+clear.
 
 ### Be patient and persistent
 
 The GraphQL specification evolves slowly, deliberately, and with the consensus
-of the core GraphQL community. The spec [contribution process](https://github.com/graphql/graphql-spec/blob/master/CONTRIBUTING.md)
+of the core GraphQL community. The spec
+[contribution process](https://github.com/graphql/graphql-spec/blob/master/CONTRIBUTING.md)
 requires considerable investment through multiple stages while meeting a
 demanding set of guiding principles. This can take a long time, and progress in
 each meeting can feel small. Don't give up!
 
 # Contributing to this repo
 
-This repository is managed by EasyCLA. Project participants must sign the free ([GraphQL Specification Membership agreement](https://preview-spec-membership.graphql.org) before making a contribution. You only need to do this one time, and it can be signed by [individual contributors](http://individual-spec-membership.graphql.org/) or their [employers](http://corporate-spec-membership.graphql.org/).
+This repository is managed by EasyCLA. Project participants must sign the free
+([GraphQL Specification Membership agreement](https://preview-spec-membership.graphql.org)
+before making a contribution. You only need to do this one time, and it can be
+signed by
+[individual contributors](http://individual-spec-membership.graphql.org/) or
+their [employers](http://corporate-spec-membership.graphql.org/).
 
-To initiate the signature process please open a PR against this repo. The EasyCLA bot will block the merge if we still need a membership agreement from you.
+To initiate the signature process please open a PR against this repo. The
+EasyCLA bot will block the merge if we still need a membership agreement from
+you.
 
-You can find [detailed information here](https://github.com/graphql/graphql-wg/tree/main/membership). If you have issues, please email [operations@graphql.org](mailto:operations@graphql.org).
+You can find
+[detailed information here](https://github.com/graphql/graphql-wg/tree/main/membership).
+If you have issues, please email
+[operations@graphql.org](mailto:operations@graphql.org).
 
 ## Commit access
 
-Commit access is granted to this repo to members of the [GraphQL TSC](./GraphQL-TSC.md) and some regular attendees of working group meetings. To request commit access, please reach out to a TSC member.
+Commit access is granted to this repo to members of the
+[GraphQL TSC](./GraphQL-TSC.md) and some regular attendees of working group
+meetings. To request commit access, please reach out to a TSC member.