On Sat, Apr 13, 2013 at 9:24 PM, Christophe Rhodes <csr21@...> wrote:
> Vsevolod Dyomkin <vseloved@...> writes:
> > On Sat, Apr 13, 2013 at 5:12 PM, Nikodemus Siivola <
> > nikodemus@...> wrote:
> >> I apologize for being a Negative Nelson here...
> >> > I'd like to participate in GSoC as a mentor. The projects I'm
> >> > particularly
> >> > interested in are:
> >> I'm not directly involved in our GSoC, so take this with a ton of salt
> >> ... but I do believe mentors should be SBCL hackers -- enough so to be
> >> able to advice the students on technical issues specific to the
> >> project at the very least. (I don't know what the actual rule is,
> >> that's just what I would consider a reasonable minimum.)
> > I see your point and have to agree. That's why I was asking.
> Well. There's unblocking technical issues, and there's also routine
> project management (e.g. making sure that the student actually knows
> where to look, is working, can write reports, knows where the git
> repository is this week, and so on). SBCL hackery is probably required
> for the former, and if we get enough SBCL hackers (not necessarily
> commiters, people with experience) as mentors then great. But we might
> not, and in that case I'd rather have team mentorship from someone
> willing to do project management and someone to be a technical
> consultant sharing the load, than have no-one at all.
> Whether that's contortable into the GSoC way of thinking I don't know.
> (But it is at least suggestive that UK PhD supervision is very much
> going this way: people have several supervisors, one of whom is
> responsible for the paperwork, and need not necessarily have any direct
> academic input.)
As for me, I'm willing to participate, so if you there's a need I can
volunteer to help.
I also view it as a chance to get more involved in SBCL development.