Line 34: |
Line 34: |
| | | |
| ===== What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; 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 (27 June); 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? The Summer of Code work period is from May 19 - August 22; 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 (27 June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then. ===== |
− | March 9 – March 15 – Understand the high level architecture of project , go through the code of different platforms, come out with plan for sugar lab platform | + | March 9 – March 15 – Understand the high level architecture of project , go through the code of different platforms, come out with plan for sugar lab platform<br /> |
− | March 16 – March 22 – Look into the corresponding code of sugar labs , how the cordova plugins can be made from the present sugar code | + | March 16 – March 22 – Look into the corresponding code of sugar labs , how the cordova plugins can be made from the present sugar code<br /> |
− | March 23 – March 29 – Understand the sugar code required for implementing the the functionalities | + | March 23 – March 29 – Understand the sugar code required for implementing the the functionalities <br /> |
− | April 1 – 12 – Buffer Period (Have sessional exams in college) | + | April 1 – 12 – Buffer Period (Have sessional exams in college)<br /> |
− | April 13 – April 21 – After understanding the sugar code required for implementing the device functionality, can either continue with the code already there if exist or write in python in order to execute the corresponding activities | + | April 13 – April 21 – After understanding the sugar code required for implementing the device functionality, can either continue with the code already there if exist or write in python in order to execute the corresponding activities<br /> |
− | April 21 – May 3 – Write the corresponding code in JavaScript | + | April 21 – May 3 – Write the corresponding code in JavaScript<br /> |
− | May 3 – May 17 – Write some activities based on the JavaScript, python architecture made | + | May 3 – May 17 – Write some activities based on the JavaScript, python architecture made<br /> |
− | May 17 - May 31 – Improve the code , remove errors if any and start out with implementation of other functionalities | + | May 17 - May 31 – Improve the code , remove errors if any and start out with implementation of other functionalities<br /> |
| May 31 – June 30 – Add functionalities, improve upon those made and make sample activities for new functionalities added | | May 31 – June 30 – Add functionalities, improve upon those made and make sample activities for new functionalities added |
− | July 1 – July 18 – Incorporate suggestions and improvement after the evaluation | + | July 1 – July 18 – Incorporate suggestions and improvement after the evaluation<br /> |
| July 20 onwards – Document all the new API's of the JavaScript library made till now, add more if time allows and make the existing code bug free. | | July 20 onwards – Document all the new API's of the JavaScript library made till now, add more if time allows and make the existing code bug free. |
| | | |