Work WAS(Re: Reporting bugs and bisection

On Tue, 2008-15-04 at 06:55 +0200, Willy Tarreau wrote:

Stats such as those above, while useful, are flawed. IMO James Morris has (probably more than anybody else) hit on the core issue. To extend his view: theres more than just code review that deserves respect. Testing is one. Commenting, not necessarily on code, but on architecture is another. Documenting. Yes, running sparse or even Lindent or checkpatch. In the old/current Linux thinking (pun intended) work equates to churning code. That thought process derives from Linus actually then propagates down stream to other folks. I think the Linus approach is still excellent - but its definition of "work" is no longer valid. Work must include all these other things and visible credit is important if the revolution is to continue.

If you look at it from a software engineering or production resource
management, the Linux development model has gotta be one of the most
inefficient[1] - with a reward system geared to developers mostly.
If you want to look it from an investment of time (ROI perspective),
developers get way too much credit riding on everybody elses back.
Why should Mark Lord report another bug to us?
Put yourself in his shoes:
- he is a clever guy who has already worked around the bug. So a proper
fix is only a convinience for him.
- Blessed as he was - he got to do more and more work after reporting.
- he got slapped for claiming he had to go and get lunch and therefore
didnt have time to do more bisect for a bug that wasnt just unique to
his setup.
- he spent a gazillion electrons responding to people and justifying his
stance
- he got no credit for his time whatsoever when the bug was fixed (he
wont be showing up on lwn list).

I think perspective and credit for peoples time needs to change.

cheers, jamal

[1] With current momentum, theres an infinite resources of developers and testers and documenters in Linux, i.e resource management is only valid as a metric if you had finite resources. So the point i am making is moot - but I do strongly believe the momentum will dampen if current trend of defining work continues.