Open Source, Sponsorship, And Community Boundaries

ECHO is an open-source project, not an on-demand service desk. Open code, public docs, and available builds do not mean maintainers must absorb every rude demand as a product requirement.

You are welcome to use ECHO, report bugs, provide logs, write reproductions, submit PRs, and improve docs. You are not welcome to treat unpaid maintenance as something owed to you personally.

Open Source Is Not Zero Cost

Open source means the source is visible, the rules are transparent, and collaboration is possible. It does not make development, testing, packaging, support, compatibility work, documentation, and long-term maintenance free.

ECHO maintenance includes:

Desktop playback behavior, operating-system audio differences, and driver compatibility.
Library scanning, remote sources, plugins, lyrics, artwork, and metadata boundaries.
Builds, signing, releases, downloads, documentation, and issue reproduction.
The quiet long-term work that keeps a real project usable.

Treating all of that as an infinite free entitlement does not make anyone look like an open-source expert. It just burns time.

Sponsorship Is Not A Scam

ECHO may accept sponsorships. ECHO may also offer paid services, hosted services, premium conveniences, or other sustainability paths in the future. That is not the same thing as a scam.

Projects do not run on air, and maintainers do not recharge from comments saying “but it is open source.” If you dislike sponsorship or paid extras, you can keep using the existing open-source version or fork the project and maintain it yourself.

Please do not enjoy the work while framing maintenance cost as a moral failure.

Support Is Not A Wishing Well

Clear, reproducible, low-risk issues are easier to handle. These do not raise priority:

No logs, no screenshots, no version number, only “it does not work.”
Personal preferences presented as official obligations.
Requests for sources or integrations with obvious copyright, authorization, or platform-boundary risk.
Threats, labels, moral pressure, or passive-aggressive demands.

Maintainers may help, and maintainers may decline. Open source does not lock project authors behind a service counter.

Community Boundaries

You can criticize ECHO. You can report bugs. You can say a design is awkward. You can bring facts, logs, and reproduction steps.

These are not welcome:

Personal attacks, harassment, public shaming, or exposing personal information.
Pushing third-party infringement risk onto ECHO.
Turning “I want this” into “you must build this.”
Mistaking restraint for permission to keep draining maintainers.

If a conversation turns into pressure, insults, or bad-faith accusations, ECHO may stop engaging. That is not fear of criticism; it is basic project hygiene.

How To Help ECHO Improve

Please provide actionable information:

ECHO version, operating system version, and install channel.
Reproduction steps, screenshots, error text, logs, or diagnostics.
For audio issues: output mode, device name, file format, sample rate, and bit depth.
For library issues: import path type, scan stage, and error details.
For feature requests: the real use case, not only “make it faster.”

That kind of feedback reduces back-and-forth and is more likely to be handled. ECHO welcomes serious collaboration, not unpaid emotional outsourcing.