--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
drafting spec…
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
--- name: Feature Request slug: feature-request type: process status: running version: 4.2.1 released: "1968-01-01" maintainer: whoever-sent-the-email dependencies: - optimism - misunderstanding-of-engineering-effort - a-slack-channel-no-one-checks - good-intentions license: CC-BY-SA (Credit the asker. Accept the blame.) tags: - process - product - hope - backlog - eternal ---
A document that converts hope into a ticket, and a ticket into a number, and a number into silence.
enhancement, nice-to-have, someday, wontfix.| ID | Description | Status |
|---|---|---|
| BUG-001 | Request submitted in 2019 still marked "under review" | Won't fix |
| BUG-002 | User who requested the feature is no longer at the company | By design |
| BUG-003 | Feature shipped does not match feature requested | Closed as resolved |
| BUG-004 | Duplicate detection fails. Always. | Known |
| BUG-005 | "We'll look into this" interpreted as promise | User error |
ERR_NOT_IN_SCOPE Request valid. Quarter full. Try again.
ERR_ALREADY_EXISTS It does exist. You haven't found it yet.
ERR_TOO_NICHE Fewer than 500 users share your exact pain.
ERR_TOO_BROAD "Make it better" is not actionable.
ERR_PRODUCT_DISAGREES The feature exists internally. It will not ship.
ERR_WONTFIX A decision was made. The reasoning was not documented.
valid.Will my request be implemented? It is in the backlog, which is a place requests go to be preserved, not necessarily executed.
How long until I hear back? You have already heard back. The auto-reply was the response.
Can I vote on other requests? Yes. Voting data is collected. Its relationship to prioritization is spiritual, not causal.
What is the best way to write a feature request? Describe the problem, not the solution. Include context. Keep it short. This advice is given freely and followed rarely.
v4.2.1 Added "we're tracking this" as a valid resolution statev3.0.0 Migrated from email to ticketing system. Volume tripled.v2.1.0 Introduced upvoting. Introduced the illusion of democracy.v1.0.0 Someone asked for something. Someone else wrote it down.