That would be great! I'm busy with the m-firmware.
(please don't take this personal)
This general attitude is absolutely the norm among software & EE. Most people refuse to even spend 1min on documentation for every 100min hacking. GitHub is littered with projects that smart people spend combined lifetimes on that'll never be seen or be of use to anybody because they could not be bothered to spend 5min on adding a screenshot and a paragraph of text on 'how to build & install'. How may times have you seen some README on GitHub where you literally can't even figure out what this is supposed to do because just writing ONE SENTENCE on what this is was asking for to much.
If you Google for 'transistor tester m-firmware' I don't find your canonical repository. And how would I even know to search for that if I didn't dig through a giant forum thread telling me that's the current branch of code for this project (I guess it is?). Looking at the janky SVN browser (for most people it's anyway 'if its not on GitHub it might as well not exist') and trying to click on the PDF docs all I get is 'Display of files larger than 512 KB disallowed by configuration'. I guess I need to install SVN.
I just see this kind of stuff over, and over again. It's the engineer's disease. Brilliant people dedicate thousands of hours of their time to build truly impressive and useful things, only to stop two steps in front of the finishing line. All it would take is brief, simple page on GitHub or a community wiki with a few words on what is the state of this project, where to get the current docs/code/schematics, a paragraph or two for the 'Buyers FAQ', done. It's like you spend a year of your life building me this beautyful car, but when I ask you for the keys all I get is a shrug and 'read through this forum thread, somewhere in there is a link to a gopher server containing a Rot13 encoded text file with the coordinates of where I buried it in your backyard. Good luck, I need to build another car'.