Editorial team and governance
SteamOS.Club is an independent community documentation project. It is not affiliated with or endorsed by Valve Corporation, a hardware vendor, a Linux distribution, or a commercial directory listed on the site.
Ownership model
Published pages name a maintenance role rather than implying an unverified personal author. The checked-in registry assigns responsibility for editorial review, Linux platform guidance, hardware evidence, compatibility, performance, open-source projects, releases, and site reliability.
| Role | Responsibility |
|---|---|
Editorial | Bilingual structure, terminology, citations, metadata, and publication state |
Linux platform | Kernel, graphics, session, recovery, and system-service guidance |
Hardware lab | Exact model scope, firmware, components, and physical-test evidence |
Compatibility lab | Game runtime, Proton, anti-cheat, and reproducibility boundaries |
Release engineering | Locked dependencies, build evidence, deployment, and rollback |
Site reliability | Availability, crawlability, stale content, and incident response |
Attribution boundary. A role is accountable for review, but it is not a fabricated human identity. Named bylines can be added only with contributor consent and a verifiable contribution record.
Publication and correction flow
Use the maintenance and crawler policy for review intervals and evidence levels. Game reports use the stricter moderated reporting policy. A vendor specification may establish a component field, but it cannot substitute for a physical Linux compatibility test.
Conflicts, sponsorship, and outbound links
- Commercial, reciprocal, or directory-partner links are isolated on the friend-links page and qualified in markup.
- Inclusion in a synchronized upstream dataset is not an editorial recommendation.
- DR, stars, popularity, and vendor marketing are metadata, not proof of compatibility or safety.
- A recommendation must state its authority, model scope, version, evidence date, and unverified fields.
- Contributors should disclose relevant employment, sponsorship, free hardware, affiliate relationships, or other material interests during review.
What is still missing
The project does not currently publish a verified list of individual maintainers. This page therefore exposes accountable roles and workflows without pretending that an organization schema proves human expertise. Public names, biographies, and contact profiles should be added only after maintainers explicitly approve them.
Sources
Version history
- 2026-07-15: Published the first bilingual governance, attribution, correction, and conflict-of-interest statement.