40open wiki tasks
40unassigned
3750points up for grabs

Wiki tasks by documentation section

Open app:wiki issues from the same catalog as all community bounties. These include wanted pages and wiki tooling. Read the issue scope and prerequisites before claiming.

XS · 25 S · 50 M · 100 L · 200 XL · 400

Wiki section: military (10 wiki tasks)

L · 200 pts military

#61 · GI Bill Complete Guide

Ready to start

L · 200 pts military

#62 · VA Claims Process

Ready to start

L · 200 pts military

#63 · MOS to Civilian Translation

Ready to start

M · 100 pts military

#64 · Transition Timeline & Checklist

Ready to start

M · 100 pts military

#65 · Security Clearance Guide

Ready to start

M · 100 pts military

#66 · OCONUS Transition Resources

Ready to start

M · 100 pts military

#68 · Veteran Benefits Overview

Ready to start

S · 50 pts military

#67 · Reserve & Guard Transition

Ready to start

S · 50 pts military

#291 · Turn Git-based training guidance into an offline practice exercise

Ready to start

S · 50 pts military

#292 · Analyze a fictional training survey with a beginner Python tool

Ready to start

Wiki section: cybersecurity (1 wiki task)

L · 200 pts cybersecurity

#72 · SOC Tooling Overview

Ready to start

Wiki section: server-guides (1 wiki task)

L · 200 pts server-guides

#86 · Kubernetes Setup

Ready to start

Wiki section: radio (14 wiki tasks)

L · 200 pts radio

#312 · DragonOS video guide: Build and validate a passive-radar learning experiment

Device access needed

M · 100 pts radio

#280 · Build a reproducible synthetic IQ learning bench

Ready to start

M · 100 pts radio

#302 · DragonOS video guide: Install and verify the latest DragonOS in a VM

Ready to start

M · 100 pts radio

#305 · DragonOS video guide: Receive FT8 through GQRX and WSJT-X

Device access needed

M · 100 pts radio

#306 · DragonOS video guide: Model a terrain-aware RF link with SignalServer

Ready to start

M · 100 pts radio

#307 · DragonOS video guide: Visualize HackRF sweeps through a local ZMQ client

Device access needed

M · 100 pts radio

#308 · DragonOS video guide: Receive your Meshtastic messages with GNU Radio and an SDR

Device access needed

M · 100 pts radio

#309 · DragonOS video guide: Decode your drone Remote ID with CatSniffer and Wireshark

Device access needed

M · 100 pts radio

#310 · DragonOS video guide: Use a remote SDR from SDR++ on a private lab network

Device access needed

M · 100 pts radio

#311 · DragonOS video guide: Automate a broadcast-band survey and bounded IQ recording

Device access needed

S · 50 pts radio

#279 · Create a hardware-free RF units practice CLI

Ready to start

S · 50 pts radio

#281 · Add a file-only first DragonOS learning lab

Dependency needed

S · 50 pts radio

#303 · DragonOS video guide: Receive broadcast FM with GQRX

Device access needed

S · 50 pts radio

#304 · DragonOS video guide: Decode your weather sensor with rtl_433 and SoapySDR

Device access needed

Wiki section: hardware (2 wiki tasks)

M · 100 pts hardware

#296 · Inspect a synthetic scan mesh before CAD cleanup

Ready to start

S · 50 pts hardware

#295 · Add an accessible cyberdeck power-budget worksheet

Ready to start

Wiki section: other (3 wiki tasks)

S · 50 pts other

#197 · Reconcile the contributor quickstart with current repo rules

Ready to start

S · 50 pts other

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

Ready to start

S · 50 pts other

#297 · Recognize canonical GitLab bounty links in wiki badges

Ready to start

Wiki section: general (2 wiki tasks)

S · 50 pts general

#284 · Build an accessible battery-units lesson for UxS beginners

Ready to start

S · 50 pts general

#290 · Create a provenance-first public strategy edition reading exercise

Ready to start

Wiki section: research (5 wiki tasks)

M · 100 pts research

#262 · Add a source-aware historical research timeline exercise

Ready to start

M · 100 pts research

#287 · Make the ACH teaching matrix editable and exportable

Ready to start

S · 50 pts research

#263 · Document one public-source-to-community-knowledge walkthrough

Ready to start

S · 50 pts research

#288 · Normalize a synthetic research chronology with Python

Ready to start

S · 50 pts research

#289 · Add a worked source-independence exercise for analysts

Ready to start

Wiki section: signalbot (2 wiki tasks)

M · 100 pts signalbot

#222 · Generate pilot service documentation from the manifest

Dependency needed

S · 50 pts signalbot

#236 · Create an accessible community-services architecture diagram

Ready to start

How to write a wiki page

You don't need to clone the repo. The fastest path is the GitLab Web IDE in your browser.

