A few things to note:
* come along to the meetings, come along to the Rails Camps (if you're planning to be in Australia in November, make sure you grab a ticket to the Rails Camp happening then when they're released - the upcoming June camp tickets disappeared in a matter of minutes). They're a great way to meet other people coding with Ruby, to learn from them, to share things with them. If there are Code Retreats and other such skill-focused events, they're extremely worthwhile as well. It may also lead to jobs.
* Write code - and if Ruby's the focus, then write Ruby code. Find a little itch that needs fixing, and write code to deal with it (unless it's an actual itch, then perhaps seeing a doctor is better). The more code you write, the more confident you'll be about your code, the easier it gets for contributing to open source projects.
* As you write code, you'll use other peoples' libraries, and thus get a better feeling for the styles of code you like - so read the code of those libraries. I use `bundle open [gem name]` *all* the time - it's often a better source of information for how gems work than their documentation. The more you navigate other peoples' code, the better you will be at doing so, and you'll learn a heap.
* Once you've got some knowledge of Ruby, and you come across things that are worth sharing, do so - especially by giving talks at the meetings. I blame/thank Tim Lucas for prodding me to speak at the very first Rails Camp - which was certainly a nervous experience. I'm far more comfortable these days because I've had a ton of practice - almost every time it gets a little easier.
* If Melbourne's where you're looking, and you have the working situation that allows for it, consider working from Inspire9 in particular (and coworking spaces in general). There's a few experienced and friendly Rubyists there - Ryan Bigg, Ivan Vanderbyl, Nathan Sampimon, Sam Richardson, the Culture Amp crew, myself - who are often happy to answer questions (though granted, I'm away from next week for four months). Also, there's some amazing Ruby teams in Melbourne as well, should you get the opportunity to work with them (Envato and The Conversation both quickly come to mind) - essentially, find smart people and if possible, work with them.
But the first three points I've listed are the key ones, I think: write code, read code, talk to coders.
Also: there's some very smart Rubyists in Montreal as well, so you've no excuses for starting on all three of those right now!
--
Pat