On 4/2/11 3:03 PM, Christian Manning wrote:
Hello all,
This is my first draft proposal for a Database API for Google Summer Of
Code. I have never written a document such as this so any and all
feedback is welcome.
Thanks
[snip]
Thanks for your interest and for sharing your draft proposal.
Fawzi is doing an excellent job at making suggestions for improving the
proposal. Let me add some.
Generally you need to create a compelling case that you know what your
project entails, you have thoroughly studied the state of the art, and
you are able to take the project to completion. Digital Mars' reputation
is at stake here - we need to make sure that we're using Google's money
and everybody's time to good end.
Here are some more additions to the proposal that would improve it:
* What is your level of understanding of D? How do you believe you could
use D's templates for improving the API compared to JDBC? If you choose
to copy JDBC's interface, how do you justify relying on dynamic typing
alone?
* What coursework did you complete? As a second-year student this makes
it easier for us to assess where you are in terms of expertise. Scores
would help as well.
* Since you now know of existing work, have you contacted Piotr for
collaboration? Would he give you his API to work on? Would he be
available to help as a formal mentor or informally? What is the
integration plan?
* If there project were totally successful, what features do you expect
it has and what would be the impact?
* What is the absolute minimum level of functionality that would still
qualify the project as successful?
* Also include Fawzi's suggestions focused on details of API definition.
Thanks,
Andrei