Path A — Edit in your browser (recommended for small changes)

  1. Sign in at git.juntogroups.org with your IrregularChat SSO (same login as score.irregulars.io)
  2. Open the issue you want to claim (e.g. wanted-page issues) and comment /assign me
  3. Click the Web IDE button on the repo (or press . on any GitLab page)
  4. Create the file at the path the issue tells you (e.g. apps/wiki/src/content/docs/privacy/tor-network-guide.md)
  5. Use this frontmatter at the top:
    ---
    title: "Your Page Title"
    description: "One-line SEO summary"
    tags: ["section", "specific-topic"]
    ---
  6. Write the page in Markdown. Reference other pages with [link](/section/slug/)
  7. Click Source Control → commit on a new branch → Create merge request
  8. Put Closes #<issue iid> in the MR description so the bounty auto-awards on merge

Path B — Clone locally (for big writeups, multi-page changes, or local preview)

git clone https://git.juntogroups.org/irregulars/irregularchat-monorepo.git
cd irregularchat-monorepo/apps/wiki
pnpm install
pnpm dev          # localhost:4321 — live-reload preview

# Create your page
vim src/content/docs/privacy/tor-network-guide.md

# Verify the build is clean
pnpm run build

# Commit and push to a new branch
git checkout -b wiki/tor-network-guide
git add src/content/docs/privacy/tor-network-guide.md
git commit -m "feat(wiki): add Tor Network Guide"
git push -u origin wiki/tor-network-guide
# Open the MR link printed in stdout

What happens after you push

  1. You open a merge request on GitLab — automated checks run
  2. A reviewer skims the page and approves (or asks for changes)
  3. Reviewer merges to main
  4. CI's deploy-wiki job builds and deploys to irregularpedia.org — live in ~30 seconds
  5. The scoreboard's GitLab webhook fires:
    • +40 merge_pr — for any merged PR
    • +10 wiki_edit — if the MR touches wiki content
    • +50 first_contribution — one-time bonus on your first ever PR
    • +25/50/100/200/400 bounty — if the MR closes a tagged issue

Tips

  • A solid stub beats no page. Don't wait until it's perfect — ship and iterate. Backlinks surface inbound interest as soon as the page exists.
  • Cite authoritative sources. Especially for cybersecurity, military, and privacy — readers act on this content.
  • Link sideways. Internal links to 2–3 related pages multiply discoverability via the auto-generated backlinks index.
  • Link your GitLab identity. Points match an admin-confirmed GitLab username or the MR commit author email on your Scoreboard account. Check your profile.

Other ways to earn points

  • Review someone else's PR — +15 pts (when the webhook detects an approval)
  • Fix a typo or expand an existing wiki page — +10 pts wiki_edit, doesn't need a wanted-page issue
  • Claim a non-wiki bounty — see the full bounties page
  • Answer a Q&A question — +15 pts, +40 more if it gets marked solved

Earn on the UxS Portal

Sign in at uxs.irregulars.io to check parts data, add store prices and keep them current. Points land here automatically.

  • Vote on whether a UxS data point is accurate — +1 pt uas_compliance_vote
  • Submit a new UxS data record for review — +2 pts uas_contribution
  • Your UxS data contribution is accepted — +10 pts uas_contribution_accepted
  • Your correction to UxS data is accepted — +15 pts uas_correction_accepted
  • Suggest an edit to a component (spec, image, description) — +5 pts uas_suggestion
  • Your component edit suggestion is accepted — +10 pts uas_suggestion_accepted
  • Add a store price with a product link — +2 pts uas_price_added
  • Another member upvotes a price you added (once per member) — +1 pt uas_price_upvoted
  • Vote a price up or down (once per price; not your own) — +1 pt uas_price_vote
  • Report an offer in or out of stock (once per offer per day) — +1 pt uas_stock_report

Price points go to members only: researched and seeded prices earn nothing, and you can't earn by voting on your own price. Each award counts once (one price-add per price, one vote per price, one stock report per offer per day).

Found a bug? Report it for points

Custom points awarded if accepted, based on severity. Use this for any non-trivial bug — UI glitches all the way up to security findings. Sensitive findings (RCE, key disclosure, auth bypass) should NEVER be posted as a public GitLab issue — submit through this form instead.

Severity rubric for security bugs:

  • low — 50 pts (info disclosure, harmless open redirect)
  • medium — 150 pts (CSRF, low-priv XSS, idempotency abuse)
  • high — 300 pts (auth bypass, SSRF, hardcoded secret, read-only SQLi)
  • critical — 500 pts (admin-priv auth bypass, mutating SQLi, key disclosure exposing user data, webhook signature bypass)
  • rce — 750 pts (remote code/command execution, sandbox escape)

Non-security bugs default to report_bug (25 pts) but admin can boost via admin_award.

See how many findings have been accepted and who has earned the most on the security program stats page.

Login to submit a bug report

For sensitive findings you can also email security@irregularchat.com or DM an admin on Signal. Do not post unfixed vulnerabilities as public issues.

Missed award? Claim it here

If you merged a PR and the webhook didn't auto-award your points (commit author email didn't match your scoreboard email, or your fork's email setting differed), paste the merged-PR URL below. If your scoreboard email or GitLab username matches the MR author, points award immediately. Otherwise an admin reviews within a few days.

Login to submit a claim

Tip: set your GitLab username on /profile to make future webhook auto-awards more reliable, even if your commit emails differ.

↑ Top