Martin Dougiamas

It's because of localhost. The hubs will always ignore localhost addresses because when it tries to communicate with the site it will always be talking to itself.

The link in the error mentions this. http://docs.moodle.org/en/error/local_hub/cannotregisternotavailablesite

This unfortunately makes testing on localhost impossible. A workaround would be to define some other hostname for your local site. On Unix and OS X you can edit /etc/hosts and define something like jon.local for yourself.

Basically, you need to get the hub plugin from

http://download.moodle.org/download.php/plugins/local/hub.zip

and then unzip it into the /local directory of a current Moodle 2.0 site so you end up with /local/hub. Once you visit the /admin page it should all install and you'll see new commands in the admin menu.

It's not recommended to do this on the same Moodle site as you use for courses. Do it on a fresh Moodle.

Yes, exactly. It's there, but you need to enable it.

It's going to stay in CVS and download packages for Moodle 2.0.

I think it's fine to add someone as a watcher if you are pretty sure they need to see it and you think an important issue is being forgotten. If I didn't think so then you wouldn't have access to do so.

Please don't let Tim's reaction stop you adding other people as watchers. However, if you abuse this then I'm sure the person involved will let you know.

Generally though, it should NOT be necessary to manually add anyone. There's a lot of default processes in place within the tracker to make sure things automatically get to the right person as long as your issue is categorised correctly, and it's best to just let that happen. Just remember we all have big backlogs.

(All I need is 20 more developers I can trust. )

Language editing will mostly be done on a dedicated site for Moodle 2.0, at http://lang.moodle.org. Nearly ready!