I don't think LOC is a good measure for that, too many variables that change the effort required for same-length pieces of code: How complex is the code? How much does it change?
And when comparing between people, what does "maintain" entail?
And when comparing between people, what does "maintain" entail?
I figured maintain to cover having originally written it and are charged with its ongoing use.
And maybe normalize for each by the lines of code for each component and some constant factor after twiddling.
Basically LoC by itself is meaningless. When you gauge responsibility you want to look at how many features are owned, how complex those features are (unit tests) and how critical those features are to the system/product (integration tests). With complexity/criticality being weighted much higher than feature count.
Of course like all metrics this is easy to game. But that's what code review is for.