I was wondering if there is one in the near future?
I bring this up every 6 months or so but no luck yet.
I think not enough people would go.
That’s shame! I believe that there are a lot of MT custumers in OZ and our geographical location is not bad. If There is MUM in Australia, I think it would attract heaps of MT custumers from neighbouring countries as well. Considering the fact that there is a great deal of foreign tourists travelling to Australia in recent years. This would give them an excuse to travel too 
look at this topic for example. you two are the only ones showing interest 
Normis,
I really want to attend MUM as well as trainning, But if it is near to India coz, it is very difficult to get the VISA outside asian country…
Any Planning for INDIA. Our Company is ready to organize each and every things for you
How about going to Egypt? Is it hard to go to Egypt MUM from India?
btw: Charm El Sheik is in Asia 
If Australia isn’t big/important enough for Mikrotik to grace it with its presence what chance do we Kiwis have?
Not that I’d go even if they held a MUM in Auckland - awful place! And how many Kiwi’s can afford to visit Queenstown these days?
Personally I’d settle for good, up-to-date documentation and comprehensive ‘How-To’s’ over any number of MUMs - battling jet-lag and Montezuma’s revenge while trying to follow a complex one-time presentation on advanced routing or the subleties of bandwidth management isn’t the way I’d choose to learn my trade.
What do you think about Bali. Isn’t it easy for Australians and Kiwis to get there?
Depends who’s paying for the trip.
If, as may be, you lived in the States and your wife came home one day with a brand-new Fisher & Paykel washing-machine with a control panel like something out of a USAF fighter cockpit, and the news that the only way to learn how to use it was to attend a training course in New Zealand would you say happily, “Sure, here you are Honey,” and hand over the air-fare and four day’s accommodation?
I’ve nothing against MUM’s - I’m sure they’re very useful and informative, and great fun when the costs are coming out of your company’s budget (and hence ultimately your customer’s pockets). But I would argue that, as seems to be the case, they should not stand in substitution for widely-available, comprehensive, up-to-date information about the product one is trying to use for one’s business!
I’d go to Bali
Bali? uhmmm… don’t get me wrong. I like the attractions but after the bombing, I am a bit …chiken out
i just wanted to point out, that MT is not substituting manual with MUM - these are completely different things. While in manual you can read how to use on or another feature in MUM you can actually see how people are using those features together in a real environment, what challenges they have overcome and what knowledge had acquired while doing that.
Where in the MT manual do I find out about ‘blink’, which has appeared in the RouterOS 3.0rc menu? Or about ‘calea’, whatever that is that demands a package to itself? I discovered quite by accident that there is a console command for ‘Pick’ which doesn’t get a mention in the manual and had to work out for myself the syntax for it. How many other commands I would find very useful are not mentioned in the manual, and therefore not available to me? Currently I’ve having to spend hours almost reverse-engineering User-Manager in order to find out how to make it work for me because all MT has put out on it is little more than a ‘Quick start guide.’
Mikrotik gear was recommended to us for our network when I knew nothing about what was available and I’ve no problem with the gear - it’s first-rate stuff that has performed exceptionally well - but a great deal of what I’ve learned, and had to do to set it up and get it to work has come from the on-line manuals, how-tos and support information put up by Cisco, Linksys, Netgear etc because Mikrotik tech. staff are too busy preparing power-point presentations for and swanning off to MUMs in exotic places to post this kind of thing for (no-doubt the many) Mikrotik users who don’t have the time and/or resources to hob-nob with them there and be inducted into RouterOS’s little secrets.
Not quite fair IMHO -
3.0RC is not yet in “release” status: one has to accept that status - caveat emptor - and just like previously with 2.9, there was no real online documentation until release version was out. Quite right: MT should put the effort into making the code stable, rather than writing manuals for non-release software versions.
Also, MT business model depends on user-input into support forums like this to solve user questions/problems and user-input Wiki to create more complete documentation and “how -to’s”. Nothing wrong with that - there are some real experts online here.
Also note some MT OEMS (bang drum, including us often create their own detailed documentation “how-to’s” for key tasks in PDF and also a wide range of pre-programmed config scripts to return/setup products to known states - makes sense for our business to do so.
I’d say a combination of wiki (go on, share your knowledge, you know you want to) and OEM’s writing helpful documentation for their solutions is the essential ingredient here.
Comments welcome -
Regards
Yes, you’re right. But the only reason I’m even trying 3.0RC is because a bug in 2.9 means I can’t use that, and another bug in 3.0 means I can’t use that either - if they are bugs and not
‘undocumented features’.
Yes, and I’m very grateful to them for the time and tolerance they are prepared to give non-professionals like me. But I would suggest forums are places for experts to get together to discuss the arcane and the esoteric, and to work out ways to boldly go where the developers never intended their software to venture. Many (most?) of the threads on this forum are from folk appealing with help re fundamentals which IMHO should be available in the manual/documentation.
There are also dangers in relying on third-party advice from strangers. Even discounting the mischievious or downright malicious, well-meaning but wrong advice gained from a forum could be disastrous.
Exactly my point. Surely you should only have to do such things where you’re adapting the software for non-standard applications. If you’re having to do it for ‘key’ tasks you’re doing MT’s job for it, acting and unpaid.
Everything you say is true, but I’m arguing that the principle onus for describing the functionality and implementation of their product is with MT, with user input the cream on the bun. By shifting the onus as you suggest you’re giving MT a free ride.
I’m only beating my own drum about this because I think its supporting documentation is by far the weakest aspect of MT’s offering and if they could get that right it would be unbeatable. And to the extent (if at all) that MUM’s contribute to that weakness (and MT’s ‘we’ve built a better mousetrap’ approach) I deplore them.
IMHO
For the price we pay for this software I don’t mind having to do a bit of reasearch with others, infact it make me sharper.
As for a bug in 2.9 that stop someone using it, MT will fix that, just not add more features
If you really write something that is not in the manual and not in the wiki already and post it in wiki - you get the license for it, if article is really good even lvl 6 license is for grabs
edit:
but that is not the point - we are working on the manual for 3.0 and this is not yet available publicly, because 3.0 is not released yet.
Talking about fundamentals - have you ever read “TCP/IP basics” book from covet-to-cover all 700 pages??? (and believe me in every 30 pages of that book there are at least some very usefull information)
All those are fundamentals. and it is only for one protocol.
Now let us imagine the size of fundamental manual off all the features???
routers are not for computer beginners. you should remember that users of routers are educated computer network administrators.