Email or username:

Password:

Forgot your password?
Hector Martin

Idle thought spun off from the prior discussion: If a bug reporter doesn't just report the bug, but debugs it and tells you exactly what went wrong and why the code is broken, then you should credit them with Co-developed-by, not Reported-by.

Debugging is just as much a part of development as actually writing the code is, and deserves equal credit. A strict reading of the kernel contribution guidelines doesn't imply this would be incorrect usage either. The only catch is the docs say C-d-b needs to be followed by a signoff, which would be unnecessary in this case (as that is about *copyright ownership/licensing* which only applies to writing the actual code), but an extra signoff never hurt anybody so shrug.

5 comments
joey

@marcan time for a new tag: Debugged-by:

Psentee

@joey @marcan Diagnosed-by?

But yeah, almost all of the tricky bugfixes I did (not in kernel, but it seems universal in complex software) were absolutely trivial code changes (like "swap two lines of code" trivial). Reproducing the problem, tracing the exact sequence of events leading to the symptoms, finding mismatch of expectations between two components – that's where the real work was.

Like in that old joke: "hitting machine with a hammer $0.01; knowing where to hit it $99.99"

Ayke van Laethem

@marcan personally if I write a patch like this I will at least credit the bug reporter with finding a fix. As you said, they did most of the work and deserve at least equal credit.

Man2Dev :idle:

@marcan I agree and giving some credit would set some incentive to give good bug reports

Go Up