wiki:Event/2011/GCI

Version 50 (modified by graeme, 10 years ago) ( diff )

--

Tasks for GCI

Tasks should be migrated to "Tasks to Upload" sheet on: https://docs.google.com/a/sahanafoundation.org/spreadsheet/ccc?key=0Ak_4NxEC3sIUdG9qZl9MT1psOWQtWmY3NXUtVmpGX2c&hl=en_US#gid=2

Info: http://code.google.com/p/google-code-in/wiki/GCIAdminMentorInformation

Code

Fixing Bugs

2 x Hard: http://eden.sahanafoundation.org/report/1

2 x Easy: http://eden.sahanafoundation.org/report/18

Enhancements

Medium (Fran): Projects/Basic#ScaleUploadedImages

Build library(ies) to integrate Emergency Data Exchange Language Distribution Element

Difficulty : HARD proposed by: | Nuwan
Specific : | EDXL-DE is the final wrapper (envelope) of all | EDXL data package. We may be delivering a EDXL Resource Management (RM) information and Situational Reporting (SITREP) information to the managers of several emergency organizations. The DE will contain who, when, and where those RM and SITREP data parcels would be delivered. Every EDXL message (data package) must carry this information. Otherwise, it cannot use available distribution methods and would need to rely on its own protocol; that's not very user friendly.
Measurable: It is purely a coding task that involves playing with XML and developing a class, possibly within or using the ??? 3R ??? framework It is basically a set of procedures for packing and unpacking EDXL-DE wrapped data.
Attainable: run through the steps
Step 1 :: select one of the existing EDXL-based applications in Eden, I recommend the EDXL-RM
Step 2 :: discuss each of the attributes/elements; then determine how EDXL-DE would be added to EDXL-RM as a pop-up GUI.
Step 3 :: create some example XML files to get a feel for the inputs and outputs
Step 4 :: write code to add to take the inputs EDXL-RM and EDXL-DE to package the data for delivery
Step 5 :: test the code, fix bugs, and generalize the functions
Step 6 :: Apply to EDXL-HAVE and EDXL-SITREP to generalize the library
Relevant : Applies to Sahana Interoperability policy. Present developments to investigate are: HAVE, RM, and SITREP http://www.oasis-open.org/standards#edxl
Time-bound: If steps 1 - 4 are completed that can be a full accomplishment; additional work is a bonus
Evaluate : Produce XML files with the EDXL-DE element appended to the EDXL-RM, SITREP, or HAVE
Reevaluate: Use an API to add and strip the EDXL-DE to any EDXL data standard. Use the same set of XML files to run through this process

Packaging

Easy (Fran): Windows Installer for End-Users

Migrated to "Tasks to Upload"

Easy (Fran): Windows Installer for Developers

Migrated to "Tasks to Upload"

Documentation

Test Developers Installation Documentation for Windows

Follow the documentation on http://eden.sahanafoundation.org/wiki/InstallationGuidelines to install a developer's instance of Sahana Eden on your Windows OS. Once you have completed send an email to the groups.google.com/group/sahana-eden list stating: 1) How long it took you 2) What was the most difficult step 3) 5 ways the documentation be improved. You will be encouraged to edit the documentation on the Wiki to add content to clarify & simplify it.

Test Developers Installation Documentation for Mac

Follow the documentation on http://eden.sahanafoundation.org/wiki/InstallationGuidelines to install a developer's instance of Sahana Eden on your Mac OS. Once you have completed send an email to the groups.google.com/group/sahana-eden list stating: 1) How long it took you 2) What was the most difficult step 3) 5 ways the documentation be improved. You will be encouraged to edit the documentation on the Wiki to add content to clarify & simplify it.

Test Developers Installation Documentation for Linux

Follow the documentation on http://eden.sahanafoundation.org/wiki/InstallationGuidelines to install a developer's instance of Sahana Eden on your Linux OS. Once you have completed send an email to the groups.google.com/group/sahana-eden list stating: 1) How long it took you 2) What was the most difficult step 3) 5 ways the documentation be improved. You will be encouraged to edit the documentation on the Wiki to add content to clarify & simplify it.

Test Customization Documentation

Follow the documentation on http://en.flossmanuals.net/sahana-eden/customisation/ to customize your local instance of Sahana Eden. Once you have completed send an email to the groups.google.com/group/sahana-eden list with: 1) Screen Shots of your customized application 2) How long it took you 3) What was the most difficult step 4) 5 ways the documentation be improved. You will be encouraged to edit the documentation in the Book to add content to clarify & simplify it.

Test Building a New Module Documentation

Follow the documentation on http://en.flossmanuals.net/sahana-eden/building-a-new-application/ to customize your local instance of Sahana Eden. Once you have completed send an email to the groups.google.com/group/sahana-eden list with: 1) Screen Shots of your customized application 2) How long it took you 3) What was the most difficult step 4) 5 ways the documentation be improved. You will be encouraged to edit the documentation in the Book to add content to clarify & simplify it.

Add Screen Shots to Building a New Module Documentation

Follow the documentation on http://en.flossmanuals.net/sahana-eden/building-a-new-application/ to customize your local instance of Sahana Eden. Once you have completed send an email to the groups.google.com/group/sahana-eden list with: 1) Screen Shots of your customized application. You will need to take the relevant sections of these screen shots and add the into the Book as examples 2) How long it took you 3) What was the most difficult step 4) 5 ways the documentation be improved. You will be encouraged to edit the documentation in the Book to add content to clarify & simplify it.

