Community Bounties
Bounty issues closed in GitLab. A closed issue and an awarded bounty are separate states; the cards show whether points were recorded.
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.
12 of 108 bounties. Choose something you enjoy; check its prerequisites before claiming.
community-portal (1)
#245 · Test self-host deployment dry-run guards with fake commands
Operators can trust preflight failures to stop before mutation.
developer-portal (1)
#253 · Generate an editable package dependency map with Python
Contributors understand which apps use shared packages before making a change.
event-service (1)
#29 · Award `share_event` points when an event is forwarded via Signal bot
**In review — implementation already exists in !300.** Coordinate with that MR and its author; do not start a duplicate implementation. This status is source/MR evidence, not a claim that release or live acceptance is complete.
rss-reader (1)
#250 · Add RSS/Atom date and deduplication regression fixtures
Community links remain correctly ordered when publishers vary their feeds.
scoreboard (1)
#299 · Audit bounty coverage by interest with a small Python report
Maintainers need a repeatable way to see whether each community interest has starter, ready and varied work. Build an offline report over an exported public bounty catalog rather than maintaining manual counts.
search-mcp (1)
#298 · Let Search MCP find bounties by community interest
The public bounty API gains recognized interest and skill filters, but bounties_open currently accepts only app, tier, unclaimed and limit. Let members ask their coding agent for Dragon, research or other interest-specific work.
search-service (1)
#244 · Measure search query plans on realistic synthetic data
Search optimization starts from measured bottlenecks and recall behavior.
wiki (5)
#204 · Generate actionable wiki broken-link reports
Wiki maintainers can repair useful documentation without manually checking every page.
#293 · Build an offline purple-team coverage-result checker
The Purple Team guide defines detected, visible-not-alerting, invisible and untested outcomes. Make that teaching model executable using original synthetic log/alert evidence, without running attacks.
#261 · Build a small offline acronym crosswalk for RF and security learning
The wiki has a cybersecurity glossary and an RF learning path, but the reviewed script inventory has no cross-topic acronym concordance. Help newcomers locate definitions without automatically inventing expansions.
#286 · Lint a local research bibliography with a small Python CLI
The research-citations guide recommends Zotero and citation traceability. Provide a small offline metadata check for a CSL-JSON export, without scraping sources or generating facts.
#294 · Create a synthetic email-header triage practice tool
The email-hardening guide explains phishing risks. Add a small offline teaching tool so learners can inspect original synthetic header examples without receiving or sending a phishing message.