KaKaRoTo raises very valid points; maintainable code is extremely important, especially for a project in which we're still learning about the hardware. That said, lots of people on these projects are reverse-engineering geniuses and can probably continue Hermes' work, but it tends to alienate other programmers, whereas a well-maintained repository is very welcoming.
But if KaKaRoTo is correct that Hermes is just sticking code in arbitrary locations, I will have to avoid it for now. Sure, it may have a low chance of causing problems, but that sort of behaviour becomes difficult to deal with as the code expands if it's not addressed soon.
I've also really appreciated KaKaRoTo's technical explanations because it really helps support his concerns and they're not so detailed that it excludes anyone that's not part of this scene.