Clear filters

3 of 154 bounties. Choose something you enjoy; check its prerequisites before claiming.

3open
3unassigned
400points up for grabs
XS · 25 S · 50 M · 100 L · 200 XL · 400

simplex-bot (3)

L · 200 pts simplex-bot

#167 · Reconcile SimpleX Q&A lifecycle and remaining delivery guarantees

**Current remaining scope, reviewed 2026-10-18:** Resolution, clarification, sharing, soft deletion, stored rejection reason and group reminder code already exist. Reconcile prior MRs/awards against current source and verify those paths rather than re-porting them. Document remai…

BackendTesting / QAAPI / MCPTechCommunity / knowledge sharingIn review
M · 100 pts simplex-bot

#162 · Reconcile and verify the existing SimpleX member lifecycle

**Current remaining scope, reviewed 2026-10-18:** Pending/queue and member approval/removal handlers already exist. Read the parity ledger and SIMPLEX_ADMIN_VERIFICATION documentation. Reconcile prior implementation MRs and award identity first, then verify the remaining native r…

BackendTesting / QAAPI / MCPTechCommunity / knowledge sharingIn review
M · 100 pts simplex-bot

#163 · Reconcile the shipped SimpleX group-directory lifecycle

**Current remaining scope, reviewed 2026-10-18:** Directory listing/unlisting, cache refresh and category commands already exist in source and the ledger records their deployment. Reconcile the original implementation/award and verify command behavior before closing. Destructive …

BackendTesting / QAAPI / MCPTechCommunity / knowledge sharingIn review

How to claim a bounty

First time? Get set up

  1. Sign in to git.juntogroups.org with your IrregularChat SSO.
  2. Create a Personal Access Token (PAT) at Settings → Access Tokens with the write_repository scope. You'll use it as your password when cloning/pushing over HTTPS.
  3. Clone the repo: git clone https://git.juntogroups.org/irregulars/irregularchat-monorepo.git
  4. On your Scoreboard profile, set your GitLab username so merges auto-credit you, and link your Signal account (+50 pts on first link).

Claim a bounty

Use the Development board: Ready → In progress → In review → Closed. Move the issue as work advances; assignment also marks it in progress here.

  1. Pick an unclaimed issue and comment /assign me on GitLab.
  2. Branch off main, implement the feature against the acceptance criteria.
  3. Test it locally before opening the MR: after rebasing on main, run cp .dev.vars.example .dev.vars && pnpm dev from the app dir (→ localhost:8787) and verify against the acceptance criteria. SSO login works with no secret — full walkthrough: Local Development & SSO.
  4. Open a merge request with Closes #<iid> in the description.
  5. On merge to main, GitLab closes the referenced issue and the webhook awards points to the matched MR author. A merge that only mentions an issue does not complete its bounty. Check the Completed tab and bounty activity; use Missed award if credit needs review.

The card shows the bounty tier · merge_pr (+40) is awarded on top. Additional bonuses stack automatically:

  • +10 wiki_edit if the MR touches apps/wiki/src/content/docs/**
  • +50 first_contribution on your first ever merged PR (one-time)

Points land when your GitLab username (set on your profile) or commit email matches your Scoreboard account. For the full walkthrough see the Contributing guide, or recover a missed award at /contribute/claim.

↑ Top