Skip to content

COMMUNITY.md

Latest commit

 

History

History
119 lines (88 loc) · 5.91 KB

COMMUNITY.md

File metadata and controls

119 lines (88 loc) · 5.91 KB
Raw

Community

Getting Involved

🎃 Hacktoberfest 2026: We are participating! Looking for your first open-source PR? Check out our good first issues and join us on Matrix for maintainer office hours in October.

tunaOS is an open-source project building OCI-based Enterprise Linux desktops. We welcome contributors at all levels.

Contribute through Hive — no code needed. Your machine runs one task at a time with your signed-in AI CLI. The relay alternates eligible School (OS) and Reef (apps) hives after each task. Your subscription quota or API charges apply. The guide explains prerequisites, verified just setup, credentials, and how to stop the relay with Ctrl+C.

Quick Start

  1. Try it: bootc switch --enforce-container-sigpolicy ghcr.io/tuna-os/yellowfin:gnome
  2. Report issues: GitHub Issues
  3. Read the docs: CONTRIBUTING.md, AGENT_GUIDE.md
  4. Add yourself: If your org uses TunaOS, add it to ADOPTERS.md

Contribution Ladder

Level What you do How to start
Compute donor Run your signed-in AI CLI for TunaOS tasks Follow the Hive donation guide
Tester Run images, report bugs Install any variant, open issues
Contributor Fix bugs, improve docs Good first issues, PRs welcome
Desktop maintainer Own a desktop flavor Build and test regularly, review PRs
Variant maintainer Own a distro variant Monitor builds, fix breakage
Core maintainer Architecture, CI, releases Sustained contribution + trust

Contributor recognition and attribution

We recognize contributors for the work they contribute, while taking care to distinguish human contributions from automated activity. Before publishing a contributor spotlight or counting a contribution toward the community's human-contributor metrics, maintainers should verify the commit author and the contributor's identity. This keeps public thanks meaningful and avoids attributing agent work to a person.

The shimonenator commits previously described as the project's first external human contribution were confirmed on 2026-08-13 to be authored by the Google Antigravity agent (antigravity). The first external human contributions landed and merged on 2026-08-14: tuna-os/docs#234 (QEMU/KVM guide by dchaudhari7177) and tuna-os/docs#239 (Gurnard Pantheon fix by Elonon901001).

External contributor onboarding is actively supported via the fork→PR loop, curated good first issue tasks, and weekly maintainer triage documented in CONTRIBUTING.md and docs/HACKTOBERFEST-2026.md.

Communication

  • GitHub Issues: Bug reports, feature requests, discussion
  • GitHub Discussions: General topics, ideas, Q&A
  • PR Reviews: All contributions reviewed within 48 hours
  • Matrix: #tunaos:reilly.asia — real-time chat, weekly release notes, monthly office hours (see below)

Matrix room cadence

The Matrix room is the project's real-time channel; this section documents its recurring structure so it doesn't rely on any one person's memory to keep going (#1136).

  • Weekly release notes (Fridays, mirroring the weekly boot report cadence): post a short summary of the week's Generate Release runs and any notable boot-report findings. Template:

    📦 This week in tunaOS — <date>

- Released: <variant/flavor list + dates, from `gh release list`>
- Boot health: <link to this week's boot-report issue>
- Notable changes: <1-3 bullets — new variant, fixed regression, etc.>
- Full changelog: <link to the release/CHANGELOG.md entry>

  • Monthly office hours (~30 min, announced 1 week ahead in the room): open Q&A / walkthrough slot. No fixed agenda beyond "bring questions."

  • #new-to-tunaos pinned message — entry points for someone new to the room:

    👋 New here? Start with one of these:

1. Donate AI CLI time — no code needed:
   → https://hub.tunaos.org/#contribute
2. Try it: bootc switch --enforce-container-sigpolicy ghcr.io/tuna-os/yellowfin:gnome
3. Pick a starter task: issues labeled "good first issue"
   → https://github.com/tuna-os/tunaOS/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22
4. Read CONTRIBUTING.md and COMMUNITY.md (this file) before your first PR

Questions are welcome any time — you don't need to wait for office hours.

  • Cross-posting GitHub Discussions: when a Discussions thread gets real engagement (multiple replies, a maintainer answer, a decision), drop a one-line summary + link into the room. Keeps the room aware of async-first conversations without duplicating them live.

Adoption Metrics

Metric Current
GitHub Stars Tracked via GitHub API
Downloads ghcr.io/tuna-os pull counts
Active variants Yellowfin, Albacore, Skipjack, Bonito, Redfin
Active desktops GNOME, GNOME 50, KDE, COSMIC, Niri
Adopters See ADOPTERS.md — organizations using TunaOS

Code of Conduct

See CODE_OF_CONDUCT.md. We follow the Contributor Covenant.

Project Governance

tunaOS is maintained by @hanthor with automated assistance from Hive agents. Decisions are made via GitHub Issues, PRs, and Architecture Decision Records. See MAINTAINERS.md for the maintainer playbook, TRIAGE-POLICY.md for issue triage SLAs, and RFC-PROCESS.md for architectural proposal governance.