Okay, here's my take...
On 5/5/06, ted@...11... <ted@...11...> wrote:
Okay, I'm going to top post :)
I like the idea of doing research and writing things up on the UI. But, I think that Google is probably more interested in code...
I do understand that it's called the "Summer of _Code_", but I've looked over the terms, and they define the scope of the project in only two places : 'The Summer of Code is a program in which Google provides student developers with a stipend to create new open source programs or to help currently established projects.' AND 'The goals of the Summer of Code program are to create new developers, support existing open source projects and developers, and to provide students in Computer Science and related fields the opportunity to do work related to their academic pursuits during the summer.'
I understand your point of view, and I agree that they most certainly expect code, but I don't know anyone that would define a 'developer' (the term they use) as a code-producer only (or even, mainly)
On 5/5/06, Ralf Stephan <ralf@...748...> wrote:
I have read through some SoC documents and i would say what is missing is between your Part 2 and 3: a list of things you want to write, and the respective date when you think to be finished.
Without this, you have exactly zero chances, as far as I understand.
That can be included in the proposal. Of course it won't be 'I'll implement this specific function here at this point' but rather 'the work will focus on rewriting unit X, and implementing new interfaces for menus A and B, the extension of which will depend of the first and second part results'.
I understand both points are highly debatable and may hold Google off, but from my (limited) knowledge of the process, I didn't understand that they were that involved in the selection process. Does that type of proposal (admittedly vague, but with strong and precise checkpoints and deliverable reports) would hold SoC deciders for Inkscape off too ?
Tim