Changes

:Scope: A UI abstraction framework is too much work: for something that we aren't even sure we need. And I won't be able to do it in 3 months single handedly. So I could start paving way for what could eventually become a framework, but still manage to do something useful for the community in these 3 months. Lets take the feature of discoverability of keyboard shortcuts and context menus. I could start working on bringing this feature into Sugar. But do younger children need keyboard shortcuts? Can the clues for enhancing discoverability of such features lead to confusion for those who dont need it? So depending upon the age of the child using the system (obtained from user profile), the system could choose to expose certain clues or not. I will limit my target groups to two. What age ranges form the groups - needs to be explored (6-10 and 11-15 ?). I think this can be done in 3 months.

:Scope: A UI abstraction framework is too much work: for something that we aren't even sure we need. And I won't be able to do it in 3 months single handedly. So I could start paving way for what could eventually become a framework, but still manage to do something useful for the community in these 3 months. Lets take the feature of discoverability of keyboard shortcuts and context menus. I could start working on bringing this feature into Sugar. But do younger children need keyboard shortcuts? Can the clues for enhancing discoverability of such features lead to confusion for those who dont need it? So depending upon the age of the child using the system (obtained from user profile), the system could choose to expose certain clues or not. I will limit my target groups to two. What age ranges form the groups - needs to be explored (6-10 and 11-15 ?). I think this can be done in 3 months.

; What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; 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 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.

; What is the timeline for development of your project?  

:This work will be part of my Master's thesis. I would hence be working on the project for the next 1.5 years. I will detail my plan for the 3 month GSoC period and beyond that.

<!--The Summer of Code work period is 7 weeks long, May 23 - August 10; 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 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.-->

:This work will be part of my Master's thesis. I would hence be working on the project for the next 1.5 years.

*May 1 - May 23:  

*May 1 - May 23:  

** Get to know the code base and the persons behind.  

** Get to know the code base and the persons behind.  

*Week 12: Finish work, core review and commit.

*Week 12: Finish work, core review and commit.

*Week 13: Document work. Blog. Put up a presentation summarizing my work and experience so far.

*Week 13: Document work. Blog. Put up a presentation summarizing my work and experience so far.

*Sign-off

*Sign-off GSoC

   

   

; Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described.

; Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described.

====You and the community====

====You and the community====

; If your project is successfully completed, what will its impact be on the Sugar Labs 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 Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

; If your project is successfully completed, what will its impact be on the Sugar Labs 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 Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.-->

; Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?

:OLPC/Sugar is based on the principles of Constructionism. Discoverability and learnability of the system with minimal/no external help hence becomes a very important factor. My work will pave way for a framework for improving the discoverability of the features of the system in a customized manner depending upon the individual using the system. I am going to bank upon only one factor: age. But once the framework is mature (couple of years from now), I can imagine various plugins that take into account other differences: culture, previous experience with technology, physical disabilities - to name a few. This will immensely improve the system's reach and usability among the millions of children using it.

I will be travelling between Canada and India. I am interested in observing how children with radically different levels of exposure to technology react to Sugar. I would like a primary deployment center at Vancouver. But I would also like to visit a center at India when I make a visit (once a year).

; <!--Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed.--> Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?

I will be travelling between Canada and India. I am interested in observing how children with radically different levels of exposure to technology react to Sugar. I would like a primary deployment center at Vancouver. But I would also like to visit a center at India when I make a visit (once a year) and observe how differently the children who haven minimal exposure to technology react to the design of Sugar UI.

; What will you do if you get stuck on your project and your mentor isn't around?

; What will you do if you get stuck on your project and your mentor isn't around?

Use the alternate contacts obtained from mentor beforehand. Fall back on community: IRC and then if still the problem exists after 12h contact mailing list. If nothing works and if it seems like I am slipping schedule, contact GSoC person Tim McNamara.

Use the alternate contacts obtained from mentor beforehand. Fall back on community: IRC and then if still the problem exists after 12h contact mailing list. If nothing works and if it seems like I am slipping schedule, contact GSoC person Tim McNamara.