Clear filters

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

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

career-board (1)

M · 100 pts career-board

#211 · Let job posters reconfirm or close aging listings

Members spend less time following stale opportunities.

BackendUXFull stackProfessional developmentDecision needed

community-portal (2)

M · 100 pts community-portal

#227 · Qualify two-user collaborative document editing

Members can collaborate on a document and reopen a reliable saved result.

DevOpsTesting / QAFull stackCommunity / knowledge sharingDependency needed
M · 100 pts community-portal

#229 · Add scoped library uploads with visible progress and recovery

Members understand where a file will go and whether it has actually been published.

FrontendUXResearchFull stackPrivacyDependency needed

developer-portal (3)

L · 200 pts developer-portal

#128 · Logger adoption + lint backlog: developer-portal (88 biome errors)

Same shape as the teamco companion issue. developer-portal has:

FrontendAPI / MCPTechFull stackReady to start
M · 100 pts developer-portal

#38 · Generate per-app API client snippets from wrangler.toml routes

Developers don't know what endpoints each Worker exposes without reading source. Build a tool that ingests each app's `wrangler.toml` and source files and emits a one-page API reference with copy-paste TypeScript / curl examples.

FrontendAPI / MCPTechFull stackReady to start
M · 100 pts developer-portal

#243 · Document and contract-test one community API error vocabulary

Agent integrators can distinguish validation, unavailable service and denied access.

Testing / QAAPI / MCPTechFull stackReady to start

event-service (1)

M · 100 pts event-service

#28 · iCal feed per-user (`/ical/<token>.ics`) for personal calendar sync

Members RSVP to events but can't easily get them in Apple/Google Calendar. A signed iCal feed token lets users subscribe to their own events.

BackendAPI / MCPFull stackCommunity / knowledge sharingReady to start

fieldnotes (3)

M · 100 pts fieldnotes

#209 · Show Field Notes authors their review progress

An author can see which version is awaiting review and what to do next.

FrontendBackendResearchFull stackReady to start
M · 100 pts fieldnotes

#265 · Preview a Field Notes version diff before restoring content

Version history currently lists versions and immediately offers loading one into the editor after confirmation. Add a read-only comparison against the current draft so authors can inspect changes first.

FrontendBackendTesting / QAResearchTechFull stackReady to start
M · 100 pts fieldnotes

#267 · Download one owned Field Notes note as portable Markdown

Field Notes has private notes, share tokens and maintainer-only content export scripts. Provide member self-service backup for one note they own, without turning it into a public link or bulk export.

FrontendBackendTesting / QAFull stackPrivacyProfessional developmentReady to start

rss-reader (1)

M · 100 pts rss-reader

#206 · Manage Signal topic subscriptions from the RSS web UI

Members manage topic DMs without confusing them with saved OPML feed addresses.

FrontendAPI / MCPResearchFull stackCommunity / knowledge sharingDecision needed

scoreboard (9)

XL · 400 pts scoreboard

#50 · Single sign-on session sharing across all 12 Workers via shared cookie domain

**Architecture decision needed.** First compare the existing per-app OIDC/session flow with alternatives and document the selected trust boundary. A shared parent-domain cookie is a proposal, not an approved implementation requirement. Preserve isolation between services and do n…

FrontendBackendFull stackInfrastructurePrivacyDecision needed
M · 100 pts scoreboard

#192 · Show linked merge requests on bounty cards

Members can see implementation/review activity before claiming a task.

FrontendBackendFull stackCommunity / knowledge sharingReady to start
M · 100 pts scoreboard

#212 · Recommend bounties using member-selected skills

Members find enjoyable work based on interests they choose to share.

FrontendDataFull stackCommunity / knowledge sharingDecision needed
M · 100 pts scoreboard

#220 · Verify the mobile bounty-to-contribution journey

A member can find and understand a contribution from their phone.

Testing / QAMobile / PWAFull stackCommunity / knowledge sharingReady to start
M · 100 pts scoreboard

#251 · Measure and improve one bounty-page loading bottleneck

The growing bounty catalog stays usable on slower phones.

FrontendTesting / QAFull stackCommunity / knowledge sharingReady to start
S · 50 pts scoreboard

#193 · Copy a complete bounty brief for a coding agent

A contributor can hand one precise brief to their preferred coding agent.

FrontendUXFull stackAI / MLCommunity / knowledge sharingReady to start
S · 50 pts scoreboard

#233 · Improve keyboard navigation in the bounty journey

Keyboard users can browse, filter and inspect tasks comfortably.

