Jerry James writes:
On Mon, Mar 25, 2013 at 11:34 AM, Stephen J. Turnbull
> Let me know if you're willing to help as soon as possible!
I don't think I have sufficient free time to be a mentor, but I'm
willing to be a backup mentor.
What are these "light duties" of the organization
The org admin is responsible for
1. Applying to Google by Friday. I'll do that, it's easy enough to
change the nominal admin later, I believe, especially if the point
is to avoid somebody doing both admin and mentor simultaneously.
2. "Quickly" reviewing evaluations of students for fairness at midterm
(July 29--August 2, nominally, but we should have a good idea of
where things are going by mid-July) and summer end (September
23--27, same kind of caveat). Mentors and students don't see each
others' evaluations (unless mentor == org admin -- I think you see
why I don't want to do both mentor and org admin!), so this is the
only way to get an idea of whether the mentor and the student are
one the same page, and that's really all you need to do. It's an
essential job, but each evaluation is less than one 24x80 screen's
worth, usually quite a bit less I think.
3. First level arbitration of disputes between mentor and student
about evaluations. (Final arbitration is done by Google staff.) I
had a bad student last year in Mailman; he complained about the
schedule (there's a bad conflict with German universities, at
least), but didn't complain about the evaluation. I hear one case
went to arbitration last summer, but I think it's very rare, even
when real jerks are involved on one side or the other.
4. Tracking down (and replacing, if necessary) mentors who go AWOL.
This shouldn't happen, of course.
5. Kicking mentors to track down students who go AWOL. This does
happen, but the first line of responsibility is the mentor, not the
6. Submitting final organization evaluation (not sure of the content
of this, but it's not huge) September 23--27. Probably I can write
that, but maybe it requires access to student evaluations, in which
case I'd rather not if I'm a mentor.
7. Point of contact for GSoC staff.
8. (Optional) Mentor Summit-and-Pool-Party at Google Mountain View in
Org admin for large umbrella organizations (Python Software
Foundation, Apache Foundation) is a pretty big (and political ;-)
deal, I gather, but for one-project orgs like XEmacs, with no need to
allocate slots across multiple somewhat independent subprojects, it's
not much effort, even in evaluation periods.
XEmacs-Beta mailing list