I can offer an opinion based on what other area teams have labeled us. They have labeled us a mentoring team. I think the reason that they have labeled us as such is because we respond (to the best of our ability) to requests for help, assistance, sharing of knowledge, and hands-on training. That can be formal or informal. It can involve one person or several persons. It can take one brief session, several hours, or more. It can be local or it can involve travel. It can be a phone call, an e-mail exchange, a workshop, a training session, or a one-on-one meeting to help problem-solve or brainstorm. I think of us as a go-to team for any type of help that we can provide or offer, even though we have just sort of evolved into that role. A lot of it is done quietly and there have been a lot of times that we don't all know what all we are doing. I have been making requests for all of us to better document our work but none of us seem to follow through very well with that request.
To add, the mentoring involved can be in the technical and non-technical aspects of building a team and/or a community.
I guess that is my roundabout way of suggesting that your team take the time to document your work with others. By documenting your work, you are better able to determine what you are doing. And, as has been suggested - contact the teams that you have helped and ask for their input regarding the mentoring side of things.
This is a good topic.
Jane
Additional thinking: Several of the teams that we have mentored through the years have become, or, they are in process of becoming, mentoring teams, themselves. It's a process of paying it forward and it is a very rewarding process. It's also fun to work together towards mutual goals such as off-seasons, group demos, and with developing training initiatives and camps.