That is not an ideal situation. It is MUCH more preferable to have
some accountability here. And that means assigning *specific* mentors
to each student. And that means those mentors should register in the
webapp.
Cheers,
-g
On Sun, Apr 16, 2006 at 10:10:40PM -0500, Ben Collins-Sussman wrote:
> On 4/16/06, David Anderson <david.anderson@calixo.net> wrote:
> > Ah, and another quick point...
> >
> > * Ben Collins-Sussman <sussman@red-bean.com> [2006-04-15 18:53:57]:
> > > At the moment, SoC is busy registering open source projects and
> > > mentors interested in hosting students.
> >
> > How does this work within our project? Last year, mentoring was
> > fairly freeform, with the community and committers as a whole
> > providing mentoring. This worked very well for me, and I think we
> > should continue along those lines. However, is there something to do
> > this year to be officially "Mentor for the Subversion project" in the
> > eyes of the SoC program organizers?
>
> Most open source projects assign specific mentors to specific
> students. Our project just doesn't bother. Our whole community
> "mentors" our students, it's just how we work.
>
> So, if you look at the SoC webapp, only fitz and I are actually listed
> as 'mentors', but it doesn't really mean anything at all. There's no
> need to "sign up"... just mentor the students when they start posting
> to our list.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 17 08:48:53 2006