I was a mentor in the Julia track in the past. I just checked back in after a pretty long break, and noticed a buildup of mentoring requests, some up to 10 months old(!) I assume that as I stepped away and spent my time elsewhere, other mentors have as well (presumably all of them, because for a time at least I know there was a good handful).
The latest requests are only a week or so old, so it’s not dead from the student side. Can anything be done to revive mentoring on this track, and/or to handle the 10 month old requests? To be honest, if it were me, I’d be pretty annoyed to hear back 10 months after I posted an exercise
Exercism shows 7 Julia solutions mentored in the last month.
If you’re up for mentoring, you could always ping old solutions with a “Hey, sorry for the long delay. There were more students then mentors for a while. Do you still want a code review session here?”
“Reviving mentoring” is … hard. You can ask people to volunteer to mentor. You can find solutions in the mentoring queue that look great and encourage students to mentor others. But I don’t think there’s a ton more that can be done.
The overview says there are 31 queued requests with an average wait of 5 days, which isn’t too terrible. Some other tracks are much worse. Zig has over 100 solutions queued. Groovy and Prolog show an average wait time of ~1 month.
