Nothing answers "is this hardware request already modelled?" except a human #1047

Closed
opened 2026-11-08 08:09:00 +00:00 by jaylouisw · 0 comments
Owner

The backlog is ~800 open issues and the overwhelming majority are device requests. A steady
fraction ask for hardware that is already in the catalogue, and each of those costs a human reading
the body, checking grep -ril <model> devices/, and closing it. That is the most expensive possible
way to answer a question with a mechanical answer.

There is no tool for it, so the answer to "is this already modelled?" is currently "someone
remembers", which in practice means "nobody checked".

What is needed

  • Parse the subject out of a request title, normalise it, and look it up in the catalogue by
    normalised model name and by vendor + model.
  • Post a comment naming the vendor, model, file and category, so the reporter can verify rather than
    take it on trust - and invite them to say if the ports are wrong.
  • Report by default. Closing is opt-in and bounded.

What it must not do

Guess. A close that points at a different product wastes the reporter's time twice and teaches them
the maintainers do not read requests. No edit distance, no similarity scores.

The first draft of this tool closed three Ubiquiti requests pointing at roku/Ultra, because the
titles shared the word "Ultra". Guards were needed, not a better apology:

  • the vendor in the title must agree with the catalogue entry's vendor;
  • a model key must contain a digit or at least two words, because single generic words identify
    product lines rather than products;
  • normalisation must keep +, so WiFi Mesh 3+ and WiFi Mesh 3 never collapse, and
    RB5009UPr+S+IN and RB5009UPr+S+OUT stay separate - the catalogue has both.
The backlog is ~800 open issues and the overwhelming majority are device requests. A steady fraction ask for hardware that is already in the catalogue, and each of those costs a human reading the body, checking `grep -ril <model> devices/`, and closing it. That is the most expensive possible way to answer a question with a mechanical answer. There is no tool for it, so the answer to "is this already modelled?" is currently "someone remembers", which in practice means "nobody checked". ## What is needed - Parse the subject out of a request title, normalise it, and look it up in the catalogue by normalised model name and by vendor + model. - Post a comment naming the vendor, model, file and category, so the reporter can verify rather than take it on trust - and invite them to say if the ports are wrong. - Report by default. Closing is opt-in and bounded. ## What it must not do Guess. A close that points at a different product wastes the reporter's time twice and teaches them the maintainers do not read requests. No edit distance, no similarity scores. The first draft of this tool closed three Ubiquiti requests pointing at `roku/Ultra`, because the titles shared the word "Ultra". Guards were needed, not a better apology: - the vendor in the title must agree with the catalogue entry's vendor; - a model key must contain a digit or at least two words, because single generic words identify product lines rather than products; - normalisation must keep `+`, so `WiFi Mesh 3+` and `WiFi Mesh 3` never collapse, and `RB5009UPr+S+IN` and `RB5009UPr+S+OUT` stay separate - the catalogue has both.
Sign in to join this conversation.
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#1047
No description provided.