Some thoughts about next GSoC

Kai Blin kai.blin at
Thu Nov 22 11:00:13 CST 2007

On Thursday 22 November 2007 17:44:09 Jesse Allen wrote:

> From my understanding, the SoC site specifically says that you do not
> have to work on a project that has to be completed in the allotted
> time. I think the idea is that google wants to encourage people that
> were already working on a project before to apply and to encourage
> people to continue working in the community after the session is
> complete. Now the mentoring organization could set their own
> requirements, based on difficulty and scope, but I would be concerned
> with making time a limiting factor.

I'm not saying that we stop people from working on their stuff afterwards, nor 
forcing them to e.g. implement the full dll if their project is "Start an 
implementation of dll x". I was talking about shrinking their proposal so 
they can actually manage to implement all the features they promise in their 
proposal in the proposed timeframe. I know that this was really hard for me.

> The best alternative to the quiz would be to have the student begin
> working on the project before the application. He can discuss it on
> the the mailing list and hopefully show some code. This would be a
> good way to judge coding skill and the project's scope. Now in order
> for this to work well, we would have to encourage people to get
> started early, which really hasn't happened before right?

Well, depends on how you want to do this. I think this is overly restrictive, 
unless you're just talking about a patch or two like Maarten proposed.

> I did write a weekly progress, but only to my mentor. Now if there was
> a website, then I could have submitted it there.

Yes, that's the idea. :)

> > According to the wiki page, we already require a post-mortem report on
> > the project, however I can't remember seeing much of those this year. We
> > should make sure those are written next time. We might think of a better
> > name for the report, post-mortem sounds like the project is dead after
> > the summer, we want people to keep working.
> Maybe I misunderstood that. I only submitted my final report to
> google/mentors.

In 2006, students were asked to send the reports to wine-devel, and there was 
some WWN coverage of the projects. That really made it really easy for people 
to follow.


Kai Blin
WorldForge developer
Wine developer
Samba team member
Will code for cotton.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : 

More information about the wine-devel mailing list