Generally I agree it could be good to have more easily accessible information on how to test on the website. However, just by playing the development builds one does not automatically help. We'd still need people to provide quality feedback on what is going wrong (or how everything is working fine, and what + where they tested). Sadly only few people are unable to provide such information in a way which allows for actually identifying underlying issues, fixing them, and getting feedback on whether they were fixed successfully. We could still try to get some information out of the game automatically, which is underway (Google breakpad), and when this will be implemented it could already help a great deal.
Nevertheless, I've just updated the development page on megaglest.org a little, i think it has a slightly more open touch now:
http://megaglest.org/development.htmlI assume the information you will find there now, much of which was already present there, will also answer your question about source code management ("Github").
If you have specific suggestions on how to improve the website (what should be changed where, use annotated screenshots, a mockup / wireframe site or something like pastehtml.com), I'll be happy to hear them.
