85 | | Clearly outline your timeline and goals for the project. All goals must follow the SMART (http://en.wikipedia.org/wiki/SMART_%28project_management%29) methodology - they should be Specific, Measurable, Achievable, Realistic and Time-bound. Each goal should explicitly tell us how we can measure it (e.g. code committed to trunk and can be assessed on demo.sahana.lk) and the date it is due. This should be provided as three columns - Due Date, SMART Goal, and Measure. The project is looking for explicit and well-written goals - proposals that contain broad and general goals will not be accepted. The more specific your goals, the better chance you have of being accepted. |
86 | | |
87 | | These should be broken down into the following stages. |
88 | | |
89 | | * Work already undertaken |
90 | | * I have already started studying current translation system in eden |
91 | | |
92 | | * First trimester (24 April - 20 May) - identify the SMART goals you have for the community bonding period. Most of these are likely to revolve around further scoping of the project with the community, engaging with the community, and updating and finalizing the project plan. |
93 | | * 10 May - 17 May: |
94 | | |
95 | | * Second trimester (21 May - 9 July) - identify the draft SMART goals you have for the first half of the project. These will be used to assess project process and form the basis for the mid-term evaluation. |
96 | | * '''Implementation of CLI''' |
97 | | * 22 May - 28 May: develop a python script to extract and store strings from the modules being used |
98 | | * 29 May - 4 June: convert the file of stored strings to a spreadsheet |
99 | | * 5 June - 11 June: develop a python script to feed the translated string from the spreadsheet back into eden |
100 | | * 12 June - 22 June: Automate the above three processes |
101 | | * 23 June - 30 June: Modify T() function as required |
102 | | * 1 July - 8 July: Testing and bug fixing |
103 | | |
104 | | * 10 July - 13 July: Midterm evaluation |
105 | | |
106 | | * Third trimester (10 July - 13 August) - identify the draft SMART goals you have for the second half of the project. These will be used to assess the whole project and in conjunction with the mid-term goals, form the basis for the final evaluation. |
107 | | * '''Implementation of GUI''' |
108 | | * 10 July - 15 July: commit adjustments based on the mentor's feedback of the mid evaluation |
109 | | * 16 July - 25 July: on the fly translation |
110 | | * 25 July - 3 August: progress report on translation of each module |
111 | | * 4 August - 13 August: Testing and bug fixing |
112 | | |
113 | | |