Clear filters

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

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

bcw-mcp (2)

M · 100 pts bcw-mcp

#215 · Exercise BCW MCP with a real protocol client

BCW tools remain usable by coding agents after dependency and API changes.

Testing / QAAPI / MCPResearchTechReady to start
S · 50 pts bcw-mcp

#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.

DataAPI / MCPResearchTechReady to start

event-service (1)

M · 100 pts event-service

#210 · Create an editable event debrief draft

An organizer can turn a completed event into useful follow-up notes.

FrontendDocumentationResearchCommunity / knowledge sharingReady to start

fieldnotes (7)

M · 100 pts fieldnotes

#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).

FrontendBackendResearchCommunity / knowledge sharingReady to start
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
S · 50 pts fieldnotes

#235 · Make published Field Notes articles readable in print

Readers can print a useful article or save a clean PDF.

FrontendDesignResearchCommunity / knowledge sharingReady to start
S · 50 pts fieldnotes

#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.

FrontendDocumentationResearchProfessional developmentCommunity / knowledge sharingReady to start
S · 50 pts fieldnotes

#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.

FrontendTesting / QAAccessibilityResearchTechCommunity / knowledge sharingReady to start
S · 50 pts fieldnotes

#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.

FrontendDocumentationUXsUAS / DronesRF / SDR (Dragon)ResearchHardware / fabricationReady to start

qa-form (4)

S · 50 pts qa-form

#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.

FrontendTesting / QAResearchProfessional developmentCommunity / knowledge sharingReady to start
S · 50 pts qa-form

#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.

FrontendTesting / QAAccessibilityResearchTechCommunity / knowledge sharingReady to start
S · 50 pts qa-form

#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.

FrontendDocumentationUXResearchPurple teamCommunity / knowledge sharingReady to start
S · 50 pts qa-form

#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.

FrontendTesting / QAResearchPrivacyCommunity / knowledge sharingReady to start

search-mcp (2)

M · 100 pts search-mcp

#194 · Add a bounty-detail tool to Search MCP

Agent users can inspect the next task without manually navigating several pages.

BackendAPI / MCPResearchTechReady to start
M · 100 pts search-mcp

#216 · Exercise Search MCP and bounty tools with a real client

Agent users can rely on working discovery and search tool contracts.

Testing / QAAPI / MCPResearchTechReady to start

search-service (4)

M · 100 pts search-service

#198 · Build a repeatable community-search quality benchmark

Search changes can be evaluated against real community information needs.

DataTesting / QAResearchAI / MLReady to start
M · 100 pts search-service

#199 · Add published Field Notes as a community-search source

Members discover reviewed public articles alongside existing wiki and Q&A results.

BackendSQLResearchCommunity / knowledge sharingReady to start
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

signal-bot (2)

M · 100 pts signal-bot

#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:

BackendAPI / MCPResearchCommunity / knowledge sharingReady to start
M · 100 pts 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.

BackendAPI / MCPResearchCommunity / knowledge sharingReady to start

task-exchange (3)

S · 50 pts task-exchange

#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.

FrontendDocumentationUXResearchPurple teamCommunity / 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
S · 50 pts task-exchange

#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.

FrontendDocumentationUXResearchWarfare studiesPurple teamProfessional developmentReady to start

teamco (1)

S · 50 pts teamco

#255 · Validate synthetic transcript timing with an offline Python tool

Audio contributors can spot malformed transcript timing before reviewing a recording.

PythonAudioResearchTechReady to start

uxs-data (3)

M · 100 pts uxs-data

#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.

DataSQLsUAS / DronesResearchReady to start
M · 100 pts uxs-data

#213 · Parse CNAS source records into a staged UxS import

The current count-only source check becomes a useful reviewable import.

BackendDatasUAS / DronesResearchReady to start
S · 50 pts uxs-data

#214 · Show UxS source freshness and evidence state

Members understand the age and provenance of lookup information.

FrontendDatasUAS / DronesResearchReady to start

wiki (12)

L · 200 pts wiki

#72 · Wiki page: SOC Tooling Overview

SOC Tooling Overview: create or improve a practical, source-checked guide for the community.

DocumentationSecurityResearchPurple teamReady to start
M · 100 pts wiki

#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.

DataDocumentationResearchWarfare studiesProfessional developmentReady to start
M · 100 pts wiki

#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.

PythonDataAudioRF / SDR (Dragon)ResearchReady to start
M · 100 pts wiki

#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.

FrontendDataAccessibilityResearchWarfare studiesReady to start
M · 100 pts wiki

#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.

PythonHardware / networks3D / graphicssUAS / DronesResearchHardware / fabricationReady to start
M · 100 pts wiki

#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 …

Testing / QADocumentationShellMaps / geospatialPhysics / simulationRF / SDR (Dragon)ResearchTechReady to start
S · 50 pts wiki

#203 · Add last-verified metadata to selected wiki guides

Readers can recognize documentation that has been checked recently.

FrontendDocumentationResearchCommunity / knowledge sharingReady to start
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

#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.

PythonDataDocumentationResearchWarfare studiesReady to start
S · 50 pts wiki

#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.

DataDocumentationResearchWarfare studiesCommunity / knowledge sharingReady to start
S · 50 pts wiki

#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.

DataDocumentationResearchWarfare studiesProfessional developmentReady to start
S · 50 pts wiki

#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.

PythonDataDocumentationResearchWarfare studiesProfessional developmentReady 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