Siddarth, I hope you do not mind, I am forwarding this back into the list. Sharing the question there will answer it for the community as a whole...
On Sun, Mar 21, 2010 at 10:16 AM, Siddharth Prakash Singh <[email protected]> wrote: > Hi Mark. > Thanks a lot for your suggestions. > Do you mean, I should just submit the proposal in the gsoc website and then > wait for review? I thought of discussing the idea with the mentor so that I > can prove better about my enthusiasm and ability to complete the project. > As you said, I will write a nice proposal and submit it in the SoC website > and then wait for the review. > I have also joined the soc list. > Regards > Siddharth > I would focus most on producing the application. There will be an opportunity for communication between the mentors and prospective students within the application during the review period. To be fair to the whole applicant pool, at this point in the process, mentors such as myself should be focused on giving you feedback on what makes a good application to DuraSpace GSoC so you can improve your chances of success. You may certainly ask technical questions in the email lists to solicit answers that will assist you in expanding your application. But bare in mind that they are publicly readable by other applicants as well. I'd recommend being conservative about conveying too much of your application and instead use the communication to get community feedback on very specific details that will assist you in building a solid application. For instance, in your case, a question for the community might be: "What are the javascript frameworks currently used in DSpace or that are recommended by the DSpace community?" Suffice it to say, that while conveying your technical ability as a software engineer is critical in the application process, it is but one facet we are considering in the application process. Also of importance are the following abilities: 1.) Engage: The ability to engage with the community and use feedback from the community to assist you in building requirements and solving technical problems. This includes being able to adapt your project to meet the requirements that are conveyed by the community. 2.) Communicate: Sadly, though Google translate seems to be getting pretty close, "Star Trek Universal Translators" do not yet exist. In this global age, the ability to communicate ideas clearly in the language of the group and mentor you are working with very important for the success of your GSoC project. 3.) Dedicate: For the student GSoC should be considered a paid summer long project that will require your to be working on it diligently. We want to see that you will be an active participant in the community during the project timeframe. Including any past examples that reflect your ability to do this in your application will increase its favor in comparison to other projects. See the FAQ for details: http://code.google.com/opensource/gsoc/2008/faqs.html#0.1_student_time Cheers, Mark -- Mark R. Diggory Head of U.S. Operations - @mire http://www.atmire.com - Institutional Repository Solutions http://www.togather.eu - Before getting together, get t...@ther ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
