Issue tracker visualization

Open
#236 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
github

Research direction

Start by reading PROGRESS.md and the existing explorer page to see how project state is currently presented, then inventory the available issue/PR data sources (GitHub API, GitHub Projects). Done means a documented decision on where the view lives and what it reads from, plus a visual grouping of open, in-progress and done issues by area (harvest, OCR, reading, vocabulary, explorers).

Written by the indexing model from the issue text.

Description

enhancement process documentation

Raised by Robin. A visual view of this repo's issues and PRs — what is open, in progress and done, by area (harvest, OCR, reading, vocabulary, explorers). To decide: where it lives (explorer page, PROGRESS.md, GitHub Projects board) and what it reads from.

🤖 Generated with Claude Code

Dominant language
Python
Stars
0
Forks
0
Avg merge
1h 11m
Merged PRs (30d)
413

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Robin-IA/Congressional-Letters-Dev

All issues in Robin-IA/Congressional-Letters-Dev

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.