Start Here: Omi Discussions (Bounties, PRs, Roadmap & Questions)

[aaravgarg]

Omi Discussions (Bounties, PRs, Roadmap & Questions)

This is the place to ask questions, propose features, claim bounties, and show what you’ve built.
We’re a ship-first team—if you see something to improve, jump in and open a PR.

---

Quick Start

1. Browse issues & bounties on GitHub.
2. Pick something and start building—no permission needed.
3. Open a PR with a clear description (what/why/how) and link related issues.
4. Discuss here if you’re blocked, proposing scope, or want feedback.

---

Bounties (tl;dr)

• We do not lock bounties to people with 0 approved PRs. New folks: pick a bounty and submit. If you ship quality work, we’ll lock the next bounty on you.
• Merge target: everything merges to main.
• Payout flow: after your PR(s) are approved & merged, email [team@basedhardware.com](mailto:team@basedhardware.com) with:
  • Links to merged PRs + short impact summary
  • Full name, shipping address, email, PayPal, and phone number

No paid bounties available?
Comment @addbounty $<amount> (e.g., @addbounty $20), wait a few minutes, refresh, and propose your own bounty.

---

Rewards (per approved, significant PR)

• 1 PR: Free DEV KIT device (necklace or glasses, based on where you contribute)
• 2 PRs: 1 month of Omi subscription
• 5 PRs: 3 months of Omi subscription + special Contributor role on Discord
• 10 PRs: We’ll fly you to San Francisco to hang out with the Based Hardware team

Rewards stack as you hit each tier.

What counts as “significant”?

• ~2+ hours of focused work (or several smaller contributions that add up)
• A new feature or major bug fix
• Quality code with explanation, tests when relevant, and helpful docs/notes

---

Discussion Categories

• Announcements – Pinned updates from the team
• Help & How-To – Setup, environment, debugging
• Ideas / RFCs – Pitch features, get feedback, discuss APIs
• Bounties – Claim, coordinate, or propose new bounties (@addbounty $<amount>)
• Show & Tell – Demos, PRs, apps, community wins
• Q&A / Support – Short questions that don’t need a full issue

Tip: Prefix titles with [RFC], [Bounty], [Idea], [Help], or [Show] for faster triage.

---

Lightweight Templates

Feature Request

Problem / Context
(What hurts today? Who is affected?)

Proposed Solution
(What should happen? UX/API sketch if relevant.)

Alternatives Considered
(What else did you try? Why not?)

Scope / Acceptance
(What’s in/out? How will we know it’s done?)

Bug Report

Environment
(OS, device, app version, firmware, commit hash)

Steps to Reproduce
(1…2…3…)

Expected vs. Actual
(What should happen? What happened instead?)

Logs / Screens / Minimal Repro
(Links, screenshots, traceback, small code sample)

Show & Tell

What you built
(1–2 sentences + link/video/gif)

Why it matters
(Problem solved, impact, next steps)

How to try it
(Install/run instructions)

---

PR Guidelines (fast merges happen when…)

• Clear title and a concise why
• Linked issues/bounties and scope called out
• Tests or a manual test plan when appropriate
• Docs updated if behavior or UX changed
• Small, reviewable commits; avoid unrelated changes

---

Code of Conduct

Be kind, be specific, and respect reviewers’ time. Disagree with ideas, not people.
Report issues privately to team@basedhardware.com if needed.

---

New Here? Introduce Yourself

Reply below with:

• What you want to build (one sentence)
• Your skills / interests
• Links to past work (optional)

Welcome aboard—can’t wait to see what you ship 🚀