Versions Compared

Old Version 26

changes.mady.by.user Andrew Woods

Saved on

compared with

New Version Current

changes.mady.by.user Alexander (Sacha) Jerabek

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. 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)
  2. Transfer of UQAM software updates into one or more GitHub repositories
  3. Review, testing and integration of the initial UQAM software updates into core VIVO
    1. Given the size of these initial software updates, we will need to slice the updates into smaller units of functionality and pull-requests
  4. Establishment of a pattern for making additional languages available to all VIVO installations
  5. Review and test incremental i18n editing updates
  6. Update documentation of installation and configuration guides

When

Four Three sprints are planned:

  • April 6 - 17
  • May 19 - 25 (Tuesday through following Monday)
  • June 22 - July 3 (sprints 3 and 4 combined)
  • April 6th - 17th
  • Pre-sprint planning meeting: Doodle

Who (and roles)

Roles: developer, documenter, tester, translator, other?

...

Panel

Sprint Summary

The (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:

  1. Initial (pre-beta) implementation of i18n edit capabilities, found on the "sprint-i18n" branches of the VIVO, Vitro, VIVO-languages and Vitro-languages projects
  2. Comprehensive testing of the i18n implementation across (almost) all UI pages, and associated JIRA ticket creation
    1. 63 JIRA bug tickets created (14 resolved)
    2. 6 JIRA improvement tickets created (4 resolved)
    3. 4 JIRA test tickets created
    4. 4 JIRA documentation tickets created
  3. Selenium testing framework created with a focus on i18n
  4. Git / GitHub process documentation created to help onboard team members to the VIVO development processes

Remaining tasks include:

  1. Finish testing of remaining few UI pages
  2. Resolving and verifying fixes of identified bugs
  3. Documentation of how to use the updated functionality, how to enable languages, and how to add a new language
  4. Expanding Selenium tests
  5. Code refactoring

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 calendarcalendars! These sprints will be happening on the third full week of the month:

  1. May 18-22
  2. June 15-19
  3. July 20-24

...