Changes

:I have not contributed code directly so far. My contributions have been limited to a number of bug reports and ideas spread across several projects.

:I have not contributed code directly so far. My contributions have been limited to a number of bug reports and ideas spread across several projects.

:I was instrumental in introducing Linux in my undergraduate CS department back in 2001. I have been wanting to contribute to Open-source ever since. I had dreamed of making significant contributions when I quit my corporate job and joined an NGO as the IT manager. But my time there was spent in developing and deploying the IT infrastructure using 100% Open-source software (Plone, Django, Zope, MySQL, Apache, TeX, Ubuntu). My deep desire to contribute and be part of the community would often turn to guilt, especially when I would be awed by the quality of some feature in the Open-source software stack I use every day (Linux has been my Primary OS since 2002).  

:I was instrumental in introducing Linux in my undergraduate CS department back in 2001. I have been wanting to contribute to Open-source ever since. I had dreamed of making significant contributions when I quit my corporate job and joined an NGO as the IT manager. But my time there was spent in developing and deploying the IT infrastructure using 100% Open-source software (Plone, Django, Zope, MySQL, Apache, TeX, Ubuntu). My deep desire to contribute and be part of the community would often turn to guilt, especially when I would be awed by the quality of some feature in the Open-source software stack I use every day (Linux has been my Primary OS since 2002).  

I am back in school doing my CS Masters now and I think this summer, this SoC could enable me to finally contribute to the community as an Open-source developer.

I am back in school doing my Computer Science Masters in Human Computer Interaction now and I think this summer, this SoC could enable me to finally contribute to the community as an Open-source developer.

===About my project===

===About my project===

** Conduct an informal user study observing children from the 2 target age groups using the system.

** Conduct an informal user study observing children from the 2 target age groups using the system.

*Week 1 (May 23 - 30): Brainstorm different designs based on the observations. Form basic UI design principles and sample mockups for the different age groups. Improvise with feedback from mentor & community. These principles would guide the rest of my GSoC work.

*Week 2 (May 30 - June 6): Start building the necessary support structures in the core system for Adaptive UI.  

| Week 1 || May 23 - 30 || Brainstorm different designs based on the observations. Form basic UI design principles and sample mockups for the different age groups. Improvise with feedback from mentor & community. These principles would guide the rest of my GSoC work.

*Week 3 (June 6 - 13): Continue building support structures for Adaptive UI. Code review and commit. No changes to system behavior at this point.

*Week 4 (June 13 - 20): Start work on improving discoverability of keyboard shortcuts.

| Week 2 || May 30 - June 6 || Start building the necessary support structures in the core system for Adaptive UI.  

*Week 5 (June 20 - 27): Code review and commit. Blog. System should now have enhanced (age agnostic) discoverability of keyboard shortcuts.

*Week 6 (June 27 - July 4): Hook up the keyboard shortcuts discoverability feature with the Adaptive UI mechanism. Give user the ability to turn-off this hook.

| Week 3 || June 6 - 13 || Continue building support structures for Adaptive UI. Code review and commit. No changes to system behavior at this point.

*Week 7 (July 4 - 11): Code review and commit. System should now have discoverability of keyboard shortcuts feature depending upon the age of the user.

*Week 8 (July 11 - 18): Refactoring week. Review all committed code. Refactor, code review and commit. Blog.

| Week 4 || June 13 - 20 || Start work on improving discoverability of keyboard shortcuts.

*Week 9 (July 18 - 25): Start work on improving discoverability of context menus.

*Week 10 (July 25 - Aug 1): Code review and commit.

| Week 5 || June 20 - 27 || Code review and commit. Blog. System should now have enhanced || age agnostic discoverability of keyboard shortcuts.

*Week 11 (Aug 1 - 8): Hook it up with the Adaptive core.

*Week 12 (Aug 8 - 15): Finish work, core review and commit.

| Week 6 || June 27 - July 4 || Hook up the keyboard shortcuts discoverability feature with the Adaptive UI mechanism. Give user the ability to turn-off this hook.

*Sign-off GSoC

*Week 13 (Aug 15 - 22): Document work. Blog. Put up a presentation summarizing my work and experience so far.

| Week 7 || July 4 - 11 || Code review and commit. System should now have discoverability of keyboard shortcuts feature depending upon the age of the user.

 

| Week 8 || July 11 - 18 || Refactoring week. Review all committed code. Refactor, code review and commit. Blog.

| Week 9 || July 18 - 25 || Start work on improving discoverability of context menus.

| Week 10 || July 25 - Aug 1 || Code review and commit.

| Week 11 || Aug 1 - 8 || Hook it up with the Adaptive core.

| Week 12 || Aug 8 - 15 || Finish work, core review and commit.

| Sign-off GSoC

| Week 13 || Aug 15 - 22 || Document work. Blog. Put up a presentation summarizing my work and experience so far.

   

   

Week 9 - Week 12 is a safety zone. If everything goes well, I should be able to go through it as planned. Otherwise, I can use this time to finish any pending work from previous weeks.

Week 9 - Week 12 is a safety zone. If everything goes well, I should be able to go through it as planned. Otherwise, I can use this time to finish any pending work from previous weeks.