[Gluster-Maintainers] Reducing technical debt

[Vijay Bellur]

Hey All,

While trying to review an upstream patch, I noticed that a single function
has almost grown to 1k LOC :-). I found it unwieldy from a readability
perspective and problems of that nature could be a major deterrent for
anybody to contribute code in such areas. I am inclined to believe that
this is not a one-off and that we have areas in our modules where code
readability could be significantly improved.

Code readability is a form of technical debt and we have some more
technical debt already identified at [1].  While accruing technical debt is
easy and common, it also requires a dedicated effort to retire that. If you
are already following some best practices for your component to address
technical debt, please share them here for the benefit of everyone! :-).

I am also wondering if we could institute a process for addressing common
technical debt (test coverage, readability/refactor, long pending problems,
outstanding bugs etc.) release over release.
Appreciate your thoughts that can help in reducing debt and make it easier
for all of us to take the project further!

Thanks,
Vijay

[1] https://github.com/gluster/glusterfs/labels/FA%3A%20Technical%20Debt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20180521/06e7e3c4/attachment.html>