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.
8 of 154 bounties. Choose something you enjoy; check its prerequisites before claiming.
task-exchange (1)
#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.
wiki (7)
#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.
#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.
#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.
#291 · Turn Git-based training guidance into an offline practice exercise
The military training guide describes Git and Markdown benefits but learners need a small complete exercise they can run without organizational systems or real course material.
#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.