[jamescostian]

I fully agree that it sounds awful for a project to go down due to politics. But only paying attention to code reviews ignores how the community feels, as well as non-code work. For example, look at Rod Vagg's contributions to node: https://github.com/nodejs/node/commits?author=rvagg

At least from the first page, it seems he's mostly working on documentation, specifically changelogs. But honestly, those changelogs are fantastic and definitely make a difference in my life (I don't want to comb through tons of commits to figure out what has changed between versions of Node). It might not be code per se, but the contribution is noticeable.

Even if all you do is make people feel welcome in a community or bring people in, those are still worthwhile (new people can mean more code). And if you're an amazing programmer but make everyone want to leave the project, one can see how that would also affect the code (contributors leaving).

[nogbit]

Usually, one who writes change logs is part of leadership deciding what should be worked on next, strategy, prioritizing and often times accountability as well. This is because they have a birds eye view of everything that is being worked on. Not easy and often thankless.