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.
41 of 154 bounties. Choose something you enjoy; check its prerequisites before claiming.
bcw-mcp (2)
#215 · Exercise BCW MCP with a real protocol client
BCW tools remain usable by coding agents after dependency and API changes.
#47 · Add `bcw_search` tool to find BCTs by free-text description
Today the BCW MCP exposes the canon and recommendations but a user has to know which BCT they want. A simple text-search tool over BCT names and descriptions makes the canon discoverable.
event-service (1)
#210 · Create an editable event debrief draft
An organizer can turn a completed event into useful follow-up notes.
fieldnotes (7)
#26 · Article scheduled publishing — submit now, publish at future date
Authors should be able to draft an article and schedule it to publish at a specific time (newsletter cadence, embargoed announcements, weekend publishing).
#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.
#235 · Make published Field Notes articles readable in print
Readers can print a useful article or save a clean PDF.
#264 · Copy a traceable citation for a public Field Notes article
Article pages have an Original Source link and selection-link copying, but no citation action combining article title, author, canonical public URL and dates.
#266 · Show missing image descriptions before publishing a Field Note
Image insertion currently permits an optional caption/alt prompt and Markdown preview. Add a lightweight author-visible check for empty Markdown image descriptions, with location hints and no automatic rewriting.
#285 · Add an opt-in reproducible bench-report draft preset
Field Notes already has a Markdown draft editor. Add one opt-in starter outline so hobbyists can publish useful bench observations with setup, units, uncertainty and reproducible evidence.
qa-form (4)
#269 · Copy an answer-level link that preserves Q&A group context
Answers already have answer-{id} anchors and question routes accept group context. Add a discoverable per-answer copy link so discussions can cite the exact answer without copying its protected content.
#270 · Make answer citation inputs clear to keyboard and screen-reader users
Q&A supports up to five source URLs, but the current dynamic source rows use placeholder-only inputs and plus/minus text buttons. Improve this existing workflow without adding a new citation system.
#271 · Offer a concise evidence-first answer starter
The answer form already has free text, source URLs and an optional confidence slider. Offer a small optional outline that helps a member separate an observed result, cited explanation, limitations and a useful next step.
#273 · Protect an unsent Q&A answer when leaving the page
The client stores a local view identifier but the reviewed answer form has no unsent-text navigation guard. Add a memory-only dirty-state warning so a researched answer is less easily lost without persisting private answer text in browser storage.
search-mcp (2)
#194 · Add a bounty-detail tool to Search MCP
Agent users can inspect the next task without manually navigating several pages.
#216 · Exercise Search MCP and bounty tools with a real client
Agent users can rely on working discovery and search tool contracts.
search-service (4)
#198 · Build a repeatable community-search quality benchmark
Search changes can be evaluated against real community information needs.
#199 · Add published Field Notes as a community-search source
Members discover reviewed public articles alongside existing wiki and Q&A results.
#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.
signal-bot (2)
#120 · Refactor: share community-rollup logic between !rollup --full and 02:00 cron
Two implementations of "build a 7-day community rollup → publish to Outline" exist in the signal-bot:
#147 · Update the canonical rolling community digest document in place
Keep one stable, bookmarkable Community Digest document rather than creating a new overlapping rollup every day. The selected implementation strategy is update-in-place; bulk deletion/archival of existing documents is outside this story.
task-exchange (3)
#275 · Add manual task starters for research, writing and verification work
The task form offers a generic Checklist insertion and AI enhancement. Add deterministic opt-in starters for a source-check, a wiki correction and a synthetic lab verification task so non-coding contributions are scoped as clearly as code.
#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.
#278 · Give task reviewers a practical source-quality review aid
Detailed reviews currently offer numeric quality/accuracy/communication/timeliness ratings and free-text feedback. Add concise reviewer guidance for knowledge work so acceptance means traceable sources and reproducible evidence, not plausible prose.
teamco (1)
#255 · Validate synthetic transcript timing with an offline Python tool
Audio contributors can spot malformed transcript timing before reviewing a recording.
uxs-data (3)
#44 · Public diff viewer — show what changed in last UAS data update
uxs-data is the canonical UAS dataset. Updates happen periodically. A public `/diff/<timestamp>` page showing what records were added/changed/removed builds trust and helps consumers (wiki, signal-bot) handle migrations.
#213 · Parse CNAS source records into a staged UxS import
The current count-only source check becomes a useful reviewable import.
#214 · Show UxS source freshness and evidence state
Members understand the age and provenance of lookup information.
wiki (12)
#72 · Wiki page: SOC Tooling Overview
SOC Tooling Overview: create or improve a practical, source-checked guide for the community.
#262 · Add a source-aware historical research timeline exercise
The Chronologies and Timelines SAT page describes arranging events and checking gaps but has no worked chronology. Teach documentary research using publication dates and provenance rather than live operational information.
#280 · Build a reproducible synthetic IQ learning bench
The SDR and DragonOS guides identify signal-analysis tools but readers need a repeatable signal with a known answer. Add a file-only baseband exercise with original generated samples.
#287 · Make the ACH teaching matrix editable and exportable
The ACH guide contains a fixed C/I/N table. Give learners an editable local-only version with visible evidence identifiers and uncertainty, using a fictional non-operational example.
#296 · Inspect a synthetic scan mesh before CAD cleanup
The 3D-scanning guide highlights excessive mesh size and post-processing work. Add a read-only local teaching inspector for one simple documented mesh format with synthetic geometry.
#306 · DragonOS video guide: Model a terrain-aware RF link with SignalServer
- **Clickable video timestamps are required.** For each major step taken from the source video, provide the actual `MM:SS` (or `HH:MM:SS`) timestamp linked to that exact point in this issue's direct video URL using its `t=` offset. Map the numbered guide steps and their commands …
#203 · Add last-verified metadata to selected wiki guides
Readers can recognize documentation that has been checked recently.
#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.
#288 · Normalize a synthetic research chronology with Python
The chronology technique asks researchers to inspect sequences and gaps. Add a small local tool that makes timezone and precision differences explicit before drawing conclusions.
#289 · Add a worked source-independence exercise for analysts
The research guides emphasize citations and competing hypotheses; add a practical exercise showing why several articles repeating one originating statement are not independent confirmations.
#290 · Create a provenance-first public strategy edition reading exercise
The national-strategy index lists documents by year. Add a bounded exercise teaching readers to compare two public editions without mistaking an old edition or secondary summary for a current primary source.
#292 · Analyze a fictional training survey with a beginner Python tool
The training-event survey guide recommends pre/post comparison and CSV analysis. Provide an offline exercise that handles missing responses and changing denominators visibly.
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.