On kernel mailing list behavior
On kernel mailing list behavior
Posted Jul 19, 2013 20:12 UTC (Fri) by dlang (guest, #313)In reply to: On kernel mailing list behavior by daniel
Parent article: On kernel mailing list behavior
one person's "make-work" project is another persons "critical for long term maintainability" project.
It's _very_ common for people to some to an open-source project and hand over a bunch of code to be implemented.
It's almost unheard of for the same person to be involved a decade later to fix or clarify that same code.
As a result, the maintainers (many of who _have_ been around for a long time) are FAR more concerned about maintainability issues than new contributers.
Sometimes the maintainer will do the work to convert a contribution to be more maintainable, but as Ted notes, that doesn't scale. What the maintainer needs to do is to push back on the contributer to get them to improve the submission.
In most cases, the contributer does so, and their next contribution is better (requiring less change).
Sometimes, the maintainer will ask the contributer to fix something else that the contributer sees as related to the contribution. sometimes the contributer does so and the result is much better, sometimes the contributer doesn't do so and their change goes in anyway, and other times the contributer refuses and goes away, and their change doesn't go in. All of these are acceptable results
