All, I've been reviewing the various resrouces offering guidance on how best to structure mentoring for GSoC projects.
Here, as a result, as my thoughts - for dicussion on today's code review call. I can't make the call today, but would be most grateful if the group could discuss and agree a structure. Please post to the list after the call if possible ? Thanks ! 1. Progress reporting - status reports from students once a fortnight. This should be brief & take the form of a simple update on tasks completed & any issues encountered. 2. Regular contact with students - I think we are already doing this via qpid-dev and should continue. Ideally, the bulk of the support given to the students will be from their mentors (for consistency/continuity). I'd like to speak with my student (Lahiru) once a week at an agreed time on the phone (due to local IRC constraints), and I'll try to make myself available one evening a week via IRC. Other mentors should consider when/how they are available ? 3. Resources - we can (only ?) give wiki access to a wiki not used to generate our website afaik. We can check, but from my asking around this, this seems the guideline. We don't have one of these that I know of so we can a) get one or b) do something else ? 4. Subversion - svn acces is out at the moment, so attachements to JIRA is prob the best way (or onto wiki if we get one). There's some debate about this just now, but no answer so doubt it'll fly for this time through. 5. Mentor co-ordination - so my understanding is that each student will have 2 or 3 mentors. We need these groups to discuss the proposal in detail (get a common understanding) and also to agree how best to share the load without confusing Lahiru & Rahul (and ourselves !). Thoughts ? Regards, Marnie
