Skip to content

CONTACT.md

Latest commit

 

History

History
167 lines (129 loc) · 6.85 KB

CONTACT.md

File metadata and controls

167 lines (129 loc) · 6.85 KB

Contact Information

This document provides comprehensive contact information for the Sorting Office project, including how to get support, report issues, contribute, and contact the maintainers.

Table of Contents

  1. 🆘 Support & Help
  2. 🐛 Bug Reports
  3. 🔒 Security Issues
  4. 💡 Feature Requests
  5. 📚 Documentation
  6. 🤝 Contributing
  7. 💰 Sponsorship
  8. 📞 Direct Contact
  9. 🏢 Enterprise Support
  10. 📋 Response Times
  11. 🔗 Quick Links

🆘 Support & Help

Getting Started

Common Issues

🐛 Bug Reports

How to Report Bugs

  1. Search existing issues first to avoid duplicates
  2. Create a new issue with the "bug" label
  3. Include detailed information:
    • Steps to reproduce
    • Expected vs actual behavior
    • Environment details (OS, database version, etc.)
    • Error messages or logs
    • Screenshots if applicable

Issue Templates

We provide issue templates to help you report bugs effectively:

🔒 Security Issues

Reporting Security Vulnerabilities

Please do not report security vulnerabilities through public GitHub issues.

How to Report Security Issues

  1. GitHub Security Advisories: github.com/flurdy/sortingoffice/security/advisories
  2. Contact Form: ltrbx.io/flurdy.com
  3. PGP Keys: keybase.io/flurdy for encrypted communication

What to Include

  • Description of the vulnerability
  • Steps to reproduce
  • Potential impact assessment
  • Suggested fix (if any)

Response Timeline

  • Initial response: Within 48 hours
  • Regular updates: On issue status
  • Credit: In security advisories (if desired)
  • Coordination: For responsible disclosure

💡 Feature Requests

How to Request Features

  1. Search existing issues to avoid duplicates
  2. Create a new issue with the "enhancement" label
  3. Use the feature request template for structured requests
  4. Explain the use case and expected benefits

Feature Request Guidelines

  • Describe the problem you're trying to solve
  • Explain how the feature would help
  • Provide examples of similar features in other projects
  • Consider implementation complexity and maintenance burden

📚 Documentation

Contributing to Documentation

Documentation Structure

🤝 Contributing

How to Contribute

  1. Read our guidelines: CONTRIBUTING.md
  2. Fork the repository: https://github.com/flurdy/sortingoffice
  3. Create a feature branch: git checkout -b feature/your-feature
  4. Make your changes: Follow our coding standards
  5. Test your changes: Run make test-all
  6. Submit a pull request: Use our PR template

Development Setup

  • Local Development: See docs/ONBOARDING.md
  • Testing: Run make test-unit, make test-integration, make test-ui
  • Code Quality: Run cargo fmt and cargo clippy

💰 Sponsorship

Supporting the Project

📞 Direct Contact

Project Maintainers

Community Channels

🏢 Enterprise Support

Commercial Support

For enterprise deployments, custom features, or commercial support:

  • Contact: https://ltrbx.io/flurdy.com
  • Services: Custom development, deployment assistance, training
  • Licensing: Commercial licensing available

📋 Response Times

General Inquiries

  • Bug reports: 1-3 business days
  • Feature requests: 1-2 weeks for initial response
  • Documentation issues: 1-5 business days
  • General questions: 1-3 business days

Security Issues

  • Critical vulnerabilities: 24-48 hours
  • High priority: 2-5 business days
  • Medium/Low priority: 1-2 weeks

Enterprise Support

  • Commercial inquiries: 1-2 business days
  • Custom development: Varies by project scope
  • Deployment assistance: 1-3 business days

🔗 Quick Links

Thank you for your interest in Sorting Office! We appreciate your feedback, contributions, and support.