Table of Contents |
---|
What
The primary objective of the i18n sprints are to bring the language-aware editing capabilities into the core VIVO application.
...
- Creation of Integration and Regression tests to ensure the existing functionality does not break during the course of the i18n editing development activities (and beyond)
- Transfer of UQAM software updates into one or more GitHub repositories
- Review, testing and integration of the initial UQAM software updates into core VIVO
- Given the size of these initial software updates, we will need to slice the updates into smaller units of functionality and pull-requests
- Establishment of a pattern for making additional languages available to all VIVO installations
- Review and test incremental i18n editing updates
- Update documentation of installation and configuration guides
When
- April 6th - 17th
- Pre-sprint planning meeting: Doodle
Four Three sprints are planned:
- April 6 - 17
- May 19 - 25 (Tuesday through following Monday)
- June 22 - July 3 (sprints 3 and 4 combined)
Who (and roles)
Roles: developer, documenter, tester, translator, other?
...
- Michel Héon(UQAM) Developer
- Joachim Dornbusch (EHESS)
- Christian Hauschke (TIB; testingcheck German version pages, documentation)
- Benjamin Gross (limited availability, testing and code review)
- Ralph O'Flinn (based on Scholars needlimited availability, testing and code review)
- Alexander (Sacha) Jerabek(UQAM - review documentation, check French version pages, test installation of Vivo)
- Matthias Lühr(HS Mittweida; testing, documentation)
- Andrew Woods
- Others?
...
- Developer / Tester
- Nicolas Dickner(UQAM - review documentation, check French version pages, test installation of Vivo)
- Rachid Belkouch (UQAM - review documentation, check French version pages, help coordinate if necessary)
Panel |
---|
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:
|
Resources
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 |
...
| |||
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 |
Sprint goals
Updates will go into the core
Sprint will demonstrate editing with French, German and English
Regression testing with Selenium
UQAM code will be in GitHubUpdated documentation
Sprint prerequisites
Code in GitHub
GitHub diff/pr
- Remove whitespace from VIVO and Vitro working branches
How How can the code be subdivided?
- Test data
...
- - no, the plan is to refine the sprint branches, then submit uber-PR
Test data
Set up a reporting and monitoring tool for identified problems (potentially Jira) able to manage screenshots - JIRA scrum board
Future goals
- English to be extracted, like any other language
- All VIVO languages will be consolidated into central language repositories
- Move translation files to ontology files
Working GitHub branches
- VIVO : https://github.com/vivo-project/VIVO/tree/sprint-i18n-whitespace (until we have whitespace removed)
- Vitro : https://github.com/vivo-project/Vitro/tree/sprint-i18n-whitespace (until we have whitespace removed)
- VIVO-languages : https://github.com/vivo-project/VIVO-languages/tree/sprint-i18n
- Vitro-languages : https://github.com/vivo-project/Vitro-languages/tree/sprint-i18n