Outreach

Design Trac template to align with: wiki.sahanafoundation.org/doku.php/foundation:branding

Videos

Give a presentation on Sahana Eden to a group (And Video) - hard

Design an IRC Bot to automatically greet new people who join the sahana-eden channel

ping members of the PMC and keep a record of all people who join the channel.

Quality Assurance

  • 2 xTesting and reporting bugs
  • Using Selenium IDE create test scripts for application (easy)
  • Document the data needed for a selenium test script to run from a bare (prepopulated) system (medium)
  • Take a selenium script (see above) and using the test API generate a python test (hard)

Research

3 x Create disaster scenarios & demos with data through pre-populate

Map elements between EDXL-SITREP and EDXL-RM

Difficulty : EASY Proposed by: | Nuwan
Specific : There are several elements within the | EDXL-SITREP data standard that are identical to that of | EDXL-RM. The objective is to create a descriptive table of those elements that a programmer can use to develop a set of procedures to strip the RM data from SITREP to manage records in the relational database
Measurable : Requires diligently investigating each and every data element then comparing them with the two data standards SITREP and RM. Requires knowledge of data types and XML. If not, this exercise will help the student learn about XML and data standards
Attainable :
Step 1 :: Go through EDXL-RM and EDXL-SITREP documentations
Step 2 :: create example files to get an understanding of the data and structure
Step 3 :: develop the table with RM and SITREP elements with a description
Step 4 :: develop a simple XSL file to strip the RM data from SITREP
Relevant : Applies to Sahana interoperability policy. Given that Eden does support resource and incident management, it is important to derive the response resources and resource requirements from situational reports. This function would help automate some of those data extraction functions. That requires integrating the SITREP and RM components with underlying Eden schema
Time-bound : The exercise of understanding the data standards and mapping the elements should not take more than one week. developing a XSL to test the mapping may take another week, depending on the level of expertise with XML.
Evaluate : The mapping table is the determining output. However, the example RM and SITREP files are also required.
Reevaluate : If the XSL transformation is developed, then the mapping can be tested with the sample RM and SITREP files

Blue print to add Transliteration to text entry controls

Difficulty : MEDIUM Proposed by: | Nuwan
Specific : , for example with http://www.google.com/ime/transliteration/ engine or any other generic plug-in
Measurable :
Attainable :
Relevant :
Time-bound :
Evaluate :
Reevaluate :

Provide UTF8 names for Locations exported from GADM in Vietnam

Mentor: Fran

  • Original Source for Boundaries: GADM
    • L1 names cleaned-up: VNM_L1.csv
    • L2, L3 & L4 names which need cleaning: VNM_adm4.7z (Focus on L2 1st, then L3, then finally L4 if you can)
  • Potential Source for UTF-8 Names: Wikipedia

Migrated to "Tasks to Upload"

Training

Translation

Translating key phrases

Each task consists of a language file (a spreadsheet) of about 100 phrases, see the attachments at the bottom of this page, masterLanguageFile1.csv, masterLanguageFile2.csv and masterLanguageFile3.csv. This file needs to be translated to the target language, with the translation in the target column.

Each phrase is related to data displayed on screens on the default home page, the registration page the login and out process and the personnel profile.

Depending upon the target language some of these phrases have already been translated but you don't need to worry about what has and what has not been translated.

Do not use an automatic translation service, when these phrases are being translated the meaning also needs to be retained. If you are unsure of the meaning, contact a mentor via IRC for assistance, and continue with other phrases, until you get a reply.

Some phrases contain a special sequence as follows: %(some_name)s this sequence must be retained within the translated string. The sequence always starts with a %( combination and ends with a ) followed by a singe letter, normally a s. As already stated this sequence must be retained exactly as written but the order within the phrase may change, depending upon the sentence structure of the target language. Again, if you are unsure contact a mentor via IRC for assistance.

To complete a task you should make an effort to translate all phrases but occasionally it is not possible to translate some phrases. A task will be accepted so long as more than 90% have been translated and a reasonable explanation, of why the untranslated phrases were left, is provided. The final say on this is will be left up to the mentor.

Review code to for quality of localized strings (1 task = 3 fixes)

  • Avoid concatenation of localized strings - use %(variable_name)s instead
  • Avoid non keyboard characters (Excel doesn't handle these)
  • Try to use consistent language

User Interface

Provide feedback on Workflows in Sahana Eden

Design a better homepage for Sahana Eden (wireframes)

Design a better GUI (deliverable: "wireframes" = moderate)

for Common Alerting Protocol (CAP) with capabilities for multi-language alerting and multi-media delivery; use Agasti CAP Broker as a starting point (Nuwan) Difficulty : MEDIUM Proposed by: | Nuwan
Specific : , for example with http://www.google.com/ime/transliteration/ engine or any other generic plug-in
Measurable :
Attainable :
Relevant :
Time-bound :
Evaluate :
Reevaluate :

Design a GUI (deliverable: "wireframes" = hard)

Difficulty : MEDIUM Proposed by: | Nuwan
Specific : , for example with http://www.google.com/ime/transliteration/ engine or any other generic plug-in
Measurable :
Attainable :
Relevant :
Time-bound :
Evaluate :
Reevaluate :
for building implementation specific XSL documents that generate SMS, Email, IVR, tweet, etc multi-media delivery text outputs (Nuwan)

Attachments (35)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.