I agree that given the way GSoC pays
students for meeting predefined goals, the issues you raise could cause
problems. It's my first GSoC experience so I'm not aware to what
extent they actually happen. <br>
<br>With the right number of students, involved mentors, and the fact
that the students' stipends are actually separate (what division?), I'm
not sure it's as impossible as you say. I've had similar experiences
working with interns at my company that worked out well - teaching
several people the same topic at once is usually more efficient than
teaching them all separately.<br>
<br>And given the level of overlapping interest in activity
development on the Ideas talk page and the mailing list, I think there
needs to be some kind of a plan to coordinate the work, so this was my
offering.<br>
<br>Best,<br><font color="#888888"><br>Wade</font><br><br><div class="gmail_quote">On Mon, Mar 24, 2008 at 3:12 PM, Austin Appel <<a href="mailto:scorche15@gmail.com">scorche15@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Wade Brainerd wrote:<br>
> What about treating several of the proposed activities as a one large<br>
> project? We would create a SoC "activity team" of 4-8 students and<br>
> 2-3 mentors, and then have these students develop several of the<br>
> activity ideas over the summer.<br>
<br>
</div>Google Summer of Code simply does not work like that. This is for many<br>
good reasons such as:<br>
<br>
Students being reliant on another student's work does not end well if<br>
something happens to the other student.<br>
Issues always arise about Xxxxx Xxxxx not doing "their fair share" or<br>
one superstar student doing almost everything.<br>
Delays while waiting for collaborators.<br>
Dividing up money fairly.<br>
<br>
This really isn't an option at all, as it is against Google's whole<br>
vision of GSoC and how it should work.<br>
</blockquote></div><br>