What you should be aware, though, is that the team thoroughly encourages taking time out for real life, putting real life first, and one of the many things I've been party to in the past is the simple fact that: if you don't have time to help out under a team position, you probably should hand that badge in. That way there's no false expectations, no misunderstandings and so on. There are more than a few people I have previously pointed in that direction, too - if you're so busy you can't commit a reasonable amount of time to the responsibility you've taken, you probably should stop. Life's hectic, it gets on top of us, and even if I hadn't quit last year due to the frustration of people not doing their fair share, I would have quit shortly after due to personal circumstances changing.
There is a point here, amid the frustrations on both sides, though, specifically relating to the fact that there are too precious few people that help out with the skills to fix some of the problems that come along. Yes, there will always be the general level problems, and I think I can speak for the team in recognising and thanking those that contribute their time in fixing those problems, under the sorts of categories of 'where's option x' or 'how do I...'
What ACAMS is getting at is that for anything more advanced than that, there is a real shortage of people with the technical skills, the time, energy etc to sit and get involved in helping people. I'm doing that mostly to assess whether things are bugs or not.
