While some low-hanging fruit could be programatically determined (eg patch only changes debian/watch as one of the current entries in the queue has) I did not mean the tags to be generated automatically.
Just to replace the current practice of prodding contributors in a comment to send to Debian - which may or may not be heeded - with the practice of flagging with for-debian. Which then can be programatically used to filter out from the view, be searched for, etc. If there is no consensus that a patch is better to go via Debian the tag can be reset easily. But once it is there it should be the equivalent of - please let's come back to the issue once it is in Debian and the BTS tracker linked.
While some low-hanging fruit could be programatically determined (eg patch only changes debian/watch as one of the current entries in the queue has) I did not mean the tags to be generated automatically.
Just to replace the current practice of prodding contributors in a comment to send to Debian - which may or may not be heeded - with the practice of flagging with for-debian. Which then can be programatically used to filter out from the view, be searched for, etc. If there is no consensus that a patch is better to go via Debian the tag can be reset easily. But once it is there it should be the equivalent of - please let's come back to the issue once it is in Debian and the BTS tracker linked.