Nothing answers "is this hardware request already modelled?" except a human #1047
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1047
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
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 possibleway 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
normalised model name and by vendor + model.
take it on trust - and invite them to say if the ports are wrong.
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 thetitles shared the word "Ultra". Guards were needed, not a better apology:
product lines rather than products;
+, soWiFi Mesh 3+andWiFi Mesh 3never collapse, andRB5009UPr+S+INandRB5009UPr+S+OUTstay separate - the catalogue has both.