RTH (Requirements and Testing Hub) is an open-source test-management tool, which also has requirements-management and bug-tracking capabilities. The main project page of RTH is https://sourceforge.net/projects/rth/
RTH was initially developed by 2 guys who stopped further development in 2006. In 2007 my company was searching for a test-management-tool and I did the evaluation of RTH. Since we could not contact the developers we did take over the SourceForge project and provided the modifications we needed for our internal purpose to the community (my manager is quite open minded there and he allowed us to do so).
So actually we took over RTH 1.6.1 as it was (hardly any user docs, lots of bugs,…) and we created some releases until now (just have a look at the “news” section on the SourceForge homepage).
At the moment there is exactly 1 person working on RTH – me (and actually I’m no developer I’m a QA team lead). From time to time I can “borrow” some developers from our company to do some of the most important bug fixes (most important to our company) and after such fixes I create new release versions on SourceForge.
So you can see there is not much man-power available to RTH at the moment 😉 From time to time people contact me and tell me about improvements for RTH which I try to collect in the Bug / Enhancement tracker on SourceForge. I absolutely agree with you that there are many possibilities to improve RTH (user doc, test environments, reporting…) and there should be a appropriate road map but actually I cannot provide such road map since I do not know when I can borrow some developers the next time to do fixes / improvements and further more I have to explain the my manager why I want to improve / fix things.
And last but not least as I said I’m a QA team lead and I have lots of other responsibilities so actually I would estimate that only 1 – 5% of my working-time are spent with RTH related things (support in forum, issue tracking, planning,…), the rest of the time I invest for RTH is my spare time.