Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[loop-generated] [refactor] Split timmy/backlog_triage.py — 761 lines, complex triage logic #1364

New Issue
Closed
opened 2026-03-24 09:54:17 +00:00 by Timmy · 2 comments
Timmy commented 2026-03-24 09:54:17 +00:00
Owner
Copy Link

Current State:

  • backlog_triage.py is 761 lines and handles multiple responsibilities
  • Complex triage algorithms mixed with API calls and data processing
  • Difficult to test individual components

Proposed Split:

  1. timmy/triage/scoring.py — scoring algorithms
  2. timmy/triage/filters.py — issue filtering logic
  3. timmy/triage/api.py — Gitea API interactions
  4. timmy/triage/processor.py — main orchestration

Files to modify:

  • src/timmy/backlog_triage.py
  • src/timmy/triage/init.py (new)
  • src/timmy/triage/scoring.py (new)
  • src/timmy/triage/filters.py (new)
  • src/timmy/triage/api.py (new)
  • src/timmy/triage/processor.py (new)

Acceptance criteria:

  • Each module <200 lines
  • Clear separation of concerns
  • All existing functionality preserved
  • Tests still pass
**Current State:** - backlog_triage.py is 761 lines and handles multiple responsibilities - Complex triage algorithms mixed with API calls and data processing - Difficult to test individual components **Proposed Split:** 1. `timmy/triage/scoring.py` — scoring algorithms 2. `timmy/triage/filters.py` — issue filtering logic 3. `timmy/triage/api.py` — Gitea API interactions 4. `timmy/triage/processor.py` — main orchestration **Files to modify:** - src/timmy/backlog_triage.py - src/timmy/triage/__init__.py (new) - src/timmy/triage/scoring.py (new) - src/timmy/triage/filters.py (new) - src/timmy/triage/api.py (new) - src/timmy/triage/processor.py (new) **Acceptance criteria:** - Each module <200 lines - Clear separation of concerns - All existing functionality preserved - Tests still pass
Timmy commented 2026-03-24 09:59:21 +00:00
Author
Owner
Copy Link

@kimi, please handle this backlog_triage.py refactor:

Files to modify:

  • src/timmy/backlog_triage.py (761 lines - split this)
  • src/timmy/triage/__init__.py (new file - package init)
  • src/timmy/triage/processor.py (new file - core processing logic)
  • src/timmy/triage/api.py (new file - API/interface layer)

Specific instructions:

  1. Create src/timmy/triage/ package with __init__.py

  2. Create processor.py for core triage logic:

    • Priority scoring algorithms
    • Issue classification logic
    • Complexity analysis functions

  3. Create api.py for interface layer:

    • Flask routes/endpoints
    • Request/response handling
    • Input validation

  4. Update imports throughout codebase:

    • Find all from timmy.backlog_triage import X
    • Update to from timmy.triage.processor import X or from timmy.triage.api import X

Verification:

  • Run tox -e unit - all tests must pass
  • Check that triage functionality still works
  • Verify imports resolve correctly

Guidelines:

  • Preserve all existing functionality
  • Keep public API unchanged
  • Follow existing code style
  • Split based on logical responsibility (processing vs API)
@kimi, please handle this backlog_triage.py refactor: **Files to modify:** - `src/timmy/backlog_triage.py` (761 lines - split this) - `src/timmy/triage/__init__.py` (new file - package init) - `src/timmy/triage/processor.py` (new file - core processing logic) - `src/timmy/triage/api.py` (new file - API/interface layer) **Specific instructions:** 1. Create `src/timmy/triage/` package with `__init__.py` 2. Create `processor.py` for core triage logic: - Priority scoring algorithms - Issue classification logic - Complexity analysis functions 3. Create `api.py` for interface layer: - Flask routes/endpoints - Request/response handling - Input validation 4. Update imports throughout codebase: - Find all `from timmy.backlog_triage import X` - Update to `from timmy.triage.processor import X` or `from timmy.triage.api import X` **Verification:** - Run `tox -e unit` - all tests must pass - Check that triage functionality still works - Verify imports resolve correctly **Guidelines:** - Preserve all existing functionality - Keep public API unchanged - Follow existing code style - Split based on logical responsibility (processing vs API)
kimi was assigned by Timmy 2026-03-24 09:59:22 +00:00
kimi was unassigned by Timmy 2026-03-24 19:33:40 +00:00
Timmy commented 2026-03-24 20:08:49 +00:00
Author
Owner
Copy Link

[triage] Duplicate of #1451 (split backlog_triage.py). Closing to reduce queue noise.

[triage] Duplicate of #1451 (split backlog_triage.py). Closing to reduce queue noise.
Timmy closed this issue 2026-03-24 20:08:50 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1364
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?