> Hi developers,
> I'm interested in the Google summer of code program and the ideas you
> proposed. And I would like to learn more about it. The soc page suggests
> that I can find the answers here.
> I've scanned through the list of ideas and found them are generally moderate
> in workload and should be quite suitable for a soc subject. I mean, I think
> I will be able to handle one of which within my summer vacation. So I would
> like to have a try.
Welcome, and thanks for your interest!
> Now, here come my questions:
> First, how can I apply for your proposal as a student?
> Should I apply to Google or to you subversion developers?
> Am I supposed to prepare some formal material to qualify myself, such as a
> detailed design proposal?
The answers to these questions are in the SoC FAQ:
> Perhaps I should introduce myself a bit. I'm a graduate student of
> University of Science & Technology of China, majored in computer science.
> I've gained some coding & debugging experiences during my campus days. I use
> subversion to manage my projects. That's why I will be interested in your
> I've gone through the materials you provided, such as those for the first
> idea -- deselection interface for sparse directories, got the idea of the
> proposal of "sparse directories" and the task that need to be worked out.
> Although I don't think it is hard to implement, I currently still have no
> idea of the detailed solution, since I'm just a user NOW, not a developer
Not a problem. Most of us started out as users before developers.
> Yes, I'm reading the 'Hackers Guide to Subversion'. And it would take me a
> couple of days to understand the underlying mechanism of subversion. Will I
> be adequate to apply for your proposal?
I think your proposal should just convince us why you'd do a good job on the
selected project, not necessarily how you'll go about doing it. Last
year, when I
was a student, we spent the "bonding time" of April and May working on the
design for my selected task, and it ended up working out pretty well.
HACKING is a great start in the process, though.
I can't speak for everybody, but when evaluating proposals, I look as
potential as I do at the past history. We just want to see why you want
the project, and why you'd be the best qualified to do so.
Do you have specific questions about a particular task (either the sparse
directories interface, or something else)?
Received on 2008-03-22 15:03:00 CET