112
edits
Changes
Jump to navigation
Jump to search
Line 55:
Line 55: − 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<br />+ − 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)<br /> − − − June 31 - Mid Term Examination<br />+ − + − + +
Summer of Code/2014/sugar cordova (view source)
Revision as of 13:06, 18 March 2014
, 13:06, 18 March 2014/* 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 h...
===== 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. =====
April 21 –May 19 – Talk with my mentors and discuss a clear outline of the project, define steps to approach the problem and discuss ways by which we can attack the issue, understand all the technicalities required for the project - the sugar -web architecture through the code, the record activity and other python code on which we shall be developing, start coding in python as required <br />
May 19 – May 31 – Code up the sugar APIs required for the further building the cordova plugins<br />
May 31 - June 15 - Code the cordova plugins and the corresponding code in the cordova native APIs , write the javascript APIs<br />
April 13 –May 19 – Talk with my mentors and discuss a clear outline of the project, define steps to approach the problem and discuss ways by which we can attack the issue, understand all the technicalities required for the project - the sugar -web architecture through the code, the record activity and other python code on which we shall be developing, start coding in python as required <br />
May 19 – June 15 – Build the architecture for the python-javascript for the cordova container<br />
June 15 - June 30 - Make a sample activity to show the working of the architecture developed<br />
June 15 - June 30 - Make a sample activity to show the working of the architecture developed<br />
'''Mid Term Examination'''<br />
July 1 - July 20 - Refine the code developed till now, add more functionality and features, remove errors<br />
July 1 - July 15 - add more plugins, improve upon the existing code as required<br />
July 20 onwards – Document all the new API's of the JavaScript library made till now, add more
July 15 - July 31 - write the corresponding activities for the plugins added above and test the work done till now<br />
August 1 - August 18 - Document the work, APIs and improve upon the existing project
===== 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. =====
===== 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. =====