Wiki contributions & points help
The community wiki is open-source. Pick a wanted page, write it, earn points. Every accepted PR adds to your scoreboard.
40 wiki tasks out of 154 open community bounties. Counts below are grouped by wiki documentation section, not application. Signal bot documentation tasks are a subset of all Signal bot work.
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.
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.
Wiki section: military (10 wiki tasks)
#61 · GI Bill Complete Guide
#62 · VA Claims Process
#63 · MOS to Civilian Translation
#64 · Transition Timeline & Checklist
#65 · Security Clearance Guide
#66 · OCONUS Transition Resources
#68 · Veteran Benefits Overview
#67 · Reserve & Guard Transition
#291 · Turn Git-based training guidance into an offline practice exercise
#292 · Analyze a fictional training survey with a beginner Python tool
Wiki section: cybersecurity (1 wiki task)
#72 · SOC Tooling Overview
Wiki section: server-guides (1 wiki task)
#86 · Kubernetes Setup
Wiki section: radio (14 wiki tasks)
#312 · DragonOS video guide: Build and validate a passive-radar learning experiment
#280 · Build a reproducible synthetic IQ learning bench
#305 · DragonOS video guide: Receive FT8 through GQRX and WSJT-X
#308 · DragonOS video guide: Receive your Meshtastic messages with GNU Radio and an SDR
#309 · DragonOS video guide: Decode your drone Remote ID with CatSniffer and Wireshark
#311 · DragonOS video guide: Automate a broadcast-band survey and bounded IQ recording
#279 · Create a hardware-free RF units practice CLI
#281 · Add a file-only first DragonOS learning lab
#303 · DragonOS video guide: Receive broadcast FM with GQRX
Wiki section: hardware (2 wiki tasks)
#296 · Inspect a synthetic scan mesh before CAD cleanup
#295 · Add an accessible cyberdeck power-budget worksheet
Wiki section: other (3 wiki tasks)
#197 · Reconcile the contributor quickstart with current repo rules
#203 · Add last-verified metadata to selected wiki guides
#297 · Recognize canonical GitLab bounty links in wiki badges
Wiki section: general (2 wiki tasks)
#284 · Build an accessible battery-units lesson for UxS beginners
#290 · Create a provenance-first public strategy edition reading exercise
Wiki section: research (5 wiki tasks)
#262 · Add a source-aware historical research timeline exercise
#287 · Make the ACH teaching matrix editable and exportable
#263 · Document one public-source-to-community-knowledge walkthrough
#288 · Normalize a synthetic research chronology with Python
#289 · Add a worked source-independence exercise for analysts
Wiki section: signalbot (2 wiki tasks)
#222 · Generate pilot service documentation from the manifest
#236 · Create an accessible community-services architecture diagram
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)
- Sign in at git.juntogroups.org with your IrregularChat SSO (same login as score.irregulars.io)
- Open the issue you want to claim (e.g. wanted-page issues) and comment
/assign me - Click the Web IDE button on the repo (or press . on any GitLab page)
- Create the file at the path the issue tells you (e.g.
apps/wiki/src/content/docs/privacy/tor-network-guide.md) - Use this frontmatter at the top:
--- title: "Your Page Title" description: "One-line SEO summary" tags: ["section", "specific-topic"] --- - Write the page in Markdown. Reference other pages with
[link](/section/slug/) - Click Source Control → commit on a new branch → Create merge request
- 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
- You open a merge request on GitLab — automated checks run
- A reviewer skims the page and approves (or asks for changes)
- Reviewer merges to
main - CI's
deploy-wikijob builds and deploys to irregularpedia.org — live in ~30 seconds - 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/400bounty — 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.
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.
Tip: set your GitLab username on /profile to make future webhook auto-awards more reliable, even if your commit emails differ.