The downside is that an assigned mentor will not get as much work done during that time.
Hopefully getting the interruption onto the schedule would have the benefit of allowing everyone to plan for it and try to minimize its cost. And it might also encourage junior members to try and work through problems themselves first (because they have to save questions for scheduled question times), but also make them feel less like an imposition when they do seek advice.
- no flak
- no flamewars
- no jokes
- no off-topic stuff
If everybody sticks to those rules then it will work fantastic, if you don't guide that it will turn into a zoo and become huge distraction.
We use a plain old IRC server + clients for this, nothing fancy.
The etiquette thing is important, and varies team by team. Our team has several channels to ourselves with varying levels of formality, and company wide channels similarly (#techteam, title line: "No banter" vs. #companyname, title line: <insert latest in-joke>)
Not only does the group element allow anyone who's taking a quick break to offer some help, it often draws in advice from across the organisation, including people you'd never have thought of asking, who just happen to be dipping in to the channel at the time.
Edit: The office wide "banter" channel's primary purpose most days (so like, not Friday afternoon) is the distribution of fresh coffee, prepared in 5 mug cafetieres, announced and claimed here. So many people have IRC bings on the word "coffee" that it's best discussed in some form of leet substitution if you're not offering to make some.
I'm more than a little jaded at this point, and would love to hear if anyone has faced and solved these sorts of issues.