Not sure what Gijs or Hyde are thinking here - but originally this was about the MapStructure side of things, which is the back-end used by the ND code (well by parts of it) - so far, most ND issues have been reported via the issue tracker or the wiki (see the wiki article) - so I would suggest to keep it that way. The MapStructure layer itself is not specific to the ND.
Feel free to make feature requests via:
http://wiki.flightgear.org/Canvas_ND_FrameworkFinally, let me say one thing very clearly: It is great that so many people are contributing to this by testing things and reporting bugs and making feature requests, but PLEASE don't think that this is all you can do - adding a new feature or fixing a bug will now typically require 5-20 lines of Nasal code, and there's very little that you can break. So if you have previously done ANY kind of scripting/programming, you will find this extremely straightforward to do, and I would suggest to get in touch with Gijs and Hyde to help with things. Some of you seem to have access to the corresponding AOMs (manuals), so we really only need to document how to add new feaures, to enable others to help maintain the whole thing - which really is the only sane way to deal with the amount of feedback we've been getting. Please do not expect Gijs to shoulder all this on his own - instead, get in touch so that we can tell you how to implement new features, and help fixing bugs.
It should really only take us 30-45 minutes to document the current process, so that things become better scalable, because we could have more people working on this, not just Gijs ...
If you are able to run, test the ND and identify bugs, then you are also able to help fix them - simple as that, this really isn't rocket science anylonger.
Typically, it will only involve 5-10 different "commands" (Nasal functions like setprop/getprop) and ~20 lines of code, most of it being purely declarative.
just my 2c obviously ...