Date
10
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://
...
...
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
- Self-register at: https://goo.gl/forms/JxQFkut4TYj4Ehww1
...
Attendees
Indicating note-taker
Kitio Fofack
Mike Conlon
Christian Hauschke
Andrew Woods
Joachim Dornbusch
Manuel Schwarz
Graham Triggs
Anna Kasprzik
Huda Khan
Muhammad Javed
Ralph O’Flinn
Agenda
- Task force governance
- Objectives
- Schedule
- Technical choices for i18n implementation
- i18n issues
- fallback mecanism
Notes
...
- mechanism
- release policy
- maintenance of language versions - tools and processes to be notified of language related changes in the VIVO code
- better usability for switching languages in standard themes (no flags)
JIRA tickets
Expand Jira server DuraSpace JIRA jqlQuery filter=14602 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Notes
Task force governance
Objectives
To fulfill the requirements the document specifies
https://docs.google.com/document/d/1liFlAkwocgoy_F28YiyKbegZglumy0xIDlz_zcwykzA/edit#Constructing rules for including I18N into the development process
Schedule
Mike is suggesting once every two weeks
Requirements (https://docs.google.com/document/d/1liFlAkwocgoy_F28YiyKbegZglumy0xIDlz_zcwykzA/edit#)
Complete multilingual interface - everything will be language-agnostic. English is treated as one of many possible languages.
Multilingual content edition
Configure available languages on the fly
Rephrased in “Make language configuration easier”
Fallback mechanism
Fallback for data. What happens when no french label exists, but the user chose to view VIVO in French
If a thing has a label, translations should be tied to this one thing.
Hard to decide on a fallback mechanism
Falling back to a pre-defined language
Showing nothing or an error if label in the selected language does not exist
Fallback languages should be customizable (like Portuguese in Macao-China).
i18n issues
fallback mechanism
release policy
There needs to be a review and release policy for /vivo-languages
maintenance of language versions - tools and processes to be notified of language related changes in the VIVO code
VIVO languages should be maintained by its language community
Language repositories are separate so they can be released independently and be used as artefacts.
better usability for switching languages in standard themes (no flags)
Actions
- ...