> 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/roster.md). # Roster The most important thing in editing and producing SftP magazine is **communication**. Each editorial collective has a Roster spreadsheet, with tabs for editors (including technical editors, proofreaders and copy-editors) and for authors and artists. The **Editors** tab of the spreadsheet includes: \ Name (as you want it to appear in the masthead), \ Email address, \ Role on the collective (editor, technical editor, copy editor/proofreader, or one of the officer or lead roles) and \ About you - any information on your scientific expertise or editorial experience, or other background you'd like to share. The **Authors** and **Artists** tabs of the spreadsheet include:\ Name (as they want it to appear in their byline)\ Email address\ Note about the article / artwork / other contribution in the magazine It's critical to maintain this roster because some people involved in technical editing and proofreading may not be on the listserv, and so that editing teams can contact each other easily without emailing the entire listserv. --- # 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/roster.md?ask=&goal= ``` `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.