How the YAMS Project Is Maintained and How You Can Get Involved

YAMS (Yet Another Media Server) is maintained as an open project: its source code is published on three Git hosts, and users can follow or contribute through those repositories, discuss the project on Discord or its forum, and support it through the donation option listed on the site. The best entry point depends on whether you want to track changes, report or fix issues, or just ask questions.

Where the project lives

The yams.media site links to three separate repositories for the same project:

Because the project is described as a bash installation script, the repositories are where the script itself and its change history live. If you want to see what changed between versions before reinstalling, the commit history on any of these hosts is the place to look.

Following updates vs. contributing

• Following: watch or star a repository on the host you already use. You do not need an account on all three.
• Contributing: the site does not document a contribution workflow (branching rules, pull request policy, coding conventions). Check the repository's own README and issue tracker on the host you choose before submitting changes, since those details are maintained there rather than on the marketing page.
• Reporting a problem: the site points to a forum and Discord as the community channels; use the issue tracker on a repository when the problem is clearly a bug in the script.

Community channels

The site lists two discussion venues alongside the repositories:

• Forum — linked from the main navigation, suited to longer setup and configuration questions.
• Discord — linked in the navigation and again in the footer, suited to quicker back-and-forth.

The site also carries a French-language toggle (🇫🇷 FR), so French-speaking users have a localized entry point to the same pages.

Supporting the project

The navigation includes a Donate link, and the homepage carries a "Support YAMS!" prompt. That is the extent of what the site states about funding: a donation option exists. No pricing, tiers, or payment details are published on the page, so treat donations as optional support for the project rather than a paid product with entitlements.

A practical way to get involved

1. Open one repository (for example the GitHub one) and read its README to see how the script is organized.
2. Check open issues to see whether your question or bug is already known.
3. For usage questions, post on the forum or Discord rather than opening an issue.
4. If you fix something, submit it through the repository you are already working in — the project accepts contributions across all three hosts, so there is no single mandated one.

The main pitfall is assuming the three repositories are identical in activity. They mirror the same project, but issues and merge activity may concentrate on one host; check before you invest time in a pull request on a quiet mirror.