This document describes the various channels available for getting help with our projects. We're committed to providing accessible support options that accommodate different communication preferences.

• Official Channels
• How to Ask for Help
• Issue Reporting
• Support Expectations
• Community Support

To stay updated on important changes, releases, and news: TODO: Update with your preferred announcement channels.

• Website: https://spicycentral.org/news
• Mastodon: @[email protected]
• Mailing List: [email protected] (Subscribe)

For questions, troubleshooting, and general assistance:

• Support Forum: https://forum.spicycentral.org

  • Recommended for most questions
  • Searchable archive of previous solutions
  • Community and maintainer responses

• Email Support: [email protected]

  • For private inquiries
  • Security-related communications
  • Account issues

TODO: Update with your preferred chat platforms. For more immediate discussions:

• Matrix: #your-org:matrix.org

  • Primary real-time communication channel

• XMPP-MUC (Multi-User Chat): [email protected]

  • Federated open protocol chat

To get the fastest and most helpful response:

1. Check existing resources first

   • Search the documentation
   • Check GitHub issues (open and closed)
   • Search the forum for similar questions

2. Provide essential information

   • Project name and version
   • Clear steps to reproduce issues
   • Error messages (use code blocks for formatting)
   • Your environment details (OS, dependencies, etc.)

3. Format your question clearly

   • Use descriptive titles
   • Break down complex problems into simpler parts
   • Include code samples when relevant

4. Choose the appropriate channel

   • Technical bugs → GitHub Issues
   • Usage questions → Forum
   • Quick interactions → Matrix/XMPP
   • Private concerns → Email

For bugs, feature requests, and documentation improvements:

1. Check for existing issues first
2. Use the appropriate issue template
3. Follow the template guidelines for necessary information
4. Add relevant labels if you have permission

See our Contributing Guidelines for more details.

• Forum and GitHub: Response within 2-3 business days
• Email: Response within 3-5 business days
• Matrix/XMPP: Community members may respond based on availability; no guaranteed response time

Please note that response times may vary based on volunteer availability. Critical security issues receive priority attention.

Our community members often provide help to each other. When receiving community support:

• Be respectful of volunteers' time
• Consider if the solution worked for you and report back
• Pay it forward by helping others when you can

Note: For security vulnerabilities, please follow our Security Policy rather than posting publicly.