Skip to content

CODE_OF_CONDUCT.md

Latest commit

 

History

History
36 lines (29 loc) · 2.79 KB

CODE_OF_CONDUCT.md

File metadata and controls

36 lines (29 loc) · 2.79 KB

Code of Conduct & Project Rules

1. Professional Expectations

This is a free, open-source project maintained by volunteers in their spare time. To keep the project sustainable, we require all participants to adhere to basic professional etiquette:

  • Start with a greeting. A simple "hello" goes a long way.
  • No demanding attitudes. We do not have an SLA. Do not use terms like "URGENT", "ASAP", or "CRITICAL". Such issues will be closed immediately.
  • Respect our time. If you act with entitlement, you will be ignored or banned. We are here to develop software, not to provide 24/7 personal support.

2. Hardware Compatibility & Support

We provide a list of recommended hardware and verified LED drivers for a reason: Wiki.

  • Unsupported Hardware: If you choose to use hardware or drivers outside of our recommended specifications, you are responsible for your own troubleshooting.
  • Testing Constraints: We can only diagnose problems that can be reproduced on our verified test environments. If we don't own your specific hardware, usually we cannot help you.
  • "Won't Fix": Issues caused by ignoring hardware recommendations will be closed as "Unsupported".

3. Policy on AI-Generated Content

Do NOT post solutions, configurations, or "bug reports" generated by AI (ChatGPT, Claude, etc.).

  • No Hallucinations: AI models frequently hallucinate details about this project that do not exist.
  • Verification: If you bring AI-generated "advice" here and treat it as a fact over our documentation or the maintainers' advice, the conversation will be terminated. We will not spend time debunking AI-generated nonsense.

4. Technical Requirements for Support

We cannot help if we are missing data. If your report lacks the following, it will be closed without investigation:

  • Detailed Environment: Full hardware and software configuration.
  • Complete Logs: We require the WHOLE log, not just snippets you deem "relevant".
  • Visuals: Screenshots of the video live preview are mandatory for any LED rendering issues.
  • Reproducibility: Clear, step-by-step instructions to reproduce the issue on recommended hardware.

5. Search Before You Ask

Most questions are already answered in our Wiki and Discussions.

Consequences

To maintain a productive environment, we reserve the right to:

  1. Close any issue or PR that violates these rules.
  2. Lock discussions that become unproductive or demanding.
  3. Ban users who demonstrate a pattern of entitlement, laziness, or disrespect.

By participating in this project, you acknowledge these rules. If you disagree with this approach, feel free to fork the code and maintain it according to your own standards.