Skip to content

docs(backlog): set exact 100-open-issue target #301

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dDevAhmed merged 2 commits into from
Nov 14, 2026
Merged

docs(backlog): set exact 100-open-issue target #301

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bfcda06
docs(backlog): align active issue target with 80-100
dDevAhmed Nov 13, 2026
00d9d98
docs(backlog): set exact 100-open-issue target
dDevAhmed Nov 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/contributing/wave-backlog-plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
# StellarForge CLI — Stellar Wave Backlog Plan

**Backlog target:** 120 contributor issues
**Active backlog target:** exactly 100 open GitHub issues per repository, with each contributor-facing issue independently actionable and evidence-backed.

The original SW-001–SW-120 catalogue is a candidate inventory, not a quota. Count only currently open issues toward the 100-issue target; exclude pull requests and closed issues. Reconcile every candidate against current `main`, open and merged pull requests, and existing contributor assignments before creating or counting it. Exclude maintainer-only and release-administration tasks from contributor backlog totals. Do not create duplicate, artificial, or already-completed work. Stellar Wave activation and Drips point allocation remain suspended until explicitly authorized.

This plan defines the dependency graph and contributor taxonomy before GitHub issue creation. It is designed to maximize parallel contribution while preserving the frozen architecture in `docs/contributing/wave-architecture.md`.

Expand Down
Loading