Contact & Support¶
How to reach the MESA team¶
| Channel | When to use |
|---|---|
| GitHub issues | Bug reports, feature requests on a specific repo |
| Project mailing list (planned) — until then, email the PI | General questions, workshop announcements, onboarding |
| Slack — invite by request to the PI | Real-time help, early-adopter conversation |
| PI direct — tswetnam@arizona.edu | Partnership inquiries, sensitive matters, security reports |
| Office hours — monthly, Zoom (link via mailing list) | Walk-in support, demos, design discussions |
Where to file an issue¶
| Topic | Repo |
|---|---|
| Hosted service, MCP tool surface | cyverse/mesa-mcp |
| AVU-history catalog | cyverse/mesa-ducklake |
| Generic iRODS MCP server | cyverse/irods-mcp-server |
| Discovery Environment job launching | cyverse-de/formation-mcp |
| Terrain API integration | cyverse/terrain-mcp |
| This documentation site, project-wide | cyverse/mesa |
Response SLAs¶
These are best-effort targets during the prototype phase (Months 1–24). 24×7 production SLAs come with the follow-on operations award.
| Priority | First response | Resolution target |
|---|---|---|
| Security | 1 business day | 30 days |
| Service outage (hosted) | 1 business day | 5 business days |
| Bug — early adopter blocked | 2 business days | 2 weeks |
| Bug — workaround exists | 1 week | Next minor release |
| Feature request | 2 weeks | Triaged into roadmap |
Acknowledging MESA¶
If MESA helped your science, please acknowledge the project:
This work was supported in part by the National Science Foundation through the MESA (Metadata-Enabled Scientific Agents) prototype project, funded by the NSF IDSS program.
Citations and acknowledgments help us secure the follow-on operations award and continue serving the community.