"Publish this service to allow your users to roam to the {XXXX} Moodle site without having to re-login there."

where {XXXX} is replaced with the name of the remote server (see Server Administration > Networking > Peers > Services). Such strings appear also when setting up partnership with a Mahara site. So they become rather confusing.

The problem is easy to reproduce:
===========================
set-up networking between your Moodle server and a Mahara site. You will see that from "Moodle Networking" is not appropriate term any more.

BTW IMHO "MNET" have the same information value as "Moodle networking" - admins have to read what the system is about to understand the concept. Also, Mnet sounds pretty IT-ish for me

Thanks for paying attention to this.

While it's called "Moodle Networks", there are definitely other systems that can speak it - and that goes beyond Mahara too. Catalyst wrote an MNET library that allows projects like drupal to speak MNET for example.

To be honest, I don't mind what it's called in Moodle's documentation - and as the other responders seem to think, 'Moodle networks' is unambiguous so it's a good choice. But I definitely think there's a usability issue in the actual UI. Constantly using the word 'Moodle' like it's the only thing that can be connected to is confusing for people, when it's hard enough to set up networks!

And as for the protocol itself - well the developers have long called it the 'mnet protocol' - although it's not really officially specced or anything.

I guess what I'm suggesting is:

• Call it 'Moodle networks' in documentation
• Call the protocol the 'MNET protocol' (only for coders)
• Change 'Moodle' specific wording in the UI. Mahara uses 'remote application' by the way.

ps: I think I already filed a bug about use of 'moodle' in the moodle UI for mnet some time ago, it's probably floating around the tracker somewhere.
pps: I think also the UI says 'moodle' a lot because you could only network between moodles in 1.8, the Mahara ability was added in 1.9. So any patches for this probably make sense from 1.9 up.

"the best way to solve a problem is to attack the cause of it" or, in Spanish, "muerto el perro, se acabó la rabia"

Alternatively I'd vote +0.5 to rename it to "Microsoft Network"

Obviously joking :-D

I think "mnet" is a good name, easy to remember for everybody, the "M" points to Moodle (where the protocol was first implemented), and the "NET" part is pretty meaningful.

So +1 to change any occurrence from "Moodle Network/ed/ing" to, simply, "Mnet" (but the main page in Docs, where the link between both names should remain/be explained.

Ciao