And of course, as a more experienced dev, really all I need is some kind of human touch so I know that if I start working my efforts won't fall into a big black void... devs tend to call that hand-holding because most devs think all socializing is a waste of time, but for most people volunteering is at least a little social.
As far as actionable advice goes, I think having virtual "volunteer days" (on the 1st Saturday of the month, beginners can join the channel and get matched with somebody more experienced if they have questions for their first pull request) may work. Also appealing is publishing "openings" showing an example of what skills developers in your project commonly tend to have (working independently, obsessive about coding standards, super-problem-solver, an eye for usability, great communication skills, ability to use valgrind, whatever) so people can self-select into it.
I do try to put in community outreach time as it scratches a different itch than the more development focused day-job, however it does frequently seem to not lead too far. There are many cases where people interested in contributing are very junior individuals who need some assisting along the way due more to a lack of experience rather than lack of familiarity with the project in question. Linux audio in particular is challenging since it involves the intersection of several different domains (low-latency programming, DSP, C/C++, user interface coding/design, audio/speech processing backgrounds, technical writing, etc). So, people do end up being more green than I would expect compared to other open source domains.
Thanks for the specific suggestions. I've considered doing a specific hack day/weekend/etc event for a while, though I've never acted upon it since I don't really want to deal with the possibility that I end up spending a day or more and there is no activity in response.
I do like the idea of openings though. It's a clever way of presenting what the project has to offer as well as presenting specific enough profiles of people that it might get someone over the initial hump of "perhaps I should ask about contributing".
As someone who is interested in growing a medium sized open source project, it's difficult to find the people who are interested in contributing without feeling too pushy. You want to give people the best information and tools to go forward, but you also want to let them learn independently (since scratching your itch is typically an adage within FOSS).
I do push the "just pop into the IRC channel" approach because it's hard to give better recommendations before knowing who the other individual is and what they want to get out of volunteering. I don't know if any particular thread could accomplish the negotiation of "who want's to help whom" due to the vast differences of all the different specializations, project sizes, project collaboration styles, etc. It would be nice if it did though.