Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.

An MR completes this bounty when it is merged into main with Closes #299 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.

Description

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.

Who might enjoy this

  • Community interests: Research, Tech, Community / knowledge sharing
  • Skills: python, data, docs
  • Experience: starter; work style: analytical.
  • Readiness: ready; bounty size: S (existing points tier; standard merge award stacks separately).

Current behavior and starting points

Source-reviewed against main cf05b29c6256dba70d0ebc09b22cc9867cdb786a on2026-10-18. Check current main and related issues/MRs before implementing so existing work is reused.

Relevant Files

Deliverables

  • A standard-library Python CLI reading a local public API JSON export, reporting counts by interest, skill, experience and effective readiness.
  • Flag unclassified items and interests with no starter-ready work; support readable and JSON output with deterministic ordering.
  • Include a tiny synthetic fixture with a positive match, missing metadata, assigned/in-review work and a deliberately empty intersection.

Dependencies and decisions

No prerequisite issue is required. Re-read current main and linked MRs before starting.

Acceptance criteria

  • [ ] Use python3 -m unittest on the fixture corpus; malformed input must produce an actionable nonzero exit and valid empty input a distinct empty report.
  • [ ] Run the CLI on a current catalog export and show Python + Starter + Ready and RF/SDR coverage counts matching a direct fixture calculation.
  • [ ] Record named baseline failures and the exact commands used. A behavior fix includes a real route/database/protocol check observed failing before the change. Knowledge work includes source traceability and reproducible reviewer evidence.
  • [ ] Run the affected app's existing checks. Explain any baseline failures rather than reporting a matching failure count as proof.

Try it locally

Start from the existing source files above. The following is the target demo your contribution should enable; a newly proposed script or fixture is part of the deliverable:

Create a local JSON fixture matching the explicit PublicBounty interface; use argparse, json and unittest from Python standard library. A live export is optional and read-only.

Use public or synthetic examples. Starter work should run without production access; explicitly name any software/device prerequisite before claiming it is ready.

Out of scope

  • No dependency packages, private GitLab token, network crawler, membership analysis, issue edits or new service.
  • Unrelated refactors, new services/providers, bulk dependency changes, production access changes, unrequested notifications, and copying private member material. Keep credentials and unresolved security findings outside the issue and repository.

For a coding agent and reviewer

Read AGENTS.md, applicable .cursor/rules/, app instructions and docs/contributing/agentic-bounty-review.md. Reuse the existing shared helpers, identity/access paths and app styling. Implement one bounded story and provide evidence the accepting app maintainer can reproduce. State updated / pre-release verified / released / live verified accurately.

A parent index carries no duplicate award for these child deliverables. Open one scoped MR using this issue's actual number after the closing keyword. Link your GitLab identity on Scoreboard; the existing merge webhook handles eligible points.

Catalog index: #258.

<!-- community-interest-bounty:2026-10-18:python-interest-coverage -->

Relevant files

Hints

No hints yet.

Activity

  • +50 Hugo Zarate earned S bounty Oct 25

Comments

No comments yet. Be the first to weigh in.

↑ Top