Lately, several potential students have asked me various questions about GSOC 2012. Consequently, I told them I would find out and email the list. I have found that all their questions are already answered (except maybe one): http://google-melange.appspot.com/document/show/gsoc_program/google/gsoc2012/faqs That's a long FAQ, but the answers are in there. If you're a student with questions, please refer to that link first, then ask on this list of your questions aren't answered there.
The one question perhaps not answered by that FAQ is: "How do I prepare?" That depends, of course. Some students have told me they know almost nothing about Drizzle. In that case, you should begin to learn the basics of Drizzle by reading http://docs.drizzle.org. Other students who were more familiar with Drizzle seemed to want to prepare for programming. In that case, you should begin be reading parts of the Drizzle source code that are relevant to the projects you may work on. Students should also know that the first several weeks of the program are dedicated to getting up and running. So students do not have to be ready to start coding and submitting branches/patches from the first day. The student application period began this Monday, March 26, and ends April 6. As the FAQ notes, proposals are submitted at that website, not directly to Drizzle. There's a proposal template, as well as other info, at http://wiki.drizzle.org/GSOC_2012 Before submitting a proposal, it is helpful to discuss your ideas on this mailing list first because ultimately Drizzle decides which proposals it will accept. Or, Drizzle has a list of ideas: http://wiki.drizzle.org/GSOC_2012_Project_Ideas If you want to work on one of these ideas, you must still submit a proposal at http://google-melange.appspot.com/gsoc/events/google/gsoc2012 but your proposal will be made for one of these ideas. However, as the template says: "Don't just cut/paste from the ideas page; instead describe your research into the problem and your solution." Here's an example: two students both want to work on idea X. One student just says in their proposal, "Idea X looks fun. I'd like to do that." And the second student says, "I want to do idea X. I've looked into ... and I see that we need to do ..." and the proceeds to explain a little more how they see their self implementing idea X. Obviously, the second student is more likely to "get the job", so to speak, because they've actually looked into the idea that they're proposing to work on. -Daniel _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
