Summer Coding 2010 student application - Aditya Patawari

Draft!
This is a draft. I am still working on it. :)

About you

1. Name: Aditya Patawari
2. Email: adimania@fedoraproject.org, adimania@gmail.com
3. Wiki User Name: Adimania
4. IRC Nick: adimania
5. Primary Language: English
6. Location: India, +0530
7. Open Source Experience: I haven't been involved in any Open Source software development before. I have been a Fedora Ambassador for more than an year and have organized several workshops on Fedora and open source. I have also customized Fedora for better usability, including some packages which are not included in Fedora to encourage newbies to use Linux. I have organized several install fests in past and seen Fedora working on a lot of hardwares.

About your project

1. What is the name of your project?
2. Does your project come from an idea on the Summer Coding 2010 ideas page? If so, provide a link for reference, as well as a link to any discussions with mentors about your proposal.
3. Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
4. What is the timeline for development of your project? The Fedora Summer Coding work period is 11 weeks long, May 24 - August 9; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 5-12); the last steps always take longer than you think, and we will consider cancelling projects that are not mostly working by then.
   • If your project development progresses differently so there is not 90% functionality by the mid-term, you must be in regular contact with your mentor about this. Your mentor must not be surprised about the state of your project when the mid-term comes.
   • If you are not progressed this far in mid-term, you must have a plan with your mentor to fix the situation.
5. Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

You and the community

1. If your project is successfully completed, what will its impact be on the Fedora community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Fedora community, at least one of whom should be a Fedora Summer Coding mentor. Provide email contact information for non-Summer Coding mentors.
2. What will you do if you get stuck on your project and your mentor isn't around?
3. In addition to the required blogging minimum of twice per week, how do you propose to keep the community informed of your progress and any problems or questions you might have over the course of the project?

Miscellaneous

1. We want to make sure that you are prepared before the project starts
   • Can you set up an appropriate development environment?
   • Have you met your proposed mentor and members of the associated community?
2. What is your t-shirt size?
3. Describe a great learning experience you had as a child.
4. Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?

Note: you will post this application on the wiki in the category Category:Summer Coding 2010 applications. We encourage you to browse this category and comment on the talk page of other applications. Also, others' comments and your responses on the talk page of your own application are viewed favorably, and, while we don't like repetitive spam, we welcome honest questions and discussion of your project idea on the mailing list and/or IRC.

The NeL project has some good general recommendations for writing proposals. We encourage Summer Coding code to include tests.