Getting good bug reports
schrieb Ian Jackson am 2011-05-25 13:46:
> I wrote:
>> Brian May writes ("Re: Getting good bug reports"):
>>> [ explanation of how reportbug is broken right now ]
>> We could solve this if we can avoid the slippery slope problem.
>> Or to put it another way, I would have no objection to an http
>> submission interface to the BTS, provided that everyone understands
>> and agrees that:
I do note think that it exactly needs to be HTTP, but just something
without MTA and a online connection. HTTP is a well understood protocol,
usually working on port 80 - which is one of the least blocked ports -
with proxies - for those networks where direct access is not allowed.
Using port 80 brings advantages in the aspect of having a direct
connection from most hosts.
Using HTTP brings proxy support, but opens the door for easy to
implement additional bug reporting facilities without the control and
quality constraints that come with reportbug.
Why not use some simple non-HTTP-protocol on port 80?
For the workflow I could imagine:
- Try online submission
- if that fails, try email submission
- if that fails, save the bug report to a file and give the user
instructions how to submit the bug later, maybe from a different host.
Engineers motto: cheap, good, fast: choose any two
Patrick Strasser <patrick dot strasser at student dot tugraz dot at>
Student of Telemati_cs_, Techn. University Graz, Austria
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com