Vimivo Community Guidelines & Support Policy

1. Our Commitment#

Vimivo is an open-source, community-driven, privacy-first multimedia player. We are dedicated to providing a welcoming, constructive, and respectful environment for all contributors, testers, and users regardless of experience level, background, or operating system preference.

2. Where to Engage#

• GitHub Issues:
• Bug reports with reproducible steps.
• Media playback compatibility defects.
• Accessibility barriers.
• Packaging and installation failures.
• GitHub Discussions:
• Feature ideas and workflow proposals.
• Format compatibility tips and user setups.
• General questions and community discussions.
• Security Vulnerabilities:
• Please follow our Security Policy and report security concerns confidentially.

3. High-Quality Community Interactions#

When filing issues or participating in discussions:

1. Be Respectful & Constructive: Focus on technical facts, reproducible behavior, and objective analysis.
2. Search Before Posting: Check existing issues and discussions to avoid creating duplicates.
3. Use the Issue Templates: GitHub issue forms are structured to capture critical technical context (OS version, app build, container, codec).
4. Do Not Fabricate or Exaggerate: State what you observed accurately. Do not invent error messages, user counts, or impact metrics.
5. Protect Privacy: Never post passwords, API tokens, personal contact details, or copyrighted media files in public threads.

4. Maintenance Expectations & Response Standards#

• Vimivo is maintained by engineers dedicated to building high-quality, long-term software.
• We do not make false promises regarding feature timelines or release dates.
• High-severity bugs (P0/P1) involving data integrity, security, or core playback failures are prioritized over cosmetic enhancements.
• All community-reported issues must have a reproducible test case or fixture before a fix is considered complete.