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: docs/community/working-interest-groups.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ These groups exist to:
24
24
25
25
## Meeting Calendar
26
26
27
-
All Interest Group and Working Group meetings are published on the public MCP community calendar at [events.modelcontextprotocol.io](https://events.modelcontextprotocol.io/).
27
+
All Interest Group and Working Group meetings are published on the public MCP community calendar at [meet.modelcontextprotocol.io](https://meet.modelcontextprotocol.io/).
28
28
29
29
Facilitators are responsible for posting their meeting schedules to this calendar in advance to ensure discoverability and enable broader community participation.
30
30
@@ -36,7 +36,7 @@ Facilitators are responsible for posting their meeting schedules to this calenda
36
36
37
37
- Regular conversations in the Interest Group Discord channel
38
38
-**AND/OR** a recurring live meeting regularly attended by Interest Group members
39
-
- Meeting dates and times published in advance on the [MCP community calendar](https://events.modelcontextprotocol.io/) when applicable, and tagged with their primary topic and interest group Discord channel name (e.g. `auth-ig`)
39
+
- Meeting dates and times published in advance on the [MCP community calendar](https://meet.modelcontextprotocol.io/) when applicable, and tagged with their primary topic and interest group Discord channel name (e.g. `auth-ig`)
40
40
- Notes publicly shared after meetings, as a GitHub issue ([example](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1629)) and/or public Google Doc
41
41
42
42
**Examples**:
@@ -76,7 +76,7 @@ Participation in an Interest Group (IG) is not required to start a Working Group
76
76
77
77
- Meaningful progress towards at least one SEP or spec-related implementation **OR** hold maintenance responsibilities for a project (e.g., Inspector, Registry, SDKs)
78
78
- Facilitators are responsible for keeping track of progress and communicating status when appropriate
79
-
- Meeting dates and times published in advance on the [MCP community calendar](https://events.modelcontextprotocol.io/) when applicable, and tagged with their primary topic and working group Discord channel name (e.g. `agents-wg`)
79
+
- Meeting dates and times published in advance on the [MCP community calendar](https://meet.modelcontextprotocol.io/) when applicable, and tagged with their primary topic and working group Discord channel name (e.g. `agents-wg`)
80
80
- Notes publicly shared after meetings, as a GitHub issue ([example](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1629)) and/or public Google Doc
0 commit comments