The primary objective of the i18n sprints are to bring the language-aware editing capabilities into the core VIVO application.
This objective will include the following goals:
Four Three sprints are planned:
Roles: developer, documenter, tester, translator, other?
Sprint SummaryThe (current) i18n sprint officially ended on Friday, April 17th. The team consisted of ten participants from 6 different organizations. The top-level objective of the effort is to establish a clearly documented capability within VIVO to add new and enable existing languages such that both the static text as well as the site-specific data is exposed in a language-aware context. Additionally, the effort is focused on adding the ability to create language-aware content in the native VIVO user interface. In addition to establishing a cohesive and productive team, the primary outcomes of the sprint include:
Remaining tasks include:
In order to complete the outstanding tasks, we will be holding one-week-long sprints during the months of May, June and July. Mark you calendars! These sprints will be happening on the third full week of the month:
|
Description | Resources | |
---|---|---|
1) Project wiki | ||
2) UQAM's GitHub | https://github.com/UQAM-VIVO/ - although development will happen on the 'sprint-i18n' branches of VIVO/Vitro/VIVO-languages/Vitro-languages | |
3) Test data | https://github.com/UQAM-VIVO/VTE-config/tree/master/Data
| |
4) i18n Reference Demo Demo VIVO server consisting of UQAM's implementation of the i18n editor design | http://vivo-i18n.dev.uqam.ca:8080/vivo_i18n_M2/
| |
5) Vivo Translation Ecosystem Ecosystem useful for the development of VIVO
| http://vivo-i18n.dev.uqam.ca:8080/download/VIVO-Trad-ecosysteme.exe | |
6) VTE First run wiki
| https://wiki.uqam.ca/display/VIVOPUB/C%29+Local+VIVO+implementation%3A+from+scrach+to+execution+with+VTE |
Updates will go into the core
Sprint will demonstrate editing with French, German and English
Regression testing with Selenium
Updated documentation