wiki:Event/2012/GSoC/Translation

Version 1 (modified by Kalpa Welivitigoda, 10 years ago) ( diff )

Initial writing

Upgrade Translation Functionality: Application

1. Personal Details

  • Name: Kalpa Pathum Welivitigoda
  • Communication details
    • Email: callkalpa [AT] gmail.com callkalpa [AT] fedoraproject.org
    • Freenode IRC Nickname: callkalpa
    • Skype: callkalpa
    • Blog: www.kalpapathum.blogspot.com
  • Include Biographical information about yourself, your education, country, timezone etc.
    • I am from Sri Lanka (GMT+0530) and an undergraduate at Department of Electrical Engineering, Faculty of Engineering, University of Moratuwa, Sri Lanka
  • Please provide an overview of your exposure to similar technologies and/or FOSS in general.
    • I have been involved with localising following projects to Sinhala, which is my native language (here I have worked with Pootle)
    • I am a packager at Sugar Labs (http://www.sugarlabs.org), a contributor at Hanthana Linux (http://www.hanthana.org), and occasionally write articles to local FOSS Magazines.
  • Please answer the question - “Why would you like to help the Sahana project?”
    • Because Sahana project is a project which helps to help people in case of need. The purpose is for humanity.

2. Personal Availability

  • Have you reviewed the timeline for GSOC2012?
    • Yes I have already
  • Do you have any significant conflicts with the listed schedule? If so, please list them here.
    • I have examinations at the university from 24th April to 10th May. Since it is the community bonding period I don't think that it will be a major issue.
  • Will you need to finish your project prior to the end of the GSOC?
    • No. My project plan is for the entire GSoC period.
  • Are there any significant periods during the summer that you will not be available?

3. Project Abstract

  • Provide a brief overview of the proposed idea and objectives you want to achieve with it here. (250 word limit)
    • Sahana-eden currently uses web2py translating feature to translate sahana-eden to different languages. With the current system only the original strings and the translated strings are available to the translators. That only would not be enough to translate correctly with the proper meaning. The objective of the project is to improve the translation process so that the translators have more information such as file name, line number, comments for the translators etc. So for example the translators will know the module in which the strings are in and that will help to translate more appropriately. Further the T() function currently used to identify strings to be translated will be improved so that the developer can add a comment for the translators. And a GUI (a web page) embedded into eden will be implemented so as to translations on the fly.

4. Project Plan

This section is to provide the detail of your project proposal. Take as much space as is necessary.

  • Project Deliverable - What is the essence of the project? What capability are you looking at adding to Sahana that will expand its capability for emergency/disaster management?
  • Project Justification - What is the relevance of your idea to the project? Why do you think its important to *have* this idea integrated to the Sahana system.
  • Implementation Plan - How are you going to implement your project? Use this section to expand in as much detail as possible how it should be constructed.
  • Future Options - Identify some aspects of the project that may not be within the scope of this submission, but could form the basis for future work that would build upon the outcomes of your project
  • Relevant Experience - Please list all experience you have that is directly relevant to the proposed project, and how they would help you deliver the project. If you have contributed to the Sahana project previously, please clearly outline your contributions.

You can also include links to additional details like diagrams etc outlining your ideas acting as supplementary information for your proposal outside of this scope. But it is highly advised to follow the KISS principle and stay as specific as possible.

5. Project Goals and Timeline

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.

These should be broken down into the following stages.

Work already undertaken - What research have you undertaken in this area in advance? (these can just be bullet points and are not required to follow the SMART methodology) 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. 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. 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.

We recognize that the goals may change during the project, and the mentors will accept modifications to the goals at any time. For example, discussion during the community engagement stage may change the scope of the project, and the goals may need to be subsequently modified. As such, the goals are not hard-and-fast, but we do want to see reasonable effort go into the initial project timeline.

The intent is to maintain these as a shared Google Spreadsheet so that mentors can track progress in the spreadsheet.

The Project Goals and Timeline will form a significant part of the assessment of your application, as well as mid-term and final evaluations.

Note: See TracWiki for help on using the wiki.