FrontendAccessibilityFull stackCommunity / knowledge sharingReady to start
S · 50 pts scoreboard

#300 · Make bounty card descriptions readable without Markdown noise

Long issue previews show escaped backticks and Markdown markers in cards. Produce a readable, bounded text preview so members can compare tasks before opening their details.

FrontendTesting / QAUXTechFull stackCommunity / knowledge sharingReady to start
XS · 25 pts scoreboard

#20 · Add /bounties to the mobile bottom nav

Scope reconciliation (2026-10-18): current main already includes Bounties in buildBottomNav at apps/scoreboard/src/templates/base.ts. The old acceptance order predates the current Board / Bounties / Contribute / Me / More layout. Confirm the remaining navigation requirement befor…

FrontendMobile / PWAFull stackCommunity / knowledge sharingDecision needed

search-service (2)

S · 50 pts search-service

#201 · Show source and index freshness on search results

Members can tell how recent a result and its index actually are.

FrontendDataResearchFull stackReady to start
S · 50 pts search-service

#202 · Show partial-result states when a search backend fails

A member understands that a partial search did not inspect every source.

FrontendBackendResearchFull stackReady to start

task-exchange (5)

M · 100 pts task-exchange

#21 · Auto-create a Task Exchange task when a feature bounty is opened

**Decision needed before coding:** define one external bounty/task relation and state mapping. The first slice mirrors discovery and lifecycle only; Scoreboard remains authoritative for the bounty reward. Specify retries/idempotency and closing behavior before adding escrow or a …

BackendSQLFull stackCommunity / knowledge sharingDecision needed
M · 100 pts task-exchange

#208 · Resolve generated tasks when source work is completed

Completed Q&A and review work stops appearing as an open task.

BackendSQLFull stackCommunity / knowledge sharingDecision needed
M · 100 pts task-exchange

#277 · Export an accessible task brief as Markdown

Task details display description, subtasks, source links and skill requirements, but reviewed routes expose no portable Markdown brief. Let a member take a task into an editor or coding agent using only the information the existing view authorizes.

FrontendBackendAPI / MCPFull stackProfessional developmentCommunity / knowledge sharingReady to start
S · 50 pts task-exchange

#234 · Honor reduced-motion preferences in Task Exchange

Members who request reduced motion can use the task marketplace comfortably.

FrontendAccessibilityFull stackCommunity / knowledge sharingReady to start
S · 50 pts task-exchange

#276 · Help contributors assemble a concrete task evidence note

Submission forms currently ask for free-text links to work. Add a small opt-in evidence outline tailored to the task: deliverable, reproduction/checks, source references and remaining limitations.

FrontendTesting / QADocumentationResearchFull stackProfessional developmentReady to start

teamco (2)

M · 100 pts teamco

#24 · Award scoreboard points when a transport run completes

**Decision needed before coding:** agree which verified actor receives the existing action/tier and how undelivered awards are reconciled. Run completion must not fail because Scoreboard is down, but a fire-and-forget HTTP attempt alone is not delivery proof. Preserve immutable r…

BackendAPI / MCPFull stackCommunity / knowledge sharingDecision needed
S · 50 pts teamco

#242 · Improve TeamCO map legend and empty-state accessibility

A newcomer can interpret a workspace map and understand missing data.

FrontendAccessibilityMaps / geospatialFull stackCommunity / knowledge sharingReady to start

uxs-portal (1)

L · 200 pts uxs-portal

#45 · Migrate auth to Authentik OIDC PKCE via @irregularchat/shared-utils

UXS Portal pre-dates the shared-utils package. Per the README "refactor backlog" and the monorepo direction, migrate auth to the same OIDC PKCE flow used by every other Worker (task-exchange, fieldnotes, etc.). Removes a divergent auth path.

BackendReactsUAS / DronesFull stackPrivacyDecision needed

wiki (2)

S · 50 pts wiki

#263 · Document one public-source-to-community-knowledge walkthrough

The operationalization plan links knowledge services and implicit tasks, while research templates still emphasize external collaboration links. Show how a member can use the actual existing services through one manual, consent-aware workflow.

DocumentationUXResearchFull stackPrivacyCommunity / knowledge sharingReady to start
S · 50 pts wiki

#297 · Recognize canonical GitLab bounty links in wiki badges

Wiki bounty-reference parsing currently recognizes the legacy GitLab hostname, while current issue links use git.juntogroups.org and work_items paths. Make references in new community pages visible to the existing bounty-badge pipeline.

BackendTesting / QADocumentationTechFull stackCommunity / knowledge sharingReady to start

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