> For the complete documentation index, see [llms.txt](https://sftpmag.gitbook.io/sftp-publishing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sftpmag.gitbook.io/sftp-publishing/editorial-collectives-1/communication-channels.md).

# Communication Channels/Tools

We want ECs to be communicating consistently, discussing their challenges, and raising any questions or ideas they may have outside of Zoom meetings. To do so, we typically use these communication channels.&#x20;

**Slack**

* SftP Slack has dedicated channels for #publication, #artwork, #socialmedia, and a channel for each editorial collective. Email the ME if you need an invitation to join the Slack.

**GoogleGroup Listservs**

* We primarily communicate as a group via a GoogleGroup listserv, to which all members of the editorial collective are added once they fill out the [Roster](/sftp-publishing/editorial-collectives-1/roster.md).
* The Technical Editors and Copy Editing/Proofreading volunteers have their own listservs to spread the word about occasional trainings or open assignments.
* The Publications Committee, the umbrella group for all magazine-related activities that sets themes and priorities for the months ahead, also has a listserv.
* Email the ME (<editors@scienceforthepeople.org>) to be added to any of these lists.

**Zoom meetings**

* We use Zoom, set up in the SftP organization account, for all regular meetings.
* If you can't use Zoom or can't make our regularly scheduled calls--usually on Sundays--please reach out to the ME, especially if you have ideas for alternatives to stay in touch outside of meetings.

**When2Meet**

* we use when2meet.com to create polls for meeting availability. It's like Doodle, but easier to use. Anyone can create a when2meet without an account.


---

# 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://sftpmag.gitbook.io/sftp-publishing/editorial-collectives-1/communication-channels.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.
