Docs: no device request is ever closed as impossible #1209

Merged
jaylouisw merged 1 commit from docs/never-impossible into main 2026-11-09 13:40:03 +00:00
Owner

A device that cannot be modelled yet is still a real device that someone asked for. Closing that request trades away the evidence that a person wanted it, in exchange for a tidier backlog.

docs/RESOLUTIONS.md states the rule, linked from CONTRIBUTING and from the port-table section of MAINTAINING.md, with the three cases that used to end in a close:

  • no conventional port count -> a stated configuration in the label (OptiXtrans E6616 (14x B1LDCD), OptiXtrans E6608 (6x B1LDCD, DC chassis)), not a refusal;
  • no Ethernet ports at all -> an RF radio, a mesh extender, a cellular modem: "it has no Ethernet port" is a fact about the box, not a reason to forget the request;
  • source unreachable today -> the issue keeps which table was missing and where the search stopped, so the next attempt starts there instead of at the beginning.

The only close this project uses for a device request is one where the catalogue answers it, and the comment names the file that does.

Six requests closed on the old reasoning are reopened with that comment: #54, #167, #360, #362, #374, #387. #387 is the sharpest - the Teltonika RUTX12 has four gigabit ports, so it was never a ports problem at all.

Suite: 115 suites, 5,361 assertions, 0 failed.

A device that cannot be modelled *yet* is still a real device that someone asked for. Closing that request trades away the evidence that a person wanted it, in exchange for a tidier backlog. `docs/RESOLUTIONS.md` states the rule, linked from CONTRIBUTING and from the port-table section of MAINTAINING.md, with the three cases that used to end in a close: - **no conventional port count** -> a *stated* configuration in the label (`OptiXtrans E6616 (14x B1LDCD)`, `OptiXtrans E6608 (6x B1LDCD, DC chassis)`), not a refusal; - **no Ethernet ports at all** -> an RF radio, a mesh extender, a cellular modem: "it has no Ethernet port" is a fact about the box, not a reason to forget the request; - **source unreachable today** -> the issue keeps which table was missing and where the search stopped, so the next attempt starts there instead of at the beginning. The only close this project uses for a device request is one where the catalogue answers it, and the comment names the file that does. Six requests closed on the old reasoning are reopened with that comment: #54, #167, #360, #362, #374, #387. #387 is the sharpest - the Teltonika RUTX12 has four gigabit ports, so it was never a ports problem at all. Suite: 115 suites, 5,361 assertions, 0 failed.
Docs: no device request is ever closed as impossible
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Test (Node 18) (pull_request) Successful in 1m47s
CI / Test (Node 20) (pull_request) Successful in 1m41s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 1m38s
7b5cb10922
A device that cannot be modelled *yet* is still a real device someone asked for. Closing that request
trades away the evidence that a person wanted it, in exchange for a tidier backlog.

`docs/RESOLUTIONS.md` states the rule and the three cases that used to end in a close:

- **no conventional port count** -> a *stated* configuration in the label (`OptiXtrans E6616 (14x
  B1LDCD)`, `OptiXtrans E6608 (6x B1LDCD, DC chassis)`), not a refusal;
- **no Ethernet ports at all** -> an RF radio, a mesh extender, a cellular modem: "it has no Ethernet
  port" is a fact about the box, not a reason to forget the request;
- **source unreachable today** -> the issue keeps which table was missing and where the search
  stopped, so the next attempt starts there.

The only close this project uses for a device request is one where the catalogue answers it, with
the comment naming the file that does.

Six requests that had been closed on the old reasoning are reopened with that comment: #54, #167,
#360, #362, #374, #387. #387 is the sharpest example - the Teltonika RUTX12 has four gigabit ports,
so it was never a ports problem at all.

Suite: 115 suites, 5,361 assertions, 0 failed.
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-09 13:39:59 +00:00
jaylouisw force-pushed docs/never-impossible from 7b5cb10922
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 11s
CI / Test (Node 18) (pull_request) Successful in 1m47s
CI / Test (Node 20) (pull_request) Successful in 1m41s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 1m38s
to dfb28f69cd
All checks were successful
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 10s
CI / Test (Node 18) (pull_request) Successful in 1m47s
CI / Test (Node 20) (pull_request) Successful in 1m43s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 1m35s
2026-11-09 13:40:01 +00:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1209
No description provided.