update readme

Author: saihaj

README.md

@@ -1,38 +1,10 @@
-# Working Group Template
-
-This repository contains a template for creating working groups under the
-GraphQL Foundation. To use this template you should:
-
-- create a new repository from it
-- remove this front-matter
-- customize the text in this README
-- fill out `(NAME)` in [notes/README.md](notes/README.md)
-- fill out `wg.config.js` with details about the WG's schedule
-  - `name` / `repoUrl` - update with the name and URL of your WG
-  - `videoConferenceDetails`: ask @Benjie to generate a new series of (recorded) Zoom meetings, then update the URL and password (do NOT change the spacing, it will break the markdown)
-  - `liveNotesUrl`: create a blank Google document with the same title as the
-    WG, make it publicly editable, copy instructions from the main GraphQL WG
-    live notes
-  - `nth`, `weekday`, `time` - when will your WG be? (e.g. 4th Thursday at 10:30am-12am would be `nth: 4, weekday: "Th", time: "10:30-12:00"`)
-- generate your first month's agenda `yarn && yarn gen-agenda YYYY MM` (replacing YYYY MM with the meeting's year and month, e.g. `2025 01`)
-- let @Benjie know the first meeting is scheduled and ask for the GraphQL Foundation calendar to be updated
-- (optional) ask @Benjie or a TSC member to enable agenda auto-merge:
-  - set up branch protections on `main`, specifically requiring `EasyCLA` to pass (may require a PR to be raised to trigger EasyCLA the first time?)
-  - uncomment the block at the top of `.github/workflows/wgutils-automerge.yml`
-
-In this README, items that need replacing are ALLCAPS and surrounded by
-parenthesis. We've attempted to make as much of the text as possible generic so
-that little customization will be needed.
-
----
-
-# GraphQL (NAME) Working Group
+# GraphQL Community Working Group
 
 This working group is a subcommittee of the
 [GraphQL Working Group](https://github.com/graphql/graphql-wg) with the
 following primary purpose:
 
-> (MISSION STATEMENT)
+Serve as the steward of GraphQL's global narrative and market positioning in the technology ecosystem. We develop and execute strategic initiatives that reinforce GraphQL's value proposition while fostering an engaged, educated, and expanding community.
 
 Anyone in the public GraphQL community may attend a meeting of this
 subcommittee, provided they first sign the

package.json

@@ -3,7 +3,7 @@
   "private": true,
   "license": "OWFa-1.0",
   "scripts": {
-    "gen-agenda": "wgutils agenda gen"
+    "gen-agenda": "wgutils agenda gen",
     "test:spellcheck": "cspell \"**/*.md\"",
     "format": "prettier --write \"**/*.{md,yml,yaml,json}\"",
     "format:check": "prettier --check \"**/*.{md,yml,yaml,json}\""

rfcs/README.md

@@ -1,18 +1,28 @@
 # RFC (request for comments) Working Documents
 
-The files found here are collaborative notes exploring various proposals for advancing this subcommittee. Documents included in this directory imply no specific approval or support nor are any proposals required to create a document here.
+The files found here are collaborative notes exploring various proposals for
+advancing this subcommittee. Documents included in this directory imply no
+specific approval or support nor are any proposals required to create a document
+here.
 
 ## Disclaimers
 
-* Documents included in this directory imply no specific approval or support for inclusion in the GraphQL spec or other GraphQL projects.
-* Documents here may be historical or out of date.
-* An RFC may be active without being documented here; there is no requirement to add RFCs here.
+- Documents included in this directory imply no specific approval or support for
+  inclusion in the GraphQL spec or other GraphQL projects.
+- Documents here may be historical or out of date.
+- An RFC may be active without being documented here; there is no requirement to
+  add RFCs here.
 
 ## Contributing
 
-Pull requests are encouraged. New documents and other non-destructive changes may be merged with a low degree of scrutiny and minimal review.
+Pull requests are encouraged. New documents and other non-destructive changes
+may be merged with a low degree of scrutiny and minimal review.
 
 That said, please follow these suggestions:
 
-* New proposals should be presented in a [working group meeting](../agendas). Submitting a document here is not sufficient or required to introduce a new proposal.
-* Favor documents which define a problem and explore a solution space rather than propose a specific change. The intent of documents found here are to help ask and answer questions to build confidence and advance an RFC.
+- New proposals should be presented in a [working group meeting](../agendas).
+  Submitting a document here is not sufficient or required to introduce a new
+  proposal.
+- Favor documents which define a problem and explore a solution space rather
+  than propose a specific change. The intent of documents found here are to help
+  ask and answer questions to build confidence and advance an RFC.

wg.config.js

@@ -2,8 +2,8 @@
 
 /** @type {import('wgutils').Config} */
 const config = {
-  name: "NAME OF WG",
-  repoUrl: "https://github.com/graphql/...",
+  name: "Community Working Group",
+  repoUrl: "https://github.com/graphql/community-wg",
   videoConferenceDetails: `https://zoom.us/j/...
   - _Password:_ ...`,
   liveNotesUrl: "https://docs.google.com/document/d/...",
@@ -16,7 +16,7 @@ const config = {
   attendeesTemplate: `\
 | Name             | GitHub        | Organization       | Location              |
 | :--------------- | :------------ | :----------------- | :-------------------- |
-`
+`,
   /*
   // Additional configuration (optional):