> For the complete documentation index, see [llms.txt](https://documentarians.gitbook.io/metadocumentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentarians.gitbook.io/metadocumentation/clone/the-open-collective-way/core-contributors-communication.md).

# Core Contributors: Communication

**Slack:** Most daily communication happens in slack.

* DM if it’s urgent / personal
* Use public channels by default
* Thread replies for ease of flow

**Email:**

* Remove people from ccd in threads if their attention is not needed
* Being ccd is assumed to be an FYI only (no expectation of reply)
* Address as to in an email: there’s an expectation of reply.
* If email communication is being handled, put the rest of the people in the thread in bcc so they know it’s been taken care of but doesn’t keep popping up in their inboxes.

**Mentions (figma, mockups, github, slack)**

* There’s an expectation of reply.

**Hangouts**

* Monday weekly meeting: weekly planning, review of To Dos, numbers and open issues.
* Tuesday-Thursday: daily standup. Rough account of what we are up to & blockers.
* Friday Open Call and Demo Day: open stand-up and demo day.

**Sprints**

* We strive to meet once a quarter, at least once every 6 months. We’d like you to attend once a year.  Open Collective will cover all the costs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentarians.gitbook.io/metadocumentation/clone/the-open-collective-way/core-contributors-communication.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.