Comment 9 for bug 231316

Sending bugs via email only makes sense when the bug reception engine expects email. As a result, the appropriate means to map the behaviour of sending to the BTS is to send to the LP mail interface. While this has the side effect of possibly generating duplicate or inadequate bugs, this is also true for this functionality within the BTS. Further, it makes sense to leverage ptyhon-launchpad to generate canidate duplicates, etc.

Extending these tools to provide a different service, specifically to integrate with launchpad in a different way is really creating a new tool. Sending people to a webpage (e.g. https://launchpad.net/ubuntu/+filebug) doesn't map well to many of the use cases where a user might be using reportbug or reportbug-ng (e.g. not having a web browser installed).

Handling these requests is a different matter, but I submit that if LP is going to accept bugs by use of the email interface, it is no different to have LP accept bugs by use of various Debian BTS-oriented tools that may benefit from a patch. How these bugs are handled is a different matter: if triage of these is expected to be a considerable additional load (remembering that LP requires signed mail and a valid account), how is this different from any other use of the LP mail interface?