Previously I had setup system issue tracking at JavaForge. However, JavaForge is a bit more complex than our needs. So I've setup the issue tracking on GitHub. This gives the added benefit of being integrated with our source code updates. So issues can be tied to commits.
I will be transitioning the open issues from JavaForge to Github soon.
Anyone can submit an issue. However, any submitted issues will be reviewed and managed. In addition, because GitHub makes it easy to Fork and make changes, anyone can work on a bug in their own forked repository and submit the code fix. This is the whole intention of moving to GitHub. Make it easier for the community and any developer to contribute to the code base.
On another note, I have published the various demo world code, for both server and client, to GitHub as well. This includes; the Common assets and code, the Fantasy world, and the NYTS world files. The intention for this is to provide an easy way for people to contribute to these common worlds.
These community driven demo worlds would then be setup on the Foundation VPS for showcasing.
Let me know if you have any questions. While I can't necessarily teach you on how to use a source control system I can help out in some ways.