Community Bounties
Submit a merge request that closes one of these issues to earn points on merge — bounties stack on the standard +40 merge_pr award. New to the repo? See the Contributing guide or the step-by-step below.
Open includes work in progress and tasks waiting on prerequisites. App counts show the matching issues, not just work available to claim. Ready to start · In progress · In review.
Some bounties are visible to members only — sign in to see them.
Last checked with GitLab: . Status comes from GitLab using a 5-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.
21 of 154 bounties. Choose something you enjoy; check its prerequisites before claiming.
developer-portal (3)
#128 · Logger adoption + lint backlog: developer-portal (88 biome errors)
Same shape as the teamco companion issue. developer-portal has:
#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.
#243 · Document and contract-test one community API error vocabulary
Agent integrators can distinguish validation, unavailable service and denied access.
event-service (1)
#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.
fieldnotes (3)
#209 · Show Field Notes authors their review progress
An author can see which version is awaiting review and what to do next.
#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.
#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.
scoreboard (6)
#192 · Show linked merge requests on bounty cards
Members can see implementation/review activity before claiming a task.
#220 · Verify the mobile bounty-to-contribution journey
A member can find and understand a contribution from their phone.
#251 · Measure and improve one bounty-page loading bottleneck
The growing bounty catalog stays usable on slower phones.
#193 · Copy a complete bounty brief for a coding agent
A contributor can hand one precise brief to their preferred coding agent.
#233 · Improve keyboard navigation in the bounty journey
Keyboard users can browse, filter and inspect tasks comfortably.
#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.
search-service (2)
#201 · Show source and index freshness on search results
Members can tell how recent a result and its index actually are.
#202 · Show partial-result states when a search backend fails
A member understands that a partial search did not inspect every source.
task-exchange (3)
#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.
#234 · Honor reduced-motion preferences in Task Exchange
Members who request reduced motion can use the task marketplace comfortably.
#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.
teamco (1)
#242 · Improve TeamCO map legend and empty-state accessibility
A newcomer can interpret a workspace map and understand missing data.
wiki (2)
#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.
#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.
How to claim a bounty
First time? Get set up
- Sign in to git.juntogroups.org with your IrregularChat SSO.
- Create a Personal Access Token (PAT) at Settings → Access Tokens with the
write_repositoryscope. You'll use it as your password when cloning/pushing over HTTPS. - Clone the repo:
git clone https://git.juntogroups.org/irregulars/irregularchat-monorepo.git - 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.
- Pick an unclaimed issue and comment
/assign meon GitLab. - Branch off
main, implement the feature against the acceptance criteria. - Test it locally before opening the MR: after rebasing on
main, runcp .dev.vars.example .dev.vars && pnpm devfrom the app dir (→localhost:8787) and verify against the acceptance criteria. SSO login works with no secret — full walkthrough: Local Development & SSO. - Open a merge request with Closes #<iid> in the description.
- 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_editif the MR touchesapps/wiki/src/content/docs/**+50 first_contributionon 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.