Date

17 Jul 2018

Call-in Information

Time: 10:00 am, Eastern Time (New York, GMT-04:00)

To join the online meeting:

Join from PC, Mac, Linux, iOS or Android: https://uqam.zoom.us/j/981823821

Or iPhone one-tap :
    Canada: +16475580588,,981823821#
Or Telephone:
    Dial(for higher quality, dial a number based on your current location):
        Canada: +1 647 558 0588
    Meeting ID: 981 823 821
    International numbers available: https://zoom.us/u/eAvn48bdc

Or an H.323/SIP room system:
    H.323:
        162.255.37.11 (US West)
        162.255.36.11 (US East)
        221.122.88.195 (China)
        115.114.131.7 (India)
        213.19.144.110 (EMEA)
        202.177.207.158 (Australia)
        209.9.211.110 (Hong Kong)
        64.211.144.160 (Brazil)
        69.174.57.160 (Canada)
    Meeting ID: 981 823 821

    SIP: 981823821@zoomcrc.com

Slack

• https://vivo-project.slack.com
  • Self-register at:  https://goo.gl/forms/JxQFkut4TYj4Ehww1 
    

Attendees

 Indicating note-taker

1. Kitio Fofack

2. Mike Conlon

3. Christian Hauschke

4. Andrew Woods

5. Joachim Dornbusch

6. Manuel Schwarz

7. Graham Triggs

8. Anna Kasprzik

9. Huda Khan

10. Muhammad Javed

11. Ralph O’Flinn

Agenda

1. Task force governance
   1. Objectives
   2. Schedule
2. Technical choices for i18n implementation
3. i18n issues
   
   1. fallback mechanism
   2. release policy
   3. maintenance of language versions - tools and processes to be notified of language related changes in the VIVO code
   4. better usability for switching languages in standard themes (no flags)

4. JIRA tickets

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes

1. Task force governance

1. Objectives

1. To fulfill the requirements the document specifies
   https://docs.google.com/document/d/1liFlAkwocgoy_F28YiyKbegZglumy0xIDlz_zcwykzA/edit#

2. Constructing rules for including I18N into the development process

2. Schedule

1. Mike is suggesting once every two weeks

2. Requirements (https://docs.google.com/document/d/1liFlAkwocgoy_F28YiyKbegZglumy0xIDlz_zcwykzA/edit#)

1. Complete multilingual interface - everything will be language-agnostic. English is treated as one of many possible languages.

2. Multilingual content edition

3. Configure available languages on the fly

1. Rephrased in “Make language configuration easier”

4. Fallback mechanism

1. Fallback for data. What happens when no french label exists, but the user chose to view VIVO in French

2. If a thing has a label, translations should be tied to this one thing.

3. Hard to decide on a fallback mechanism

1. Falling back to a pre-defined language

2. Showing nothing or an error if label in the selected language does not exist

3. Fallback languages should be customizable (like Portuguese in Macao-China).   

3. i18n issues

1. fallback mechanism

2. release policy

1. There needs to be a review and release policy for /vivo-languages

3. maintenance of language versions - tools and processes to be notified of language related changes in the VIVO code

1. VIVO languages should be maintained by its language community

2. Language repositories are separate so they can be released independently and be used as artefacts.

4. better usability for switching languages in standard themes (no flags)

Actions

• ...